Hello everyone.
I’m having a strange issue with my app. I can’t click the title bar of my MDI windows, which would allow me to move the windows within the frame.
I also can’t click “close” or “minimize.”
The mouse itself works, the driver is up-to-date.
The version works without any issues for customers.
What could this be?
I’m a bit confused.
I’m using Clarion 11 IDE and legacy templates.
It’s a multi dll app.
Thanks!
You are saying this issue only happens for you on your computer?
Have you ruled out the possibility that one of the scroll-lock types of keys haven’t been toggled?
Do you do any key ALIAS() in your app?
Other programs do not exhibit this behavior? Other Clarion programs?
What if you sign in as another user?
Do you have a cat?
Does it also happen to you on another computer?
Are there any developer only utilities revealed when only you run the app?
I suspect that something is intercepting the mouse or the click on the title bar, and the event is running into oblivion.
But I haven’t figured out which program it is yet.
I also deactivated the virus scanner, but no success.
I’ve already updated the mouse driver. Even the graphics card driver is updated.
There are no pending Windows updates.
What if you clear out whatever ini files your app stores (while your app isn’t running), including tearoff, if applicable?
What a strange thing!
After a few reboots, installing the graphics and mouse drivers several times…and suddenly it works again.
I don’t like errors like this where you don’t know exactly what caused it.
But I have to say that the mouse (hardware) did indeed have a problem, I had replaced it, but the error was still there afterwards.
It wasn’t the program itself; I tested it on several PCs.
Maybe it was the Clarion Runtime.
Something was wrong with the system (Windows).
Thanks for all the ideas…
Has no one else run into this?
I’m seeing it in production on a few windows 11 pro computers and also on a windows 7 system. (yeah I was surprised too)
I coded a bare bones clarion 11.0.13505 app with a solitary window and I’m still see the issue.
I also compiled same app in clarion 11.1.13845, and again same issue.
I have seen this behavior for some of our users and not for others. looking for comanality and can not find it. The only common thing is that it happens on version of our program compiled in C11.1 but not the same compiled in C9. Not all users experience it. It seems to be isolated to win11 but not all win11. The X on the frame still works but it does not work on MDI children windows. We also have other weird issues with this version of Clarion like speed to open / close screens. However, still hoping if I find solution to one issue, it will help resolve other issues too.
Might it be related to some manifest settings? I know there a bit there to tweak and some has odd behaviour
I was wondering about that. I don’t really know much about manifest settings. Guess it is time to start reading up on it. Anyone have any suggestions or info to share?
Do you want to share that “bare bones” app, I’d be happy to try it for you?
As requested they are here:
I cannot seem to upload zip files but am new to this group.
https://globalsoftware-inc.com/harncw/testapp/TestApp%20c11.1.zip
https://globalsoftware-inc.com/harncw/testapp/TestApp%20c11.zip
What happens if you create a subclassed procedure for one of the windows thats playing up and intercept all the WM messages before the clarion runtime processes it?
You could also create a subclassed procedure for the main (mdi frame) window because iirc the thread 1 main (mdi frame) window intercepts messages first as a process before its then diverted to the running thread and window.
What type of threading model are you using? The new C6 true threads or older C1.5 co-operative threading model?
It is in C11 and using true threads. never had any issues in C9 but nothing but issues since going to C11.1
I tested your app, and it works as it should. I can click the title bar and move the window.
I’m using Windows 11.
Are there any additional programs installed on the test PCs that could be causing this?
Something like Autotext?
Both working on mine just fine. Win11 24H2.
Both work on my Win 10 Pro 19045.5737 x64
My customer’s IT found that the issue resolved when they updated “Dell Display and Peripheral Manager”
Their email to me:
SOLVED.
There is an app called “Dell Display and Peripheral Manager” that broke this.
When we opened the app and ran the update inside the app, it fixed the MDI window issue.
I had my tech support guys apply this to a machine that we know had the issue and it did NOT fix it. one weird thing though was that it seemed to fix ONE of the screens (but none of the others) but, only the first try. When they then tried the original fixed screen again, it did not work again.