View previous topic :: View next topic |
Author |
Message |
simon
Joined: 05 Jul 2006 Posts: 297
|
Posted: Fri Apr 25, 2025 8:42 pm Post subject: setMaxLines |
|
|
I have an application that works perfectly ok until I have opened an external file a couple of times, and then all of the menu items stop working. The program has not frozen; if I click on the menus they still expand, but the callback functions are not activated so the user cannot do anything. Even the exit callback function does nothing. The behaviour is the same compiled with x64 and Win32. The program will quit using the X button on the menu bar, but I then get the following error message if I have compiled in x64, but I get no message with Win32:
Code: | Access violation (c0000005) at address 7fff797308b4
Within file CLEARWIN64.DLL
In setMaxLines at address 7AD44
In CallWindowProcW at address 60C
Within file USER32.dll
In DispatchMessageW at address 6EC
In SendMessageTimeoutW at address 143
In KiUserCallbackDispatcher at address 24
Within file ntdll.dll
In NtUserMessageCall at address 14
Within file win32u.dll
In GetWindowTextW at address 845
Within file USER32.dll
In PeekMessageA at address 2DD
In GetWindowTextA at address 3A7
In setMaxLines at address 7F9FC |
Before I spend what will likely be a few days trying to isolate this problem, I am wondering whether anyone has any idea on what the problem might be given the above message. I do make a call to set_max_lines$ when the program starts up, but opening the external file does not repeat the call or provide any output to the ClearWin+ window that was created. |
|
Back to top |
|
 |
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 8182 Location: Salford, UK
|
Posted: Sat Apr 26, 2025 6:58 am Post subject: |
|
|
I don't have any insights on this but it is worth noting that you can learn a lot by running the application from the debugger. Even though it is using ClearWin+ you can still set multiple break points within the callback functions and often get a better idea where and how it is failing. |
|
Back to top |
|
 |
simon
Joined: 05 Jul 2006 Posts: 297
|
Posted: Tue May 06, 2025 11:18 pm Post subject: |
|
|
In case it is helpful to anyone experiencing a similar problem, I successfully resolved this issue. It was caused by an attempt to write to a ClearWin+ window with an incorrect Fortran unit number. |
|
Back to top |
|
 |
|