Re: Quitting with the close box on Mac

On 29 May 2014, at 12:38 pm, J. Landman Gay wrote: > I find Mavericks auto-save pretty useless actually. When you go back into > their time machine interface you can only see the first page of the document > (and nothing at all for many types of files.) […] If you do a “Revert to…” from a Page

Re: Quitting with the close box on Mac

On 5/28/2014, 6:51 PM, Björnke von Gierke wrote: Just imagine, never hitting save, but always having a save of every change you ever made within the stack itself, without cluttering your disk and filesystem with dozens of saves Like HyperCard did. I was never so glad to get rid of auto-save as

Re: South Florida LiveCode User Group

Skip Kimpel wrote: > I am exploring setting up a LC user's group down here in South > Florida. I am in the Ft. Lauderdale region and am trying to > gauge interest and determine how many LC developers we have in > this area. You may also want to post a note in the User Groups section of the for

South Florida LiveCode User Group

Good evening everybody, I am exploring setting up a LC user's group down here in South Florida. I am in the Ft. Lauderdale region and am trying to gauge interest and determine how many LC developers we have in this area. Please respond to let me know if you are interested. SKIP KIMPEL _

Re: Quitting with the close box on Mac

Björnke von Gierke wrote: > Ah! Well, I thought you where quite rambly there, and the point was > actually a simple one. So that's why I did that. I regret nothing. 😈 There's nothing to regret. On the contrary, many of my posts do tend to get longer than needed. You have a good editorial eye.

Re: Quitting with the close box on Mac

Ah! Well, I thought you where quite rambly there, and the point was actually a simple one. So that's why I did that. I regret nothing. 😈 On 29 May 2014, at 02:01, Richard Gaskin wrote: > > My Version? Excuse me? What? > > Consider it a customized summary. :) > >

Re: Quitting with the close box on Mac

Björnke von Gierke wrote: > On 28 May 2014, at 19:19, Richard Gaskin wrote: > >> stephen barncard wrote: >>> This dumbing down crap should be optional, not forced on us. >> >> Björnke version: Options can get expensive over time, introducing a >> form of technical debt. >> >> TL/DR version: >>

Re: Quitting with the close box on Mac

My Version? Excuse me? What? A minor annoyance on Mavericks is that Text Edit does indeed close automatically when the last text file is closed, slightly less annoying, so does preview. Sadly, I do expect more apps to follow in the next version of OS X. I do like the new saving behaviour tho,

Re: Quitting with the close box on Mac

On 5/28/2014, 4:35 AM, divya navaneeth wrote: Respected Sirs, I am new in livecode .Could you plz tell me hoe can we search for certain words or chars inside a textile and deleting unwanted words The easiest way is to use the "replace" function to replace the words you don't want with empty:

Re: LiveCode 7.0.0-DP-5 Linux

On 28/05/14 21:53, Richard Gaskin wrote: Fraser Gordon wrote: > All LiveCode does during the install is to re-launch itself using > gksu: > > gksu --preserve-env /path/to/installer.x86 $MAGIC_INSTALLER_OPTIONS > > The installer relies on the gksu programme to do the authentication > and authorisa

Re: LiveCode 7.0.0-DP-5 Linux

Fraser Gordon wrote: > All LiveCode does during the install is to re-launch itself using > gksu: > > gksu --preserve-env /path/to/installer.x86 $MAGIC_INSTALLER_OPTIONS > > The installer relies on the gksu programme to do the authentication > and authorisation magic; it can't really influence how

Re: LiveCode 7.0.0-DP-5 Linux

On 28/05/14 18:22, Fraser Gordon wrote: On 28 May 2014, at 15:01, Richard Gaskin wrote: The "You Only" requirement when installing under a non-admin account seems an unnecessary drag. When I install any .deb file I'm prompted to enter an admin password, but the LC installer only prompts for

Re: iOS: Wait Time less than 1 millisecond?

Let us know how that works on iOS. That is, whether ‘the long seconds’ has the resolution you want and whether 'wait 0.00025 seconds' works. Another thing to try is ‘send … in 0.00025 seconds’ if the above does not work. Send actually has a lower overhead than you might expect, well, less than

Re: Quitting with the close box on Mac

stephen barncard wrote: This dumbing down crap should be optional, not forced on us. Björnke version: Options can get expensive over time, introducing a form of technical debt. TL/DR version: -- Richard Gaskin Fourth World

Re: iOS: Wait Time less than 1 millisecond?

Hi Dar, Sorry, I should have told you it is for iOS. The good news is that ’the long seconds' is supposed to work for iOS according to the documentation. I’ll give it a try. I’ll look for darzTimer plugin too at your link. Thanks! Rick On May 28, 2014, at 12:55 PM, Dar Scott wrote: > On O

Re: 7.0.0 dp 5

Exactly what happened to me, but I've never seen it. That's what makes me think there's a difference between the commercial and community notifications. On May 28, 2014 8:54:10 AM CDT, Richard Gaskin wrote: > >I had a client recently refer to a "stable" build of 7.0, but >everything >I can

Re: Quitting with the close box on Mac

Except for Preview, which is document based but auto-closes. It seems there is no firm rule about this but in general Apple is following the established behavior. I guess I'll do the same, partly for consistency and partly because I prefer it. On May 28, 2014 2:37:36 AM CDT, Igor de Oliveira

