Re: How I learned to love and use auto quotes & parentheses with LC 9 DP11

One other useful tidbit is that it will skip over the ending quote if you type it... so when you type “ and get “|”, you can type “text|” and then the next quote will skip over the automatically added one. (“|” is the insertion point) On Sun, Jan 21, 2018 at 8:09 AM Martin Koob via use-livecode <

How I learned to love and use auto quotes & parentheses with LC 9 DP11

Maybe I am the last person to know this but if you don't this may be helpful. I was getting frustrated with the new feature that automatically puts the end quote when you type the initial quote. It works fine if you are typing the initial quote first and then the text contained within the

Re: Do script-only stacks support "chained" behaviors?

That's a nice idea about the warnings. On Sun, Jan 21, 2018 at 3:30 PM, Monte Goulding via use-livecode < use-livecode@lists.runrev.com> wrote: > Cool, scriptifier was/is just a tool I wrote because it took about the > same about of time to write as to tediously scriptify a stack so I thought >

Re: Do script-only stacks support "chained" behaviors?

Another key difference in our implementations that I find fascinating: you create script-only stacks by creating the stacks, then saving the stacks. I created them by constructing a variable with the text contents of the stacks, then writing that out to files with put into url etc. On Sun, Jan

Re: Do script-only stacks support "chained" behaviors?

Also, status update: grr. I'm finding that the answer dialog I'm using to warn the user that the script conversion process is dangerous and to work on a backup is causing my script to die, no warning, and no error message. The exact same script *not* running in Navigator works fine. Answer dialogs

Re: Do script-only stacks support "chained" behaviors?

It occurs to me that this isn't as much of a problem as I thought -- any button being converted to a stack is highly unlikely to have an openstack handler already in it, and therefore it would be safe to add one and include setting the behavior of the script-only stack to the appropriate stack up

Re: Do script-only stacks support "chained" behaviors?

Cool, scriptifier was/is just a tool I wrote because it took about the same about of time to write as to tediously scriptify a stack so I thought it would be a win in the end. If anyone is keen to make it more robust or start from scratch then have at it. FWIW it would probably be a good idea

Re: Do script-only stacks support "chained" behaviors?

As long as you're at it, it would be cool if you added an option to organize the SOS's the way Levure would. I was working on Scriptifier to do the same thing, but I haven't gotten around to finishing it. If Navigator does it, then I can just stop fiddling with my hack. On Sun, Jan 21, 2018 at

Re: Do script-only stacks support "chained" behaviors?

How does Levure organize SOS's? The present setup already allows the user to specify a target folder into which to place the newly created stacks, and correctly sets the relative path in the stackfiles property. On Sun, Jan 21, 2018 at 1:34 PM, Mike Kerner via use-livecode <

Re: Do script-only stacks support "chained" behaviors?

Double-grrr. I put the warning dialogs in the menuPick handler instead of the conversion handler, and it works fine. That's *not* where the warnings should be, since it means that it's possible to call the conversion handler and receive no warnings. I'm testing further. Once I'm comfortable enough

Re: Do script-only stacks support "chained" behaviors?

Heisenbug -- as far as I remember the last twenty minutes, the sequence of edits was: 1. Answer commands die without warning 2. Wrap the problematic answer commands in a try...catch structure. 3. Run the command; get no error from the try, and the command runs all the way through. 4. Comment out

Re: How I learned to love and use auto quotes & parentheses with LC 9 DP11

Martin, thanks for this information. Helps me to like this completion option much more. Matthias > Am 21.01.2018 um 15:08 schrieb Martin Koob via use-livecode > >: > > Maybe I am the last person to know this but if you

Switcheroo

I have a list field where each line may contain a number or be empty. I need a SWITCH statement that checks the state of each line . . . This is throwing a "bluey": switch line number of fld "MM" is empty Where am I going wrong? Richmond. ___

Re: Switcheroo

You aren't actually providing a line number. Try this.. repeat with i = 1 to the number of lines in field "mm" switch (line i of fld "mm" is empty) case true break case false break end switch end repeat Though if you have a LOT of lines you'd be better off adjusting it to use

Re: How I learned to love and use auto quotes & parentheses with LC 9 DP11

Speaking of auto-insertions, is there something in 9dp11 that blocks cmd-shift-space? A custom insertion I use no longer works. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On January 21, 2018 8:11:09 AM

Re: Switcheroo

Thank you very much: I'll get back to work. Richmond. On 21/1/2018 6:35 pm, Mike Bonner via use-livecode wrote: You aren't actually providing a line number. Try this.. repeat with i = 1 to the number of lines in field "mm" switch (line i of fld "mm" is empty) case true break