Re: Quitting with the close box on Mac

[Igor de Oliveira Couto]

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 Pages document, for instance, you ARE able to 
scroll through every page in your document, and see the individual changes made 
to every page. It seems Apple has built that ability into the system for 
developers to take advantage of, if they want to - but it’s up to the 
individual developers to decide just how much/little of it they will implement 
in their apps. 

Now, how useful would that be if we were able to do the same from, let’s say, 
inside a stack window (viewing previous versions of an interface), or directly 
from the script editor?…

--
Igor Couto
Sydney, Australia

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Quitting with the close box on Mac

[J. Landman Gay]

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 when 
I started with the MC/LC engine. I always tinker and make mistakes and 
mess around until I get something working and then I save it. HC saved 
every little thing, which made it impossible to revert to your last 
stable version if you've made a mess of things. I don't want all my 
experimental fluff saved.


That said, there's an auto-save plugin (RevSmartSave) that ships with LC 
for those who want it.


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 your changes 
aren't visible on that first page, there is no way to tell which one of 
those dozens of copies is the one you're looking for. Looking through 
them in Finder is a little easier, at least for some file types you can 
page through the document in QuickLook.


I wouldn't mind having a QuickLook for stacks.

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: South Florida LiveCode User Group

[Richard Gaskin]

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 
forums, as there are far more new users there than here on this list:




--
 Richard Gaskin
 LiveCode Community Manager
 rich...@livecode.org



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

South Florida LiveCode User Group

[Magicgate Software - Skip Kimpel]

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
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Quitting with the close box on Mac

[Richard Gaskin]

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.


--
 Richard Gaskin
 Fourth World
 LiveCode training and consulting: http://www.fourthworld.com
 Webzine for LiveCode developers: http://www.LiveCodeJournal.com
 Follow me on Twitter:  http://twitter.com/FourthWorldSys


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Quitting with the close box on Mac

[Björnke von Gierke]

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. :)
> 
> 



--

Anyone thinking about joining on the 28. June in Zurich? 
Please send me an email!

-- 

Use an alternative Dictionary viewer:
http://bjoernke.com/bvgdocu/

Chat with other RunRev developers:
http://bjoernke.com/chatrev/



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Quitting with the close box on Mac

[Richard Gaskin]

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:
>> 
>
> My Version? Excuse me? What?

Consider it a customized summary. :)



--
 Richard Gaskin
 Fourth World
 LiveCode training and consulting: http://www.fourthworld.com
 Webzine for LiveCode developers: http://www.LiveCodeJournal.com
 Follow me on Twitter:  http://twitter.com/FourthWorldSys


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Quitting with the close box on Mac

[Björnke von Gierke]

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, It was broken in the last version 
(mountain lion?) But now it works as expected. Yes, it's different from the 
'save/save as...' approach, and in the beginning I was fearing loss of control, 
or non-standard files (again for plain files in text edit). But it works 
hidden, database-style, reliably, and doesn't introduce large storage demands, 
at least as fas as I could tell. It took me about an hour to understand, it 
simplifies workflow, and there is no need to remember if i've made a backup, or 
if i need to save vs. save as vs. export. It's certainly easier to understand 
for beginners, and if there'd be a Björnke doctrine, then 'make it easier for 
beginners' would probably be among the first rules, if not the primary doctrine.

In a sense, the recent discussion about an automatic backup for stacks... 
Mavericks automatic save system and complete version history is actually THE 
solution for that. 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, it's amazing if it works properly... 
until the whole file is corrupted ;-)

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:
> 
> 
> --
> Richard Gaskin
> Fourth World
> LiveCode training and consulting: http://www.fourthworld.com
> Webzine for LiveCode developers: http://www.LiveCodeJournal.com
> Follow me on Twitter:  http://twitter.com/FourthWorldSys
> 
> 
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

--

Anyone thinking about joining on the 28. June in Zurich? 
Please send me an email!

-- 

Use an alternative Dictionary viewer:
http://bjoernke.com/bvgdocu/

Chat with other RunRev developers:
http://bjoernke.com/chatrev/



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Quitting with the close box on Mac

[J. Landman Gay]

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:


replace "cat" with empty in tText

This will remove all instances of the word "cat" from the text in the 
variable "tText".


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: LiveCode 7.0.0-DP-5 Linux

