Jacque --
Thanks so much!
The two lines of code that you recommended be added immediately after the answer command did indeed resolve the problem. Upon clicking the "OK" button in the answer dialog, the test items again responded to keyboard presses without first needing to click on the frontmost window.
I'm still not sure why my original app worked a year or so ago, yet broke now until inserting your two new lines of code. Although I'd like to know, most important is that the app is working again.
Just in case it makes any sense to anyone, one possibility is that because my app required that the entire screen background be set to black, I had to tinker with the background color of the built-in LC "Answer Dialog" stack in order for the dialog window to display with a white background. Perhaps that built-in stack remained the default even after being dismissed.
In any case, I seem to be back on track to complete this app, so I truly appreciate everyone's help.
jeff k
Old standalones work, IDE versions don't
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
-
- VIP Livecode Opensource Backer
- Posts: 7258
- Joined: Sat Apr 08, 2006 8:31 pm
- Location: Minneapolis MN
- Contact:
Re: Old standalones work, IDE versions don't
Changing the backcolor of the answer dialog is a pretty common thing to do and is only cosmetic, so it's doubtful that would interfere, especially if it's done before the dialog displays.
There have been a lot of changes in the last two years, so it's possible you did find a minor bug. It wouldn't hurt to report it and see what the team thinks. Meanwhile I'm glad you have a workaround.
There have been a lot of changes in the last two years, so it's possible you did find a minor bug. It wouldn't hurt to report it and see what the team thinks. Meanwhile I'm glad you have a workaround.
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
-
- Posts: 9
- Joined: Wed Jul 15, 2020 12:38 am
Re: Old standalones work, IDE versions don't
Hello!
did you finish your project? Did you find the cause of the problem? a missing pop card command, a lock message, a group behaving as a background? a dynamic path working differently? a frontscript?
Can you a minimal stack with the same problem?
Thank you!
did you finish your project? Did you find the cause of the problem? a missing pop card command, a lock message, a group behaving as a background? a dynamic path working differently? a frontscript?
Can you a minimal stack with the same problem?
Thank you!
Re: Old standalones work, IDE versions don't
Hi ChristianBC --
In answer to your first question: My project is finished, but not yet published (because I've yet to figure out how to master Apple's ever-more draconian method of signing and authenticating applications).
As regards the cause of the IDE-vs-standalone problem I experienced, the fix suggested by Jacque back on 16 July 2018 worked for me. I've just run the app in the LC 9.5.x IDE and found that everything still works okay.
In case your question was prompted by a problem you've had with trying to run an older stack in a newer LC IDE, I'd just refer back to Jacque's point that the LC IDE has undergone lots of changes over the past few years. Any glitch in your older stack may differ from the one that she spotted in my code, so you might want to post the specifics to a new question in this forum.
jeff k
In answer to your first question: My project is finished, but not yet published (because I've yet to figure out how to master Apple's ever-more draconian method of signing and authenticating applications).
As regards the cause of the IDE-vs-standalone problem I experienced, the fix suggested by Jacque back on 16 July 2018 worked for me. I've just run the app in the LC 9.5.x IDE and found that everything still works okay.
In case your question was prompted by a problem you've had with trying to run an older stack in a newer LC IDE, I'd just refer back to Jacque's point that the LC IDE has undergone lots of changes over the past few years. Any glitch in your older stack may differ from the one that she spotted in my code, so you might want to post the specifics to a new question in this forum.
jeff k