Re: Wait Time less than 1 millisecond?

On OS X, you can use ‘the long seconds’. On Windows and with a commercial LiveCode, you might be able to use darzTimer plugin to help with measuring looping delays. I haven’t looked at that in years. Find it here: http://pages.swcp.com/dsc/revstacks.html It is a plugin stack with an embedded

Re: Wait Time less than 1 millisecond?

Hi. Try waiting 0 (with messages?) Zero is not quite zero. I have no idea if a small loop, waiting 0 one or more times, might actually give you a fraction of a mS. This would be an interesting experiment. Craig Newman -Original Message- From: Rick Harrison To: How to use LiveCode

Re: 7.0.0 dp 5

The file format has changed, so stacks saved in 7.0 can't be opened again in previous versions. Is that what happened? This is the second time I've heard someone say that 7.0 was stable. I thought we were still at dp. I wonder if the community edition is reporting incorrectly in the updater

This session has timed out

Here's a new one. On launching Livecode I see "This session has timed out" ...and no matter what license I enter it endlessly cycles the same dialog. Ideas anyone? ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to

Wait Time less than 1 millisecond?

Hi there, I’m trying to speed up my application by reducing my wait times. Unfortunately, the wait command itself says that the minimum wait time is 1 millisecond. I want to reduce my wait times to .5 or .25 milliseconds. I’m thinking perhaps a loop to wait just a few cpu cycles. It would be b

Re: LiveCode 7.0.0-DP-5 Linux

On 28 May 2014, at 15:01, Richard Gaskin wrote: > > The "You Only" requirement when installing under a non-admin account seems an > unnecessary drag. When I install any .deb file I'm prompted to enter an > admin password, but the LC installer only prompts for the current account and > requir

Re: sloooowww standalone building with many included files

No, this one hasn’t been submitted yet. The app is about 85 MB, maybe around 90 once we’re all done with the audio. Very small audio files. Just a narrator saying a single word in each one. We’ve done this kind of thing before and never had any problems. On May 27, 2014, at 2:49 PM, Bob Sneida

Re: 7.0.0 dp 5

Phil Jimmieson wrote: Currently, if you save a stack with version 7 of LiveCode and try and open it with version 6.6.1 (for example) you get the message: "Unable to open stack: Stack is corrupted, check for ~ backup file." Could Rev not get LiveCode to read the version number off the stack wh

Re: 7.0.0 dp 5

I'd be willing to bet it wasn't a corrupted stack, merely the result of the scary message you get when LC tries to load a stack saved with a later version - e.g. if it is saved with 7.0 and later you try to load it with 6.6 -- Alex. On 28/05/2014 14:54, Richard Gaskin wrote: Paul Foraker wro

Re: 7.0.0 dp 5

Currently, if you save a stack with version 7 of LiveCode and try and open it with version 6.6.1 (for example) you get the message: "Unable to open stack: Stack is corrupted, check for ~ backup file." Could Rev not get LiveCode to read the version number off the stack when it tried to open it a

Re: LiveCode 7.0.0-DP-5 Linux

Richmond wrote: On 27/05/14 12:06, Fraser Gordon wrote: Hi all, There have been a number of problems reported with the Linux builds of LiveCode 7.0.0-DP-5. As far as I've been able to tell, these were due to a build problem that resulted in DP4 being re-packaged as DP5. I've now re-built and

Re: 7.0.0 dp 5

Paul Foraker wrote: When I opened a couple of large stacks I use every day in the "stable" version of 7.0 CE, both stacks got corrupted on the first save. This happened twice in a row, so I've now gone back to 6.5.2. I had a client recently refer to a "stable" build of 7.0, but everything I ca

Re: Quitting with the close box on Mac

-- Forwarded message -- From: divya navaneeth Date: Wed, May 28, 2014 at 3:05 PM Subject: Re: Quitting with the close box on Mac To: How to use LiveCode Respected Sirs, I am new in livecode .Could you plz tell me how can we search for certain words or chars inside a paragraph

Re: Quitting with the close box on Mac

Respected Sirs, I am new in livecode .Could you plz tell me hoe can we search for certain words or chars inside a textile and deleting unwanted words Thank you in Advance > > -- Divya S Sathyan RSGP Condulting pVt ltd ___ use-livecode mailing list

Re: Quitting with the close box on Mac

I understand how you feel: On 28 May 2014, at 5:43 pm, stephen barncard wrote: > Sorry, I don't buy that. The changes just require more stupid clicking > than needed to do what was easy before. I can take care of my own file > management, thank you, and I hate this intrusion into my workflow

Re: Quitting with the close box on Mac

On Tue, May 27, 2014 at 8:26 PM, Igor de Oliveira Couto wrote: > unnecessary annoyance. But I have to admit, that after watching new users > play with these features, they ARE easier to learn - all the confusion > about when to use ‘Save/Save as…’ is gone, and they find using Duplicate > and Rever

Re: Quitting with the close box on Mac

On 28 May 2014, at 1:54 pm, Kay C Lan wrote: > On my 10.9.3 a slew of Apple and non-Apple apps all remain open after > I've closed the last window. The one's that do auto-close seem to be > sensible ones: System Preferences for many versions of OS X has > auto-closed when the window was closed, n