[Richmond]

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 authorisation magic; it can't really influence how it does that
> job. Normally, gksu follows whatever rules the /etc/sudoers file
> specifies.
>
> One problem is that some versions of Ubuntu and other distros no
> longer include gksu by default. The Ubuntu recommendation (somewhat
> strangely) is to get people to use "sudo" on the command line
> instead; hardly the most user-friendly way to run the installer. An
> alternative is to use pkexec, which should provide the same features
> as gksu, but (at least last time I tried) wasn't a drop-in
> replacement so things stopped working.
>
> Why does everyone make it so difficult to get admin privileges? ;)

Given that Ubuntu (and Mint and Debian etc.) all handle .deb files 
well, I suppose the next obvious question is:


Can we see .deb package deployment as an optional alternative for Linux?

If we can, you can do something very useful for RunRev:  get LiveCode 
into the Ubuntu Software Center.


Not to mention seamless with-the-grain installation for everyone using 
.deb-based systems.




I'm not entirely sure what "seamless with-the-grain" means [ possibly 
because I'm quite

good and being seamy against-the-grain, LOL ].

But, just now, when I decided to install 7.0.0 dp 5, I clicked on "All 
Users", was asked
for my password, and everything installed 'seamlessly', insofar as that 
was all I has to
do and Livecode 7.0.0 dp 5 duly appeared in the standard XFCE menu under 
'Development' and

in Whisker menu in the same place.

I, honestly don't know what could be smoother than that. And, in many 
ways I feel that is a bit
better than mucking around with the terminal, Synaptic or the "Ubuntu 
Software Center" thing.


As the Livecode installers for Linux are not .deb files automagically 
downloaded and installed
they don't also start clogging up the arteries so one has to keep doing 
"sudo apt-get autoremove"

and so forth with the termilnal or mucking around with Ubuntu Tweak.

The other great thing is that all versions of Livecode are now neatly 
lined up inside a .runrev
directory inside one's Home folder so one can chuck out older ones when 
things get a bit much.




Oh, and, bye-ther-way; the newer dp 5 of Livecode 7.0.0 still says "dp 
4" in the top bar of

the "revmenuBar" stack, and the "About" gives dp 4 | build 10008.

Richmond.

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: LiveCode 7.0.0-DP-5 Linux

[Richard Gaskin]

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 it does that
> job. Normally, gksu follows whatever rules the /etc/sudoers file
> specifies.
>
> One problem is that some versions of Ubuntu and other distros no
> longer include gksu by default. The Ubuntu recommendation (somewhat
> strangely) is to get people to use "sudo" on the command line
> instead; hardly the most user-friendly way to run the installer. An
> alternative is to use pkexec, which should provide the same features
> as gksu, but (at least last time I tried) wasn't a drop-in
> replacement so things stopped working.
>
> Why does everyone make it so difficult to get admin privileges? ;)

Given that Ubuntu (and Mint and Debian etc.) all handle .deb files well, 
I suppose the next obvious question is:


Can we see .deb package deployment as an optional alternative for Linux?

If we can, you can do something very useful for RunRev:  get LiveCode 
into the Ubuntu Software Center.


Not to mention seamless with-the-grain installation for everyone using 
.deb-based systems.


--
 Richard Gaskin
 Fourth World
 LiveCode training and consulting: http://www.fourthworld.com
 Webzine for LiveCode developers: http://www.LiveCodeJournal.com
 Follow me on Twitter:  http://twitter.com/FourthWorldSys


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: LiveCode 7.0.0-DP-5 Linux

[Richmond]

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 the current account and requires that the account 
be on the sudoers list.

Fraser, can this be changed?

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 it does that job. Normally, 
gksu follows whatever rules the /etc/sudoers file specifies.

One problem is that some versions of Ubuntu and other distros no longer include gksu by 
default. The Ubuntu recommendation (somewhat strangely) is to get people to use 
"sudo" on the command line instead; hardly the most user-friendly way to run 
the installer. An alternative is to use pkexec, which should provide the same features as 
gksu, but (at least last time I tried) wasn't a drop-in replacement so things stopped 
working.

Why does everyone make it so difficult to get admin privileges? ;)

Regards,
Fraser



Further "entertainment":

I successfully installed the 7.0.0 DP 5 'second attempt' with the "All 
Users" option.


When I launched it [Livecode 7.0.0 dp 5] it offered me the chance to UPGRADE
to version 6.7.0 dp 4.

