Re: Button scripts

2019-10-05 Thread dunbarx--- via use-livecode
on mouseUp if the name of the target has some nice property thenset the bordercolor of the Target to "orange"... Craig -Original Message- From: General 2018 via use-livecode To: use-livecode@lists.runrev.com Cc: General 2018 Sent: Sat, Oct 5, 2019 12:57 pm Subject: Button

Button scripts

2019-10-05 Thread General 2018 via use-livecode
Hi , Have many buttons that do different operations , each one has the following script :- Is the script required for each button and is the use of flush correct ? on mouseUp set the bordercolor of me to orange set showBorder of me to true --- do something get flushEvents("mouseUp") end

Re: Preference for Keeping Saved Empty Button Scripts Empty

2017-06-21 Thread Mike Bonner via use-livecode
Cool! thanks Monte! On Wed, Jun 21, 2017 at 5:48 PM, Mark Talluto via use-livecode < use-livecode@lists.runrev.com> wrote: > > On Jun 21, 2017, at 4:40 PM, Monte Goulding via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > > Hi Guys > > > > I have done _some_ work on an

Re: Preference for Keeping Saved Empty Button Scripts Empty

2017-06-21 Thread Mark Talluto via use-livecode
> On Jun 21, 2017, at 4:40 PM, Monte Goulding via use-livecode > wrote: > > Hi Guys > > I have done _some_ work on an autocomplete framework which could also be used > for a snippet library. It is something we have on the radar to complete and > integrate into

Re: Preference for Keeping Saved Empty Button Scripts Empty

2017-06-21 Thread Monte Goulding via use-livecode
> On 22 Jun 2017, at 3:20 am, Mike Bonner via use-livecode > wrote: > > Perhaps a different direction here? I think it would be helpful to me as a > perpetual newbie to have the option to insert common scripts on demand. > Maybe a context sensitive dropdown with

Re: Preference for Keeping Saved Empty Button Scripts Empty

2017-06-21 Thread Alex Tweedly via use-livecode
You're right, not a good solution for newcomers. However, I think there's a (perhaps minority) class of newcomers - more or less, those who come as experienced developers in another language / IDE - for whom a good setup would include ST + linter + just enough of Levure to provide the

Re: Preference for Keeping Saved Empty Button Scripts Empty

2017-06-21 Thread Mike Kerner via use-livecode
I am using ST and Levure, now, and I have the linter working, and am a cheerleader for the setup. However, that is not a good solution for beginners, IMHO. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe,

Re: Preference for Keeping Saved Empty Button Scripts Empty

2017-06-21 Thread Alex Tweedly via use-livecode
Why not just use Sublime Text editor, with Levure to allow you to use an external editor? (or plug in to that system to allow other external editors to be used) Other than the fact that I can't get the 'linter' to work (and I know that'll just be me doing something stupid and wrong :-), it

Re: Preference for Keeping Saved Empty Button Scripts Empty

2017-06-21 Thread Mike Kerner via use-livecode
I like the idea of going even another step further, and having macros that we can use. An example from another tool I use adds the ability to add structures (e.g. if-then-else, repeat, etc.), and even being able to hilite text and have the macro do something with the text, for example

Re: Preference for Keeping Saved Empty Button Scripts Empty

2017-06-21 Thread Richard Gaskin via use-livecode
Mike Bonner wrote: > Perhaps a different direction here? I think it would be helpful to me > as a perpetual newbie to have the option to insert common scripts on > demand. > Maybe a context sensitive dropdown with a mouseup framework for > buttons, for fields, textchanged, keyup, keydown.

Re: Preference for Keeping Saved Empty Button Scripts Empty

2017-06-21 Thread ELS prothero via use-livecode
What about Mike Doub’s MasterLibrary? I just tried it in latest LC, and it fails because there is a function named a reserved word. But, it seems like a valuable resource that might be used as a starting point? Best, Bill William Prothero, PhD Professor Emeritus University of California, Santa

Re: Preference for Keeping Saved Empty Button Scripts Empty

2017-06-21 Thread Richard Gaskin via use-livecode
Making scripted elements is a great thing for scripters to do. And the one thing we all have in common here is that we're all scripters. There should be no need to make LC Ltd's C++ experts set aside work on the engine to build these instead. What prevents any of us from delivering those?

Re: Preference for Keeping Saved Empty Button Scripts Empty

2017-06-21 Thread Mike Bonner via use-livecode
Perhaps a different direction here? I think it would be helpful to me as a perpetual newbie to have the option to insert common scripts on demand. Maybe a context sensitive dropdown with a mouseup framework for buttons, for fields, textchanged, keyup, keydown. Maybe backed by a personal snippet

Re: Preference for Keeping Saved Empty Button Scripts Empty

2017-06-21 Thread Andre Garzia via use-livecode
Going back to the original issue of "not applying the empty mouseup handler", wouldn't a frontscript running on a plugin on the IDE be enough to remove those scripts by interfeering with the IDE Editor at runtime? (PS: I have a thing for dangerous scripts...) On Wed, Jun 21, 2017 at 12:03 PM,

Re: Preference for Keeping Saved Empty Button Scripts Empty

