Re: Storing and saving a setting in a stand alone

This restriction in Yosemite causes big issue if you want to hack the LiveCode ide. On Windows the LC ide stacks are stored in a sub directory of the users AppData folder which allows modifications to be made to the LC ide stacks. You cannot now do this in Yosemite and it will prevent any plugins u

Re: Possible insanity, or is it LC 7.0.1?

Yes, verified this - new stack, new button, put this script onto it, and this is what it does. This is Debian, 7.0 Community Edition. Also verified it in multiline message box and tried a couple of other things. What is really weird is that if you just change 1.884956 to 1.88495, it seems to run

Re: Script to Generate Concurrent Times

That is hilarious, in a gruesome way. Bill > On Jan 15, 2015, at 8:10 PM, Simon wrote: > > Then there is this; > https://www.youtube.com/watch?v=-5wpm-gesOY > > Simon > > > > -- > View this message in context: > http://runtime-revolution.278305.n4.nabble.com/Script-to-Generate-Concurrent-Tim

Re: Storing and saving a setting in a stand alone

On 1/15/2015 9:31 PM, Kay C Lan wrote: Yes Scott,you are right it's still a valid method, but it's not a method that works for all platforms and for a product who's key feature is that it is cross platform, desktop and mobile, I see it being counter productive to provide an example that isn't.

Re: Script to Generate Concurrent Times

Then there is this; https://www.youtube.com/watch?v=-5wpm-gesOY Simon -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Script-to-Generate-Concurrent-Times-tp4687781p4687891.html Sent from the Revolution - User mailing list archive at Nabble.com.

The Internet Date on Cento OS / LiveCode Server Returns Zulu Time

Anyone know a) why Livecode returns zulu time (no UTC offset) for the internet date on a web server in San Francisco? b) how to fix that? On my machine (HST) the internet date returns: Thu, 15 Jan 2015 18:00:57 -1000 And the web server (in SF) CentOS shell --- system itself returns the i

Re: Storing and saving a setting in a stand alone

On Fri, Jan 16, 2015 at 8:40 AM, Richard Gaskin wrote: On the contrary, as the rest of your post points out, it's increasingly > useful as OS file system permissions get ever more restrictive. > Yes Scott,you are right it's still a valid method, but it's not a method that works for all platforms

Re: Script to Generate Concurrent Times

Roger Eller wrote: So that's where the old saying, "your singing would bring a jersey cow to tears" comes from. LOL! Hmmm back on topic: Requirement: Generate current time list for a *future* time (for scheduled webinar) OK, so it is easy enough to get world time from the linux system. a

Re: Free IP Calculator

That's a lot of notes to yourself :) Thanks for sharing! SKIP > On Jan 15, 2015, at 6:17 PM, Bob Sneidar wrote: > > Change this line to: > > — usablecount > set the itemdelimiter to “.” > > won’t work without it. Another note to self: Don’t try to modify code posted > in an email. > > Bo

Getting the URL out of

How would I go about getting a random URL out of an XML file like the following? There's several of these CDATA tags. My brain is about to explode. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubsc

Re: How to solve "can't find stack" error

On 14.01.2015 at 17:01 Uhr -0800 tbodine apparently wrote: Hi all. Looking for some insight here... I have a desktop program built in LC 6.5.1 that uses LC stacks as user files for storing user data in fields and cprops. Mostly this works well. However, I get occasional Error Reports when a few

Re: Storing and saving a setting in a stand alone

Kay C Lan wrote: * It would probably be wise for RunRev to remove any mention of the Splash Stack method on their how-to site as it is clearly not an approach that should be used any more. On the contrary, as the rest of your post points out, it's increasingly useful as OS file system permissi

Re: Storing and saving a setting in a stand alone

RunRev may need to edit the description of the method but why remove it? What is preventing developers from placing their primary stacks in the Documents folder or any other writable folder? AFAICT, using the splash stack technique is still valid, but you may not be able to save the stack in a