Lovely :)

Richmond.

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: iOS: Wait Time less than 1 millisecond?

[Dar Scott]

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 I 
expected.  

Dar


On May 28, 2014, at 11:12 AM, Rick Harrison  wrote:

> 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 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 external.  
>> 
>> Unfortunately, it is locked and I will have to go and unzip some files in 
>> some old CDs to find an unlocked version.  
>> 
>> Another approach for Windows is to calibrate your delay command by calling 
>> it a thousand times at the start.  You might even thousand, tweak, thousand, 
>> tweak.  It might cost a half second at a slash screen, though.  That should 
>> work for OS X, too.
>> 
>> Dar Scott
>> Externals and Libraries
>> 
>> On May 28, 2014, at 9:37 AM, Rick Harrison  wrote:
>> 
>>> 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 best if I could start and stop a timer which would
>>> tell me exactly how much time has passed executing my loop.
>>> 
>>> Ideas?  Suggestions?
>>> 
>>> Thanks,
>>> 
>>> Rick
>>> ___
>>> use-livecode mailing list
>>> use-livecode@lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your 
>>> subscription preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>> 
>> 
>> ___
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription 
>> preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> 
> 
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Quitting with the close box on Mac

[Richard Gaskin]

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
 LiveCode training and consulting: http://www.fourthworld.com
 Webzine for LiveCode developers: http://www.LiveCodeJournal.com
 Follow me on Twitter:  http://twitter.com/FourthWorldSys



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: iOS: Wait Time less than 1 millisecond?

[Rick Harrison]

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 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 external.  
> 
> Unfortunately, it is locked and I will have to go and unzip some files in 
> some old CDs to find an unlocked version.  
> 
> Another approach for Windows is to calibrate your delay command by calling it 
> a thousand times at the start.  You might even thousand, tweak, thousand, 
> tweak.  It might cost a half second at a slash screen, though.  That should 
> work for OS X, too.
> 
> Dar Scott
> Externals and Libraries
> 
> On May 28, 2014, at 9:37 AM, Rick Harrison  wrote:
> 
>> 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 best if I could start and stop a timer which would
>> tell me exactly how much time has passed executing my loop.
>> 
>> Ideas?  Suggestions?
>> 
>> Thanks,
>> 
>> Rick
>> ___
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription 
>> preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> 
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: 7.0.0 dp 5

[J. Landman Gay]

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 find refers to it as "DP", with "Stable" used only for final 
>versions, the most recent of which is 6.6.1:
>

-- 
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Quitting with the close box on Mac

[J. Landman Gay]

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 Couto  
wrote:
>
>It seems that document-based applications stay open, while utilities
>auto-quit when their window is closed. So System Prefs quits when
>closed, and both Disk and Network Utility quit when closed.

-- 
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Wait Time less than 1 millisecond?

[Dar Scott]

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 external.  

Unfortunately, it is locked and I will have to go and unzip some files in some 
old CDs to find an unlocked version.  

Another approach for Windows is to calibrate your delay command by calling it a 
thousand times at the start.  You might even thousand, tweak, thousand, tweak.  
It might cost a half second at a slash screen, though.  That should work for OS 
X, too.

Dar Scott
Externals and Libraries

On May 28, 2014, at 9:37 AM, Rick Harrison  wrote:

> 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 best if I could start and stop a timer which would
> tell me exactly how much time has passed executing my loop.
> 
> Ideas?  Suggestions?
> 
> Thanks,
> 
> Rick
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Wait Time less than 1 millisecond?

[dunbarx]

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 
Sent: Wed, May 28, 2014 11:39 am
Subject: 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 best if I could start and stop a timer which would
tell me exactly how much time has passed executing my loop.

Ideas?  Suggestions?

Thanks,

Rick
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

 
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: 7.0.0 dp 5

[J. Landman Gay]

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 notification.

On May 28, 2014 12:32:29 AM CDT, 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.
>
>-- Paul
>___
>use-livecode mailing list
>use-livecode@lists.runrev.com
>Please visit this url to subscribe, unsubscribe and manage your
>subscription preferences:
>http://lists.runrev.com/mailman/listinfo/use-livecode

-- 
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

This session has timed out

[Ray]

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 subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Wait Time less than 1 millisecond?

[Rick Harrison]

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 best if I could start and stop a timer which would
tell me exactly how much time has passed executing my loop.

