Of course, you can start 'rolling your own' by cloning the IDE stacks then
customizing those clones as you wish.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
However, if you have improvements to make, you can always submit them along
with a bug report.
On Tue, Jan 11, 2022 at 9:40 AM Tom Glod via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Alright, I'll have to add that to my list. Thanks for the hints
> Jacqueline.
>
> On Mon, Jan 10,
Alright, I'll have to add that to my list. Thanks for the hints Jacqueline.
On Mon, Jan 10, 2022 at 7:16 PM Bob Sneidar via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Just roll your own. Any mod to the IDE goes away next time you update.
>
> Sent from my iPhone
>
> > On Jan 10,
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
> 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
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.
Tom.
There was a pretty long thread here about modifying those dialogs. They are
just stacks, after all, but the IDE is protective of them. I think the upshot
was that you can hack anything, but better to roll your own. These would be
just stacks, after all, and you can start with a clean