Re: Storing and saving a setting in a stand alone

On Fri, Jan 16, 2015 at 3:57 AM, Richard Gaskin wrote: > > Why do you suppose this has survived so long with no one discovering it > until now? > Whilst I may be a Mac fanboy, I'm definitely anti-iOSing of OS X. That said, one of the few side effects may be the herding of LCers to store User dat

Re: Free IP Calculator

Change this line to: — usablecount set the itemdelimiter to “.” won’t work without it. Another note to self: Don’t try to modify code posted in an email. Bob S On Jan 15, 2015, at 15:18 , Bob Sneidar mailto:bobsnei...@iotecdigital.com>> wrote: -- usablecountset the itemdelimiter to "

Re: Free IP Calculator

OK I took some time today to really go through this IPCalc function. Note to self: Don’t try to write publicly distributable code quickly. That being said, I’ve been asked to include this function in the library of commands and functions everyone’s been talking about. So I am going to post the

URL affected by default browser?

Is the URL keyword affected by the default browser? It seems that if I do a put url, the result is directly dependent upon the default browser selected by the user. So, for instance, on Windows, with IE as the default, if the URL pointed to an invalid page, I would get an empty result, but if I s

Re: Which version...

Richmond wrote: > On 15/01/15 21:51, Richard Gaskin wrote: >> Throughout the forums and the bugs reports I've been following >> I've seen fairly regular references to Ubuntu 14.04 LTS, the >> most recent Long-Term Support release the project has. > > That's good to know :) > > Last I heard they w

Re: Storing and saving a setting in a stand alone

On 1/15/2015 2:54 PM, J. Landman Gay wrote: my main project is still done in LC 6.5.x Oops, that should be 6.6.5. I'm not THAT far behind. ;) -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com

Re: Storing and saving a setting in a stand alone

On 1/15/2015 1:57 PM, Richard Gaskin wrote: J. Landman Gay wrote: > On 1/15/2015 10:05 AM, Richard Gaskin wrote: >> While the absence of reports related to general file access in the >> bundle would seem to suggest this change was implemented well in the >> engine, René's report shows this w

Re: Which version...

On 15/01/15 21:51, Richard Gaskin wrote: Richmond wrote: >> On 15/01/15 16:34, Dr. Hawkins wrote: >> >> Pretty much standardized. ... >> An RC believes that all bugs are taken care of, and is only making >> sure of this. > > Why do I have a funny feeling that RunRev probably know that? Because

Re: Storing and saving a setting in a stand alone

J. Landman Gay wrote: > On 1/15/2015 10:05 AM, Richard Gaskin wrote: >> While the absence of reports related to general file access in the >> bundle would seem to suggest this change was implemented well in the >> engine, René's report shows this workaround for Apple's new security >> policy need

Re: Which version...

Richmond wrote: >> On 15/01/15 16:34, Dr. Hawkins wrote: >> >> Pretty much standardized. ... >> An RC believes that all bugs are taken care of, and is only making >> sure of this. > > Why do I have a funny feeling that RunRev probably know that? Because they're described in similar terms at the

Re: Storing and saving a setting in a stand alone

On 1/15/2015 10:05 AM, Richard Gaskin wrote: While the absence of reports related to general file access in the bundle would seem to suggest this change was implemented well in the engine, René's report shows this workaround for Apple's new security policy needs to be added to the SQLite external

Re: Which version...

On 15/01/15 20:31, Dr. Hawkins wrote: On Thu, Jan 15, 2015 at 9:49 AM, Richmond wrote: On 15/01/15 16:34, Dr. Hawkins wrote: On Wed, Jan 14, 2015 at 11:56 PM, John Dixon wrote:5.5 if you want stability; it is late-beta quality. Some report stability on 6.6, apparently. 6.7 and 7.0 are lat

Re: Which version...