Ideas?  Suggestions?

Thanks,

Rick
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: LiveCode 7.0.0-DP-5 Linux

[Fraser Gordon]

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 
> requires that the account be on the sudoers list.
> 
> Fraser, can this be changed?

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 it does that job. Normally, 
gksu follows whatever rules the /etc/sudoers file specifies.

One problem is that some versions of Ubuntu and other distros no longer include 
gksu by default. The Ubuntu recommendation (somewhat strangely) is to get 
people to use "sudo" on the command line instead; hardly the most user-friendly 
way to run the installer. An alternative is to use pkexec, which should provide 
the same features as gksu, but (at least last time I tried) wasn't a drop-in 
replacement so things stopped working.

Why does everyone make it so difficult to get admin privileges? ;)

Regards,
Fraser


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: sloooowww standalone building with many included files

[Chris Sheffield]

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 Sneidar  wrote:

> Apple let an app through with 8500 audio files attached? How big is the app 
> when compiled?
> 
> Bob
> 
> 
> On May 22, 2014, at 11:29 , Chris Sheffield 
> mailto:cmsheffi...@icloud.com>> wrote:
> 
> So I have an app. An iOS app. This app includes lots and lots of small audio 
> files (nearly 8500).
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: 7.0.0 dp 5

[Richard Gaskin]

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 when it 
tried to open it and report back a different message if you're trying to open a 
stack that appears to come from a later, incompatible version of LiveCode. This 
is especially important when we have so many versions of LiveCode that are 
current and it is easy to make a mistake and save the stack with a test 
version. Of course they can't retro-fit version 5 et al, but all the currently 
in progress versions and any future versions could have this feature.  The 
message you get could be something along the lines of:

"This stack cannot be opened by this version of LiveCode. It was most recently saved 
by a version of LiveCode newer than this one."

That would help people figure out what the problem was…

What do people think?


I think you should submit that as a feature request.  It would be very, 
very helpful, not only providing specific useful guidance but also for 
maintaining LC's good reputation with its robust file format.


--
 Richard Gaskin
 Fourth World
 LiveCode training and consulting: http://www.fourthworld.com
 Webzine for LiveCode developers: http://www.LiveCodeJournal.com
 Follow me on Twitter:  http://twitter.com/FourthWorldSys

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: 7.0.0 dp 5

[Alex Tweedly]

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 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 can find refers to it as "DP", with "Stable" used only 
for final versions, the most recent of which is 6.6.1:



Where are people seeing any pre-release build labeled "stable"?

Stack file corruption has historically been extremely rare, esp. 
compared to other xTalks - I'd like to see it stay that way.  I hope 
anyone experience what appears to be corruption has filed a bug report 
so the team can be alerted to this most critical issue.


--
 Richard Gaskin
 Fourth World
 LiveCode training and consulting: http://www.fourthworld.com
 Webzine for LiveCode developers: http://www.LiveCodeJournal.com
 Follow me on Twitter:  http://twitter.com/FourthWorldSys

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your 
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-livecode



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: 7.0.0 dp 5

[Phil Jimmieson]

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 and report back a different message if you're trying to open a 
stack that appears to come from a later, incompatible version of LiveCode. This 
is especially important when we have so many versions of LiveCode that are 
current and it is easy to make a mistake and save the stack with a test 
version. Of course they can't retro-fit version 5 et al, but all the currently 
in progress versions and any future versions could have this feature.  The 
message you get could be something along the lines of:

"This stack cannot be opened by this version of LiveCode. It was most recently 
saved by a version of LiveCode newer than this one."  

That would help people figure out what the problem was…

What do people think?


On 28 May 2014, at 14:54, Richard Gaskin  wrote:

> 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 
> can find refers to it as "DP", with "Stable" used only for final versions, 
> the most recent of which is 6.6.1:
> 
> 
> Where are people seeing any pre-release build labeled "stable"?
> 
> Stack file corruption has historically been extremely rare, esp. compared to 
> other xTalks - I'd like to see it stay that way.  I hope anyone experience 
> what appears to be corruption has filed a bug report so the team can be 
> alerted to this most critical issue.
> 
> --
> Richard Gaskin
> Fourth World
> LiveCode training and consulting: http://www.fourthworld.com
> Webzine for LiveCode developers: http://www.LiveCodeJournal.com
> Follow me on Twitter:  http://twitter.com/FourthWorldSys
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

