Re: Exit without quitting

I also use this all the time and have not seen this problem. Which version of LiveCode are you using? - Andy Piddock My software never has bugs. It just develops random features. TinyIDE a Free alternative minimalist IDE Plugin for LiveCode TinyIDE Script editor Themer for LC

Re: Exit without quitting

That definitely sounds like some weird situation or bug. Exit to top is my default exit when I hit some bad condition, and I have never had an app crash on me when I did it. On Wed, Jan 18, 2017 at 9:11 PM, Craig Newman via use-livecode < use-livecode@lists.runrev.com> wrote: > I use exit to

Re: Exit without quitting

I use exit to top all the time in a standalone. Just habit, since exit "handler" would do in many cases. But never had it quit. Still in v. 6.7 if that makes a difference. Sent from my iPhone > On Jan 18, 2017, at 6:33 PM, Monte Goulding via use-livecode >

Re: Exit without quitting

> On 19 Jan 2017, at 11:20 am, Bob Sneidar via use-livecode > wrote: > > That is to say, it QUITS the app. BTW this "feature" is not documented. If > it's not supposed to quit the app, I can report it as a bug, but I recall > past conversations about this I

Re: Exit without quitting

Hi Bob, What happens in a standalone if you just "exit " instead of "exit to top" ? Of course that could cause problems in some contexts. Phil Davis On 1/18/17 4:20 PM, Bob Sneidar via use-livecode wrote: That is to say, it QUITS the app. BTW this "feature" is not documented. If it's not

Re: Exit without quitting

That is to say, it QUITS the app. BTW this "feature" is not documented. If it's not supposed to quit the app, I can report it as a bug, but I recall past conversations about this I think. Bob S On Jan 18, 2017, at 16:15 , Bob Sneidar via use-livecode

Exit without quitting

In the IDE if you exit to top, all script execution stops. In a standalone, it wuits the app. I need a way to stop script execution without quitting the app. Is there an easy way, or will I have to return a value all the way up the script hierarchy to tell the initial handler to sop running?

Re: Zippy-da-doo-dah 8.1.3

Ye and Amen! Bob S On Jan 18, 2017, at 09:41 , Stephen Barncard via use-livecode > wrote: . We have other interests and use livecode to support their complexities. We want to get to the "thing" that accomplishes our task and

Re: Nightly Builds

Here it is: Nightly Builds discussion On Wed, Jan 18, 2017 at 12:41 PM, Roger Eller wrote: > Just a few days ago, nightly builds were being discussed. Some thought it > would take too long

Re: Zippy-da-doo-dah 8.1.3

On Wed, Jan 18, 2017 at 8:56 AM, Richmond Mathewson via use-livecode < use-livecode@lists.runrev.com> wrote: > And all that I am twitched about at the moment is finding a properly > documented list of the conjunct > consonants for the Siddham writing system: suddenly my burden feels about > 1000

Re: Nightly Builds

Just a few days ago, nightly builds were being discussed. Some thought it would take too long to automate the process enough to provide nightly builds. Monte chimed in with the fact that nightly builds are already automated, but are not published to everyone. I think he said they were available

Re: Zippy-da-doo-dah 8.1.3

If it is a line, then technically it has no beginning or end point. You must mean a line segment or a ray. ;-) Bob S On Jan 18, 2017, at 09:20 , Richard Gaskin via use-livecode > wrote: Ali Lloyd wrote: > Of course at some

Re: Zippy-da-doo-dah 8.1.3

Ali Lloyd wrote: The reason it doesn't show up on GitHub is that it will only appear on GitHub when there is a pull request, which is usually only when it is fixed. What you need is http://quality.livecode.com/buglist.cgi?list_id=67534_format=advanced_milestone=8.1.3-rc-1 Not everything in

Re: Zippy-da-doo-dah 8.1.3

Richmond Mathewson wrote: > Well, even if nothing else I am beginning to understand just how > complicated LiveCode development is . . . Amen to that, brother. I find that complaints about the LC engine often tend to occur in inverse proportion to the poster's experience in multi-platform C

Re: Zippy-da-doo-dah 8.1.3

Ali Lloyd wrote: > Of course at some point you have to draw a line, but the > aformentioned bug is well beneath* it. > > *I'm not sure when you metaphorically draw a line, whether that line > is meant to be horizontal or vertical, or indeed which side of the > line you start from We're bike

Re: Zippy-da-doo-dah 8.1.3

Well, even if nothing else I am beginning to understand just how complicated LiveCode development is . . . And all that I am twitched about at the moment is finding a properly documented list of the conjunct consonants for the Siddham writing system: suddenly my burden feels about 1000 times

Re: Zippy-da-doo-dah 8.1.3

The reason it doesn't show up on GitHub is that it will only appear on GitHub when there is a pull request, which is usually only when it is fixed. What you need is http://quality.livecode.com/buglist.cgi?list_id=67534_format=advanced_milestone=8.1.3-rc-1 Not everything in that list actually

Re: Zippy-da-doo-dah 8.1.3

Hi Richmond, Github shows all the bugs for which a PR has been submitted. So if no PR has been submitted for a blocker, it will not show up. The blocker Ali was referring to in his previous post is now fixed ( https://github.com/livecode/livecode/pull/5071). However, unfortunately, yesterday we

Re: Nightly Builds

On 1/18/17 6:30 pm, Richmond Mathewson wrote: Mooching around, as I tend to from time to time, on the LiveCode website, I came across this: https://livecode.com/resources/release-process/ "Release Frequency: RCs (Release candidates) every 1-3 days Stable versions every 2-4 weeks (Nightly

Nightly Builds

Mooching around, as I tend to from time to time, on the LiveCode website, I came across this: https://livecode.com/resources/release-process/ "Release Frequency: RCs (Release candidates) every 1-3 days Stable versions every 2-4 weeks (Nightly builds available)" Which is either horribly out of

Re: Zippy-da-doo-dah 8.1.3

One thing I don't understand is, if there is a blocker, why it does not show up on Github: https://github.com/livecode/livecode/milestone/126 I wonder if there is a way people like me can track all the dependencies ( i.e. those mentioned inwith GitHub and those that seem to be outwith GitHub)

Re: Code signing - not out of the wood yet: please help!

Bill, thanks for staying with me. I will report on my success, if I have any… Cheer Graham > On 17 Jan 2017, at 22:55, William Prothero via use-livecode > wrote: > > I “think” that once you get the certificate into keychain, you no longer need > to worry about

RE: [OT] Website Design Apps-Mac

To minimize the brutal attacks of WP sites is to change the default wp-admin folder to something else. The safest way to do this is via the WP plugin: https://wordpress.org/plugins/rename-wp-loginphp-to-anything-you-want/ All the best, Erik Beugelaar -Original Message- From:

Re: International LiveCode Mini Conference

The LiveCode conference in Antwerp will take place on 25th February 2017. Please, reserve the date in your agenda. More information will follow shortly. Kind regards, Mark Schonewille http://economy-x-talk.com https://www.facebook.com/marksch Buy the most extensive book on the LiveCode

AW: What has changed in MacOS 10.12 in handling code pages?

Hi Kay C, Good guess, but it's a stack with the old standard LC font Tahoma, which was installed on my machine with OS X 10.11 and still is installed in 10.12. The issue also occurs in answer dialogs, where I havn't (can't) explicitely set the font. And the problem only occurs in standalones of <=