I’ve confirmed an issue in one of my apps when using Windows 8.1. We have not had any reports in Windows 7 (where the code works fine) or Windows 8 (as far as I know).
I have a listbox in the app and code in the key down even to tab between valid editable columns. As soon as you hit the tab key when in the listbox, the program freezes and you get a “Windows has detected that this program has stopped responding” message. The problem happens after the new listbox cell has been selected, but code is still finishing up in the previous cell’s key down event (just basically exiting a loop and hitting “End If” statements.
Anyone else seen any issues with Windows 8.1 similar to this?
I’m trying to figure out exactly what is going on and get consistent results. That’s why I have not posted any code or projects.
It seems to me that the IDE is much less stable in Windows 8.1. I am constantly having problems with it just locking up completely to the point where I have to force it to quit. This happens quite often when the app you are debugging is forced to quit by Windows (which is part of the problem I’m trying to solve).
One thing to note now that I’ve gone back and looked in my code is that I bypassed this section of code for the same reason in Linux. It was crashing in Linux. It was never a big deal as I don’t have that many Linux users. Was on my list to figure out some time. But now that Windows 8.1 is showing the same behavior, it has to be something really obscure in my code. One of those things that are a royal pain in the backside to solve…
I’ve confirmed an issue in one of my apps when using Windows 8.1. We have not had any reports in Windows 7 (where the code works fine) or Windows 8 (as far as I know).
I have a listbox in the app and code in the key down even to tab between valid editable columns. As soon as you hit the tab key when in the listbox, the program freezes and you get a “Windows has detected that this program has stopped responding” message. The problem happens after the new listbox cell has been selected, but code is still finishing up in the previous cell’s key down event (just basically exiting a loop and hitting “End If” statements.
Anyone else seen any issues with Windows 8.1 similar to this?[/quote]
Sounds to me like “something” in the code causes another event to get raised and then you get into a cascade of events firing other events
Yes. Problem is I can’t find what it is yet. I’ve put lots of debugging statements in. It’s definitely something at the framework level that is raising those events and they
It’s one of those things that once I find it, I’ll be like, “DUH!” But finding it is the hard part…
The IDE is definitely WAY less stable in Windows 8.1. I was just debugging a project that contains a subset of my problem code. The debug app was running fine (I’ve taken out things and am going to try to add them back in gradually to find the problem). I exited the app. Now the IDE is completely frozen. I’m going to have to force the app to quit and wait for it to restart.
Not sure how to necessarily post a bug report about it…
I’ve had a few reports of this crash happening to a few users. For me it is on a listbox where they can edit the cells and I display the editable text area. They press tab to go to the next area and it supposedly crashes the program. I have yet to dig into the issue first hand however.
[quote=122211:@Jon Ogden]
Looks like remote debugging is what I’m going to have to do but what a pain…[/quote]
Have you tried running as Windows 7 on the compatibility properties? Just something to try. For the most part I have had no issues with Win8 except when using peripherals. Seems to me (and this is only empirical observation - coming from a non-power user) that sometimes it seems to time out (and to be completly forthcoming, I have no tried the latest release as of yet). I’ve only seen this happen on Xojo and Win8.1 (and only when accessing peripherals). I noticed these specific apps were very stable under Win7, but not 8.1. Turned the compatibility setting and everything worked fine. Not sure how this helps you, but there you go.
You have to return true from the key down event after processing the code to move to the next cell. Once I made sure that I returned true (and passed that return value properly up the chain of supers), everything works fine. It seems that Windows 7 and OS X aren’t so concerned about the framework getting the key down event after all your code executes. Windows 8 is more picky.
And I am wondering if this will solve a similar problem that I have seen in Linux. I’ve yet to test it but I bet it does.
Bottom line (and probably good coding practice): Properly return true when you don’t want/need the framework to handle a keystroke.
It’s not a faulty comparison at all. Since the IDE is far more complex as you point out, if it is unstable and my app is crashing and Xojo is locking up while running the debugger, how am I to know if it is my app or Xojo? If Xojo is unstable, you cannot have confidence that your much simpler app will be stable.