Just roll your own. Any mod to the IDE goes away next time you update. Sent from my iPhone
> On Jan 10, 2022, at 14:48, J. Landman Gay via use-livecode > <use-livecode@lists.runrev.com> wrote: > > I agree with Craig that you're better off making your own. There is a > built-in mechanism for this: the dialogData. It's a generic global property, > always available, specifically for moving data between a modal stack and your > scripts. You don't need to declare it as a global, it's always there. > > Create a stack with the controls you need, and open it as modal. When the > user hits the OK button (or whatever dismisses the stack,) use a closeStack > handler to put the data you need into the dialogData. Your script will pause > when the modal opens and resume when it closes, so you just get the > dialogData in the line after the one that opened the modal. > > Be sure to grab the data in the same handler that opened the modal stack, > because a lot of things use it and it can change often. > > >> On 1/10/22 12:13 PM, Tom Glod via use-livecode wrote: >> Hi Folks, >> Am I allowed to modify the answer and ask dialog stack to be what I need it >> to be? and build my standalones from the modified version? >> and can those modified stacks be shared with others? >> Thanks in advance, > > > -- > Jacqueline Landman Gay | jac...@hyperactivesw.com > HyperActive Software | http://www.hyperactivesw.com > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