--
Phil Jimmieson  p...@liverpool.ac.uk  (UK) 0151 795 4236
Computer Science Dept., Liverpool University, Ashton Building, Ashton Street
Liverpool L69 3BX  http://www.csc.liv.ac.uk/~phil/
I used to sit on a special medical board... ...but now I use this ointment.





___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: LiveCode 7.0.0-DP-5 Linux

[Richard Gaskin]

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-uploaded the Linux installers for DP5 to the downloads website:

http://downloads.livecode.com/livecode/

Regards,
Fraser



I have just tried to install the "re-built and re-uploade" DP 5 on my
UbuntuStudio 14.04
['you only'] and it crashed, silently [no error messages]. I wonder
where the crash log is.


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 requires that the account be on the sudoers list.


Fraser, can this be changed?

--
 Richard Gaskin
 Fourth World
 LiveCode training and consulting: http://www.fourthworld.com
 Webzine for LiveCode developers: http://www.LiveCodeJournal.com
 Follow me on Twitter:  http://twitter.com/FourthWorldSys

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: 7.0.0 dp 5

[Richard Gaskin]

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 can find refers to it as "DP", with "Stable" used only for final 
versions, the most recent of which is 6.6.1:



Where are people seeing any pre-release build labeled "stable"?

Stack file corruption has historically been extremely rare, esp. 
compared to other xTalks - I'd like to see it stay that way.  I hope 
anyone experience what appears to be corruption has filed a bug report 
so the team can be alerted to this most critical issue.


--
 Richard Gaskin
 Fourth World
 LiveCode training and consulting: http://www.fourthworld.com
 Webzine for LiveCode developers: http://www.LiveCodeJournal.com
 Follow me on Twitter:  http://twitter.com/FourthWorldSys

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Quitting with the close box on Mac

[divya navaneeth]

-- 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 and deleting unwanted words

Thank you in Advance



>
>
-- 

Divya S Sathyan
RSGP Condulting pVt ltd



-- 
   Thank You
Regards
Divya S Sathyan
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Quitting with the close box on Mac

[divya navaneeth]

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
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Quitting with the close box on Mac

[Igor de Oliveira Couto]

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 and an OS
> that anticipates how I work. This dumbing down crap should be optional, not
> forced on us.

But to a new user, who has just learned how to use it, the ‘new’ way of doing 
things does not seem ‘dumb down’ nor stupid, nor more difficult than the old. 
Much the opposite: they think the new way is ’smarter’… ;-)

—
Igor Couto
Sydney, Australia
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Quitting with the close box on Mac

[stephen barncard]

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 Revert quite intuitive, requiring a lot less explanation.
>

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 and an OS
that anticipates how I work. This dumbing down crap should be optional, not
forced on us.

*--*
*Stephen Barncard - San Francisco Ca. USA - Deeds Not Words*
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Quitting with the close box on Mac

[Igor de Oliveira Couto]

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, now Contacts and Reminders
> does the same - I can live with that. On my Mac the vast majority of
> apps remain open when the last window is closed. […]

It seems that document-based applications stay open, while utilities auto-quit 
when their window is closed. So System Prefs quits when closed, and both Disk 
and Network Utility quit when closed.

The problem is, that some apps are not quite 'doc-based', nor ‘utilities’. For 
instance: Terminal app, or Keychain. The approach that Apple seems to take with 
these, is to let them behave as doc-based apps, and NOT auto-quit on close. 

> […] *Mavericks is the most temperamental OS X I've used. I've had Finder
> windows that will not come to the front, drag and drop that will not
> work, when I start my Mac sometimes the Finder windows that were open
> when I shutdown are there, sometimes only one, and sometimes none -
> and it makes no difference if I check the box about 'Reopen windows
> when logging back in' or not. Plus a few other things that seem to
> suggest that Mavericks has a personality all of it's own.


I have read quite a few negative reports about Mavericks on the web, and it 
seems that some people really do have many issues with it. I have quite a few 
systems that I look after, including servers that are remotely located and 
which I have to maintain via long-distance ssh or vnc sessions. *Knock-on-wook* 
my experience has been the opposite: Mavericks seems to be the most stable 
system I’ve had in a *long* time - including the Servers.

Kindest regards to all,

—
Igor Couto
Sydney, Australia
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode