On 19/08/15 23:03, Richard Gaskin wrote:
Richmond wrote:
Why does this script NOT work in a small stack?
on mouseUp
palette stack AUTOSAVE
put the short name of the topStack into TSTAK
put TSTAK /the time / the date into TSTAKN
put TSTAKN into fld TSTAKN
save
around, but I'd be avoiding the slashes.
On Thu, Aug 20, 2015 at 1:40 PM, Richmond richmondmathew...@gmail.com
wrote:
On 19/08/15 23:03, Richard Gaskin wrote:
Richmond wrote:
Why does this script NOT work in a small stack?
on mouseUp
palette stack AUTOSAVE
put the short name
richmondmathew...@gmail.com
wrote:
On 19/08/15 23:03, Richard Gaskin wrote:
Richmond wrote:
Why does this script NOT work in a small stack?
on mouseUp
palette stack AUTOSAVE
put the short name of the topStack into TSTAK
put TSTAK /the time / the date into TSTAKN
On Aug 20, 2015, at 12:40 PM, Richmond richmondmathew...@gmail.com wrote:
save stack HEX rotate as Granny goes gay
doesn't work either.
--
Richard Gaskin
Richmond.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please
Why does this script NOT work in a small stack?
on mouseUp
palette stack AUTOSAVE
put the short name of the topStack into TSTAK
put TSTAK /the time / the date into TSTAKN
put TSTAKN into fld TSTAKN
save the topstack as TSTAKN
end mouseUp
Richmond
Richmond wrote:
Why does this script NOT work in a small stack?
on mouseUp
palette stack AUTOSAVE
put the short name of the topStack into TSTAK
put TSTAK /the time / the date into TSTAKN
put TSTAKN into fld TSTAKN
save the topstack as TSTAKN
end mouseUp
Does
On 29/10/14 07:16, Kay C Lan wrote:
On Wed, Oct 29, 2014 at 2:08 AM, Richmond richmondmathew...@gmail.com
wrote:
I mainly deal with LiveCode learners, and as such it would be nice if such
things as AutoSave
worked straight out of the box without having to add things on.
And that is why
I didn't know about this -- works great! Just what I needed. But
why is Rinaldi's save so much faster than LiveCode itself?? Odd...
And, hmm, LC7.0 just crashed on me a few minutes after activating
SmartSave... conincidence?
Tim Selander
Tokyo, Japan
On 10/28/14, 11:18 PM, Richard Gaskin
HyperCard . . . Ta dum, ta dum, ta dum.
Thanks, Tim Selander for the idea.
I wonder whether it might not be a bad idea ??? to have an optional
autosave feature
in LiveCode; it would certainly cut down on the rude words when funny
things happen.
Votes . . .
Richmond
Richmond wrote:
I wonder whether it might not be a bad idea ??? to have an optional
autosave feature
in LiveCode; it would certainly cut down on the rude words when funny
things happen.
With timers it wouldn't be hard to write for those who want it
(personally I prefer having control over
not be a bad idea ??? to have an optional
autosave feature
in LiveCode; it would certainly cut down on the rude words when funny
things happen.
With timers it wouldn't be hard to write for those who want it (personally
I prefer having control over when my stuff is committed to disk, but that's
just me
Mike Kerner wrote:
I would like some sort of versioning, similar to what we had with
that alternate script editor - so it would be the main project,
and a version get updated.
MaxV posted a nice script for that in the forums recently:
http://forums.livecode.com/viewtopic.php?f=9t=21913
--
with that
alternate script editor - so it would be the main project, and a version
get
updated.
On Tue, Oct 28, 2014 at 10:18 AM, Richard Gaskin
ambassa...@fourthworld.com
wrote:
Richmond wrote:
I wonder whether it might not be a bad idea ??? to have an optional
autosave feature
On 28/10/14 16:18, Richard Gaskin wrote:
Richmond wrote:
I wonder whether it might not be a bad idea ??? to have an optional
autosave feature
in LiveCode; it would certainly cut down on the rude words when funny
things happen.
With timers it wouldn't be hard to write for those who want
://forums.livecode.com/viewtopic.php?f=9t=21913
I am anti plug-ins and scripts for a very simple reason:
I mainly deal with LiveCode learners, and as such it would be nice if
such things as AutoSave
worked straight out of the box without having to add things on.
Richmond
Amen, Richmond!!
- Original Message -
From: Richmond richmondmathew...@gmail.com
To: How to use LiveCode use-livecode@lists.runrev.com
Sent: Tuesday, October 28, 2014 12:08 PM
Subject: Re: Autosave ???
On 28/10/14 16:53, Richard Gaskin wrote:
Mike Kerner wrote:
I would like some
: Re: Autosave ???
On 28/10/14 16:53, Richard Gaskin wrote:
Mike Kerner wrote:
I would like some sort of versioning, similar to what we had with
that alternate script editor - so it would be the main project,
and a version get updated.
MaxV posted a nice script for that in the forums
On Wed, Oct 29, 2014 at 2:08 AM, Richmond richmondmathew...@gmail.com
wrote:
I mainly deal with LiveCode learners, and as such it would be nice if such
things as AutoSave
worked straight out of the box without having to add things on.
And that is why Richard pointed out that LC, every single
,
there will have to be a field, and any autosave feature will have to
save
and/or export
and/or overwrite a rtf and/or html document at regular intervals.
Now what I don't understand is how to have a script working away 'in the
background'
checking the time and autosaving every 2-3 minutes without
On 30.03.2013 at 16:46 Uhr -0500 J. Landman Gay apparently wrote:
I just use their and ignore the plurality. It isn't grammatically
correct, but it's pretty common and includes everybody.
When the user presses a key on their keyboard...
Or don't use a pronoun at all:
When the user presses
On 03/31/2013 07:58 PM, Robert Brenstein wrote:
On 30.03.2013 at 16:46 Uhr -0500 J. Landman Gay apparently wrote:
I just use their and ignore the plurality. It isn't grammatically
correct, but it's pretty common and includes everybody.
When the user presses a key on their keyboard...
Or
On 3/31/13 11:58 AM, Robert Brenstein wrote:
On 30.03.2013 at 16:46 Uhr -0500 J. Landman Gay apparently wrote:
I just use their and ignore the plurality. It isn't grammatically
correct, but it's pretty common and includes everybody.
...
Actually, it is grammatically correct, at least
On Sat, Mar 30, 2013 at 2:46 PM, J. Landman Gay jac...@hyperactivesw.comwrote:
I just use their and ignore the plurality. It isn't grammatically
correct, but it's pretty common and includes everybody.
In English, unlike the word her, the word his does not imply gender on
its own when used for
On Mar 31, 2013, at 3:14 PM, Dr. Hawkins wrote:
On Sat, Mar 30, 2013 at 2:46 PM, J. Landman Gay
jac...@hyperactivesw.comwrote:
I just use their and ignore the plurality. It isn't grammatically
correct, but it's pretty common and includes everybody.
In English, unlike the word her,
I know english language experts say I am wrong but I too tend to use they and
their to be gender neutral.
Kee
On Mar 31, 2013, at 10:28 PM, Peter Bogdanoff bogdan...@me.com wrote:
On Mar 31, 2013, at 3:14 PM, Dr. Hawkins wrote:
On Sat, Mar 30, 2013 at 2:46 PM, J. Landman Gay
to my text entry component Wobbly Word,
there will have to be a field, and any autosave feature will have to save
and/or export
and/or overwrite a rtf and/or html document at regular intervals.
Now what I don't understand is how to have a script working away 'in the
background'
checking the time
-before-it
'Richmond-Scrubby-Cupboard'
(well, round these parts that's what passes for an office) made,
needless to say, entirely in Livecode.
Obviously, central to my text entry component Wobbly Word,
there will have to be a field, and any autosave feature will have to
save
and/or export
; the
up-and-coming-and-sweeping-all-office-suits-before-it
'Richmond-Scrubby-Cupboard'
(well, round these parts that's what passes for an office) made,
needless to say, entirely in Livecode.
Obviously, central to my text entry component Wobbly Word,
there will have to be a field, and any autosave
passes for an office) made,
needless to say, entirely in Livecode.
Obviously, central to my text entry component Wobbly Word,
there will have to be a field, and any autosave feature will have to save
and/or export
and/or overwrite a rtf and/or html document at regular intervals.
Now what I
component Wobbly Word,
there will have to be a field, and any autosave feature will have to save
and/or export
and/or overwrite a rtf and/or html document at regular intervals.
Now what I don't understand is how to have a script working away 'in the
background'
checking the time
to be a field, and any autosave feature will have to save
and/or export
and/or overwrite a rtf and/or html document at regular intervals.
Now what I don't understand is how to have a script working away 'in the
background'
checking the time and autosaving every 2-3 minutes without it interfering
On Feb 23, 2011, at 10:32 AM, Warren Kuhl wrote:
What would be the best way to implement this to have a timer running in the
background and saving my document?
You could say:
on openstack
dosave
end openstack
on dosave
save this stack
send dosave to me in 600 seconds
end dosave
32 matches
Mail list logo
