Re: Possible enhancement request

On 11/2/2023 11:20 AM, Klaus major-k via use-livecode wrote: Hi friends, before I post an enhancment request to the "Qualtiy Center", I wanted to hear your opinions about this. Wouldn't it be great if ALL widgets would receive and handle at least a mouseup (and mousedown) meassage? I have

Re: Possible enhancement request

Hi all, I filed an enhancement request for this with some more examples: Best Klaus > Am 02.11.2023 um 17:01 schrieb J. Landman Gay via use-livecode > : > > +... > > I can never keep all those variations straight. > -- > Jacqueline

Re: Possible enhancement request

+... I can never keep all those variations straight. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On November 2, 2023 10:21:29 AM Klaus major-k via use-livecode wrote: Hi friends, before I post an enhancment request to the

Re: Possible enhancement request

for good or bad, the lcb style guide section on events as excerpted, here says that those events are recommended, but not required. in many of those widgets, it would also be nice if there was a way to

Possible enhancement request

Hi friends, before I post an enhancment request to the "Qualtiy Center", I wanted to hear your opinions about this. Wouldn't it be great if ALL widgets would receive and handle at least a mouseup (and mousedown) meassage? I have always wondered why that is not the case. This way scripting

Re: Possible enhancement

On 02/28/2016 08:07 AM, Dr. Hawkins wrote: At the moment, I need to tag my "end repeat"s as you do here; even better would be "end repeat looppyloop", so that mismatches would throw errors. I like that as well - it makes a complete set. And tagging the "end repeat"s that way is especially

Re: Possible enhancement

On 02/28/2016 10:34 AM, Peter Haworth wrote: I use a true/false flag which has to be checked at each control structure level. As far as I know, that's the only way, but maybe not... Yeah, I think setting/checking a semaphore is the workaround. But every time I have to use a semaphore I think

Re: Possible enhancement

>> Peter H. wrote: >> The php break statement has a numeric argument that defines how many >> control structures to break out off I sometimes find myself in 3 or 4 >> nested repeat statements and need to get out of the whole structure if a >> particular condition is met in one of the inner

Re: Possible enhancement

On Sat, Feb 27, 2016 at 1:21 PM, Mark Wieder wrote: > What I'd rather see, and I think Robert Calliau has suggested this before, > is the ability to have named loops. Then you could exit from a loop by > specifying its name. > Yes; this is how modern Fortran does it.

Re: Possible enhancement

+1 -- Peter Peter M. Brigham pmb...@gmail.com http://home.comcast.net/~pmbrig On Feb 27, 2016, at 4:21 PM, Mark Wieder wrote: > On 02/27/2016 12:53 PM, Peter Haworth wrote: > >> Worth an enhancement request? > > What I'd rather see, and I think Robert Calliau has suggested this before, is >

Re: Possible enhancement

I like that better. It's more inline with LC's English-like structure. It also removes a potential problem with the break number if you add or remove a control structure. Is there already an enhancement request for it? On Sat, Feb 27, 2016 at 1:21 PM Mark Wieder wrote:

Re: Possible enhancement

On 02/27/2016 12:53 PM, Peter Haworth wrote: Worth an enhancement request? What I'd rather see, and I think Robert Calliau has suggested this before, is the ability to have named loops. Then you could exit from a loop by specifying its name. repeat . as outerLoop repeat. as

Possible enhancement

Following on from my post about the ability to enclose strings in single quotes, I came across another php feature which I think would be useful in LC. The php break statement has a numeric argument that defines how many control structures to break out off I sometimes find myself in 3 or 4