On Thu, Jan 15, 2015 at 9:49 AM, Richmond wrote: > On 15/01/15 16:34, Dr. Hawkins wrote: > >> On Wed, Jan 14, 2015 at 11:56 PM, John Dixon >> wrote:5.5 if you want stability; it is late-beta quality. >> >> Some report stability on 6.6, apparently. >> >> 6.7 and 7.0 are late and early alpha quali

Re: Which version...

On 15/01/15 16:34, Dr. Hawkins wrote: On Wed, Jan 14, 2015 at 11:56 PM, John Dixon wrote: Yes, but my question really is.. 'What is the reason for having all theses different versions being updated more or less at the same time ?'... Life was much simpler when you knew the version with the lar

Re: Player object

Hi Martin, Thanks for the tip. Unfortunately it doesn't seem to work for audio files, at least with LC 6.6.2 and OSX 10.7.4. That would be a nice feature though. Looks like it could be accommodated by varying the playrate property. Pete lcSQL Software Home of lcStackBrows

Re: Storing and saving a setting in a stand alone

On Thu, Jan 15, 2015 at 8:05 AM, Richard Gaskin wrote: > Hanson's confirmation there suggests they're working on it now, and given > how widely SQLite is used I'd be surprised if the fix isn't in the next > build. Hopefully they will take the opportunity to get the SQLite library up to date. C

Re: Storing and saving a setting in a stand alone

René Micout wrote: >> Le 15 janv. 2015 à 15:17, dunbarx at aol.com a écrit : >> >> You know, recently I tried to make a "splash" standalone in 6.7, >> the first I needed to in a while (the last was in 5.x) and it >> would not work. I thought it was something I was doing wrong, >> but was not on m

Re: Storing and saving a setting in a stand alone

> Le 15 janv. 2015 à 15:17, dunb...@aol.com a écrit : > > Rene. > > > OOOH. > > > You know, recently I tried to make a "splash" standalone in 6.7, the first I > needed to in a while (the last was in 5.x) and it would not work. I thought > it was something I was doing wrong, but was not on m

Re: Storing and saving a setting in a stand alone

Shawn Blc wrote: Can someone point me in the right direction? I want to save a setting in stand alone application. This setting will be different for each person (name). Once it's set, the user won't be prompted to enter again. OSes don't allow applications to modify themselves. Back in the

Re: Which version...

John Dixon wrote: Why are there different versions of liveCode being updated.. LC 7.0- updated 23 October 2014 LC 7.0.1 - updated 18 December 2014 LC 6.7.0 - updated 18 December 2014 LC 6.7.1 - updated 9 January 2015 Which one is considered to be the 'one' to use ? As with most softwa

Re: Which version...

On Wed, Jan 14, 2015 at 11:56 PM, John Dixon wrote: > Yes, but my question really is.. > 'What is the reason for having all theses different versions being updated > more or less at the same time ?'... > Life was much simpler when you knew the version with the largest number > stuck on the end of

Re: Storing and saving a setting in a stand alone

Rene. OOOH. You know, recently I tried to make a "splash" standalone in 6.7, the first I needed to in a while (the last was in 5.x) and it would not work. I thought it was something I was doing wrong, but was not on my front burner to figure out. Anyone else? This is big if true, but how co

Re: Storing and saving a setting in a stand alone

> Le 15 janv. 2015 à 15:08, dunb...@aol.com a écrit : > > Hi. > > > Are you talking about the fact that a single stack, which is the executable > if you save it as a standalone, cannot save to itself? If so, there are > several threads on the forums that address this. My favorite is the "spla

Re: Storing and saving a setting in a stand alone

Hi. Are you talking about the fact that a single stack, which is the executable if you save it as a standalone, cannot save to itself? If so, there are several threads on the forums that address this. My favorite is the "splash stack" method. Look here: Stack data i/o question Craig Ne

Storing and saving a setting in a stand alone

Can someone point me in the right direction? I want to save a setting in stand alone application. This setting will be different for each person (name). Once it's set, the user won't be prompted to enter again. ___ use-livecode mailing list use-livecode@

