![]() My Windows test machine is deliberately low-spec to test my app on a computer that many of my customers might use. I should add, my Mac is current, high-end machine. My MsgBox is a standard Xojo call, nothing modified, and it is called by a method belonging to Window1. Window1 is the only active window at this point. I’m not familiar with threads, but there shouldn’t be anything else going on at this point. What would make a MsgBox display behind a Window? I call the MsgBox after all other processing is done, so no methods working in background. I can’t even kill the app with the debugger, have to use Windows Task Manager. Can’t even move Window1 to show the MsgBox. But OK can’t be clicked because the entire message box is hidden behind Window1. Its modal, so nothing else can happen until OK is clicked. So the entire app hangs, waiting for user to click OK. The MessageDialog class provides a bit more features. On Windows I have a problem: the MsgBox is displayed BEHIND Window1 (I can sometimes see it flash up, then covered by Window1). The easiest way is to use the MessageBox method. A MsgBox is then displayed with simple text string telling user data is ready.Īpp working beautifully (ie as expected) on OSX - msgbox displays, user clicks OK and on we go. ![]() When app starts up, it loads Window1 with a listbox, loads with data and a bit of listbox formatting (cellbackgroundpaint and celltextpaint). ![]() ![]() I have a long-standing app that I am updating to 64 bit, Retina and a few other bits. It contains the native library and source code examples needed to integrate hardware-locked licensing in your Xojo app: Get TurboActivate for Windows. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |