We were evaluating 2017r1 for Windows and it will crash XOJO if we click on one of our windows. We can’t even find out what is making it crash because the windows does not even show.
We are still using 2016r3 because it is the only stable version that we have found. We had issues with 2016r4, 2016r4.1, and now 2017r1. We can click on the same window in 2016r3, see it, make changes to it and it does not crash XOJO.
Anyone else run into this behavior or what might be causing it.
Submitting a bug report + project is probably the best bet
Make it private so only you and we can see it
Norman
We’d really like to do that, but our application is high propriety and we probably can’t do that.
Incidentally, in the Mac version of XOJO, we can view and edit the window so it’s obviously something in the Windows version of XOJO.
Any other ways to diagnose this? Debugview?
Anything submitted to us is basically under NDA
And it may not be that an entire app is needed
Just copy the Window into another project and see if that still causes the error in that project
If so submitting that, without the rest of the app, would be sufficient for us to see whats up
DebugView is unlikely to tell you much