Re: Player object

Oh forgot to say don't know how this works for audio files. Martin Koob -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Player-object-tp4687755p4687857.html Sent from the Revolution - User mailing list archive at Nabble.com.

Re: Player object

If you hold the shift key and click on the step forward/step backward buttons on the right of the controller you get a scrub control that allows you to vary the player's playrate forward and backward from - 3x to 3x. Martin Koob -- View this message in context: http://runtime-revolution.2783

AW: Which version...

Brave new world -Ursprüngliche Nachricht- Von: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] Im Auftrag von John Dixon Gesendet: Donnerstag, 15. Januar 2015 11:50 An: How to use LiveCode Betreff: RE: Which version... Just made a standalone for a stack I'm working on... fro

RE: Which version...

I believe it's resources needed to make their new handling of UniCode work (also believe they are looking at ways of slimming down file sizes...) John Dixon wrote > from LC 6.7 - 2.8 mb in size > from LC 7.0 - 28.0 mb in size > > Where did all that bloat appear from !? - "Some are bor

RE: Which version...

Just made a standalone for a stack I'm working on... from LC 6.7 - 2.8 mb in size from LC 7.0 - 28.0 mb in size Where did all that bloat appear from !? Dixie > Date: Thu, 15 Jan 2015 02:37:28 -0800 > From: d...@applicationinsight.com > To: use-revolut...@lists.runrev.com > Subject: Re: Which

Re: Which version...

As far as I know (which isn't saying much): LC 6.6.x = maintenance of 'old generation' versions (e.g. carbon) LC 6.7.x = 'new generation' stuff like cocoa, excluding UniCode LC 7.x.x = all 'new generation' stuff, including Unicode LC 6.6 is for working on legacy stacks LC 6.7 is for those wanting

Re: [OT] I'm going to go live in a cave

Whoops, don't know what happened there: http://www.amazon.com/Cyber-Clean-25055-Office-Pop-up/dp/B00375JBL4 ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferen

Re: Which version...

There seems to be another oddity, which is that I just found out that when you report a bug, you’re currently asked which of three or four versions of 7.0.1 you have - but when I look at the version I’m actually using, there’s no reference in the ‘About’ box to any of these versions! FWIW I thin

Re: Possible insanity, or is it LC 7.0.1?

Now reported as a bug (14386) - I’ve included a reference to this thread to show that my observation is backed up by many listers. Thanks everyone. Thanks Jacque for doubting the sanity of SANE. Graham > On 15 Jan 2015, at 10:00, Henk van der Velden wrote: > > I get the same error here, same

Re: Possible insanity, or is it LC 7.0.1?

I get the same error here, same setup: OS X 10.10.1, LC7.0.1 build 10023 So it’s definitely not just you! Henk > On 15 Jan 2015, at 09:12, use-livecode-requ...@lists.runrev.com wrote: > > Message: 6 > Date: Thu, 15 Jan 2015 00:06:12 +0100 > From: Graham Samuel mailto:livf...@mac.com>> > To: How t

Re: [OT] I'm going to go live in a cave

On 01/15/2015 02:04 AM, Kay C Lan wrote: On Wed, Jan 14, 2015 at 7:24 PM, FlexibleLearning.com wrote: where did I put those cotton swabs? Cotton swabs? I've tried micro nozzle attachments that connect to your vacuum cleaner but by far the most effective way of cleaning all the nooks and cra

AW: Which version...

... I forgot to answer your question which version to use. If you need one of the new features of version 7 (see version info), then you go with 7.x If not, I personally would stay with 6.x until 7.x is more stable and more bugs are solved (see list) This is only my personal advice Tiemo -Ursp

AW: Which version...

Hi John, the 7.x line is the new world, based on cocoa, full unicode support, etc. which will developed further on. The 6.x line is the old world without full Unicode support and is just maintained from runrev a little further for the old school guys (like me), who can't switch to the new world (y