View previous topic :: View next topic |
Author |
Message |
Ralf
Joined: 30 Aug 2007 Posts: 50 Location: munich
|
Posted: Mon Dec 10, 2018 9:44 am Post subject: editable %lv with go_down_on_return |
|
|
I am struggling with a Problem connected with %lv.
Each time I use %lv with options edit_cells and go_down_on_return I get a crash when I edit a cell and then press the return button. The corresponding error message looks like:
Unfortunately I was not yet able to reproduce this error in a simple test program, so it seems that there is another dependency.
Compiled as 32bit, the program runs fine.
Ralf |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 8003 Location: Salford, UK
|
Posted: Mon Dec 10, 2018 10:52 am Post subject: |
|
|
Ralf
Are you using the latest DLLs? I think that there was a recent fix in this context. Or was it you that previously reported a problem with 64 bit %lv? |
|
Back to top |
|
|
Ralf
Joined: 30 Aug 2007 Posts: 50 Location: munich
|
Posted: Tue Dec 11, 2018 1:39 pm Post subject: |
|
|
Paul,
I am using the 8.40 release, no recent DLL-update.
I reported another %lv Problem in July ("editable listview controls"), which you have fixed in the meantime.
Ralf |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 8003 Location: Salford, UK
|
Posted: Tue Dec 11, 2018 5:04 pm Post subject: |
|
|
Ralf
If you are able to provide me with a link to a download of your code then I will aim to track down the problem for you. |
|
Back to top |
|
|
Ralf
Joined: 30 Aug 2007 Posts: 50 Location: munich
|
Posted: Tue Dec 18, 2018 10:58 am Post subject: |
|
|
Paul,
I was able to track down the problem. It occurs in combination with a %og OpenGl graphic area.
Here is the code of my simple example:
Code: |
winapp
!=======================================================================
!=======================================================================
Program Test_Listview
!=======================================================================
! use lvt
integer :: winio@
integer :: iw
integer(kind=7) :: handle_ogl_mainwin
external :: c_func
iw = winio@ ('%ca[Test lv]&')
iw = winio@ ('%mn[Listview]&',c_func)
iw = winio@ ('%`og[depth16]', 400, 300, handle_ogl_mainwin)
stop
end
!=======================================================================================================================
integer function c_func()
!=======================================================================================================================
! use lvt
integer :: winio@
integer :: iw, nitems, listview
integer,dimension(2) :: isel
character(len=20),dimension(0:2) :: items
external :: c_func
items(0) = '|Header|Value'
items(1) = '|Test |1.0'
items(2) = '|Test2|2.0'
nitems = 3
listview = 1
iw = winio@ ('%ca[lv]&')
iw = winio@ ('%lv[single_selection,edit_cells, go_down_on_return]', &
150,100,items,nitems,iselect_legend,listview)
end
|
I have linked it with the following linker file (lw):
Code: |
lo testlv
lo tlv.res
windows
file Test_lv |
the resource file tlv.rc is an empty file
the makefile has the following lines:
Code: | src tlv.rc /r
ftn95 /64 testlv.f95
slink64 @lw
|
The crach occurs, if I open the listview from the menu, click into one of the cells and then press return. |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 8003 Location: Salford, UK
|
Posted: Tue Dec 18, 2018 11:47 am Post subject: |
|
|
Ralf
It works OK for me.
I will upload the DLLs that I am using later today. |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 8003 Location: Salford, UK
|
|
Back to top |
|
|
Ralf
Joined: 30 Aug 2007 Posts: 50 Location: munich
|
Posted: Tue Dec 18, 2018 6:34 pm Post subject: |
|
|
Paul
I have still the same Problem with the new DLLs, but I was wrong: I linked an old tlv.res, i.e. the corresponding file tlv.rc contains:
and clrwin.manifest contains:
Code: | <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">
<security>
<requestedPrivileges>
<requestedExecutionLevel level="asInvoker" uiAccess="false"/>
</requestedPrivileges>
</security>
</trustInfo>
<dependency>
<dependentAssembly> <assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0"
processorArchitecture="*" publicKeyToken="6595b64144ccf1df" language="*"/>
</dependentAssembly>
</dependency>
</assembly>
|
|
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 8003 Location: Salford, UK
|
Posted: Wed Dec 19, 2018 9:12 am Post subject: |
|
|
Ralf
It fails for me when using the given manifest. I have included a fix in ClearWin+ and uploaded a new DLL here...
https://www.dropbox.com/s/po9v8y6q9k4e61v/clearwin64.dll?dl=0
It would be interesting to know if you get a different theme (i.e. appearance) when using a manifest. In other words, when porting to 64 bits, has Microsoft ported both versions of the common controls DLL with their different themes?
If not then the manifest can be omitted. |
|
Back to top |
|
|
Ralf
Joined: 30 Aug 2007 Posts: 50 Location: munich
|
Posted: Thu Dec 20, 2018 11:04 am Post subject: |
|
|
Paul
thanks for the DLL-update. The fix works fine in my testprogram, as well as in my complex program.
Yes, I get a different appearance when I use the manifest. Especially buttons and radiobuttons look like typical Win 10 controls, otherwise they have a more old-style appearance.
Ralf |
|
Back to top |
|
|
|