2017-06-21 Thread Sannyasin Brahmanathaswami via use-livecode
Kevin, Thanks for jumping in, very inspiring work you have all been doing recently. One has to wonder if anyone sleeps in Edinborough! I've been having a running conversation with Richard on how to make small solutions available to the whole community, in the spirit of "this would make

Re: Preference for Keeping Saved Empty Button Scripts Empty

2017-06-20 Thread Kevin Miller via use-livecode
How to use LiveCode <use-livecode@lists.runrev.com> >> Subject: Re: Preference for Keeping Saved Empty Button Scripts Empty >> Message-ID: >> <cadcoycohgntezjx8voym6ywjhnznenvjghjzuxhkezxeflp...@mail.gmail.com> >> Content-Type: text/plain; charset="UTF-8"

Re: Preference for Keeping Saved Empty Button Scripts Empty

2017-06-20 Thread Mike Kerner via use-livecode
Which is exactly why this is a better idea. Kickstarter releases the funds when the funding goal is achieved, not when the product is finished. This idea is the reverse. 1. We set up the account 2. We fund the account 3. We administer the account 4. We decide which projects we want to fund at

Re: Preference for Keeping Saved Empty Button Scripts Empty

2017-06-20 Thread Richmond Mathewson via use-livecode
Subject: Re: Preference for Keeping Saved Empty Button Scripts Empty Message-ID: <cadcoycohgntezjx8voym6ywjhnznenvjghjzuxhkezxeflp...@mail.gmail.com> Content-Type: text/plain; charset="UTF-8" and another case where we should have a little crowd fund setup. On Mon, Jun 19, 2017 at

Re: Preference for Keeping Saved Empty Button Scripts Empty

2017-06-20 Thread Andrew Bell via use-livecode
<mikeker...@roadrunner.com> To: How to use LiveCode <use-livecode@lists.runrev.com> Subject: Re: Preference for Keeping Saved Empty Button Scripts Empty Message-ID: <cadcoycohgntezjx8voym6ywjhnznenvjghjzuxhkezxeflp...@mail.gmail.com> Content-Type: text/plain; charset="UTF-8&q

Re: Preference for Keeping Saved Empty Button Scripts Empty

2017-06-20 Thread Sannyasin Brahmanathaswami via use-livecode
A work in progress http://quality.livecode.com/show_bug.cgi?id=19905 On 6/19/17, 2:35 PM, "use-livecode on behalf of Sannyasin Brahmanathaswami via use-livecode" wrote: ha… that's a simple hack… I

Re: Preference for Keeping Saved Empty Button Scripts Empty

2017-06-19 Thread Sannyasin Brahmanathaswami via use-livecode
ha… that's a simple hack… I might use # instead… though these all start showing up in PB as have in a 1 line script.. which I guess is server explanatory. panos wrote me back today say he thinks the default behavior is good for newbies. which it probably is. Theoretically the IDE *could*

Re: Preference for Keeping Saved Empty Button Scripts Empty

2017-06-19 Thread Mike Kerner via use-livecode
and another case where we should have a little crowd fund setup. On Mon, Jun 19, 2017 at 4:00 PM, Bob Sneidar via use-livecode < use-livecode@lists.runrev.com> wrote: > +1 > > > On Jun 19, 2017, at 12:49 , J. Landman Gay via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > > Right,

Re: Preference for Keeping Saved Empty Button Scripts Empty

2017-06-19 Thread Bob Sneidar via use-livecode
+1 > On Jun 19, 2017, at 12:49 , J. Landman Gay via use-livecode > wrote: > > Right, but every time you open the script and then close it again, it keeps > asking if you want to save the default. It gets irritating. > > I sometimes just replace the default

Re: Preference for Keeping Saved Empty Button Scripts Empty

2017-06-19 Thread J. Landman Gay via use-livecode
On 6/19/17 12:58 PM, Paul Hibbert via use-livecode wrote: On Jun 19, 2017, at 8:19 AM, Sannyasin Brahmanathaswami via use-livecode wrote: so, does it make sense to request a feature enhancement to add a preference to*not* insert any handler in buttons/widgets,

Re: Preference for Keeping Saved Empty Button Scripts Empty

2017-06-19 Thread Mike Kerner via use-livecode
e support "complaining" that after I clear the > > on mouseup > > end mouseUp > > that is inserted in button scripts by default, apply, close, save. Then > later if one inadvertently opens the script of that button, the script is > reinserted. Panos replied this is the def

Re: Preference for Keeping Saved Empty Button Scripts Empty

2017-06-19 Thread Paul Hibbert via use-livecode
On Jun 19, 2017, at 8:19 AM, Sannyasin Brahmanathaswami via use-livecode wrote: > > so, does it make sense to request a feature enhancement to add a preference > to *not* insert any handler in buttons/widgets, whose scripts are empty if > inadvertently opened?

Preference for Keeping Saved Empty Button Scripts Empty

2017-06-19 Thread Sannyasin Brahmanathaswami via use-livecode
I wrote support "complaining" that after I clear the on mouseup end mouseUp that is inserted in button scripts by default, apply, close, save. Then later if one inadvertently opens the script of that button, the script is reinserted. Panos replied this is the default behavior….gave