Re: QT player and continuous play of a list of songs problem
Hi Mark, maybe this is the problem: from the dictionary: Note: The playStoppedmessage is sent when a card containing the player closes and when the player's filename property is changed. If the player is hidden, or the movie or sound is not currently running, the message will still be sent. To prevent a playStopped handler from being executed inappropriately, set the lockMessages to true before changing the filename or switching cards: lock messages -- prevent sending playStopped set the filename of me to newFile unlock messages Kind regards Bernd -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/QT-player-and-continuous-play-of-a-list-of-songs-problem-tp4657886p4657887.html Sent from the Revolution - User mailing list archive at Nabble.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
Problems with German Umlaute
Hello, Recently I have a customer with OS X 10.8.2 where all German Umlaute in input and output fields are corrupted. Umlaute in Custom Propertys are correct. Strange to say it is a german customer with a german OS X with german country and keyboard settings. On other german machines all Umlaute are shown correct. Up to now, this is the only customer with this problem. I have no idea, what is going on here. Any pointer where to start investigating? Thanks Tiemo ___ 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
Time Entry Control
Does anyone know where I can find Shao Sean's Time Entry Field Object? In the list archives, shao mentions it being available at their website, but I am having a hard time finding it. In lieu of finding it, does anyone have a control that works good for selecting time's that works with 12 hour clock format? -- Regards, Andrew Kluthe and...@ctech.me ___ 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
Problems with German Umläute
There was a bug in LC 5.5.2 preventing accents etc. to show correctly. I reported it and got fixed. ___ 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
AW: Problems with German Umläute
Hi Meliton, was it a general issue for you or did it show up only in specific environments? Could you track that down? How did it show up? The relevant LC version in my case is 4.6.4 Tiemo -Ursprüngliche Nachricht- Von: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] Im Auftrag von Melitón Cardona Gesendet: Donnerstag, 6. Dezember 2012 17:39 An: How to use LiveCode Betreff: Problems with German Umläute There was a bug in LC 5.5.2 preventing accents etc. to show correctly. I reported it and got fixed. ___ 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
Problems with German Umläute
Dear Tiemo, It was LC 5.5.2 on a macBook pro with Mac OS X 10.8.2. It was filed as bug report number 10501. No accents whatsoever could even be typed. This happened at the end of october this year. Feel free to ask me for more specific issues if those are not enough. Cheers Ton ___ 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: [OT] Sailfish - Mobile Alternative
With Wakanda and others coming on as pure JS IDE's, and everybody and their Mom having HTML exporting, I think that it will be far more productive to have direct object code for devices instead of trying to go for the commodity. The string of icons following the LC logo is far more impressive to me than the ability to build web apps. I don't think I will be using it soon, but the extra feather of an RT target would also be sweet - so wait, I can write on one of several platforms and target literally *any* of the major desktop or mobile platforms? Does your tool do that? Even without RT, how many IDE's target both iOS and Android? Granted it isn't great, yet, but it's better than not-at-all. On Wed, Dec 5, 2012 at 12:49 PM, Andre Garzia an...@andregarzia.com wrote: Folks, The sailfish thing is based on Maemo with a different UI. Check out the MER project for more info. Mobile is getting interesting... (now, if we had an HTML5/js/css exporter we could target all these platforms) Best andre On Tue, Dec 4, 2012 at 4:21 PM, Scott Rossi sc...@tactilemedia.com wrote: This won't affect LiveCode any time soon, thus the OT, but as a point of mobile development interest, folks might be interested in taking a look at startup Jolla (http://www.jolla.com) who is creating an open source mobile OS called Sailfish (https://sailfishos.org/wiki/Main_Page). The company (mostly ex-Nokia) is getting some US press at the moment, perhaps due to Apple/Google fatigue, and is intent on creating an alternative to iOS/Android. The SDK appears to be tied to or based on Qt. Also, for anyone in the San Francisco Bay Area, Jolla will be talking about Sailfish OS in Santa Clara from 7-9PM tomorrow evening as part of Qt DeveloperDays (http://www.qtdeveloperdays.com/northamerica/). Regards, Scott Rossi Creative Director Tactile Media, UX Design ___ 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 -- http://www.andregarzia.com -- All We Do Is Code. http://fon.nu -- minimalist url shortening service. ___ 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 -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, This is good. ___ 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: [ANN] Dog Tales for iPad
We submitted something last Friday, and it's in the store now too. So things are a couple of days quicker than usual at the moment. On Dec 5, 2012, at 2:35 PM, John Craig j...@splash21.com wrote: Dog Tales for iPad has just been approved. This could be a good time to submit apps - this is only day 6 after it was submitted. ___ 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
Looking for tips on memory mgt in standalones
Hi, all. Two questions about standalones... I'm building a desktop app as a standalone that will use separate stacks to store the user's work. A New File button creates the stack under a new name and saves it to the user's document area. When the user closes such a file, it looks like it still persists in memory. (Going by what the Application Browser shows.) What's the best way to remove these document stacks from memory in a standalone? Also, the app will need to save user's preferences. Knowing that main stacks cannot save to themselves, I set it up with a substack that stores prefs in custom properties. However, I see now that the substack is actually part of the main stack file. So doesn't that means the substack will have the same problem of being sandboxed by the OS and unable to save? What solutions do you recommend? Many thanks. Tom Bodine -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Looking-for-tips-on-memory-mgt-in-standalones-tp4657895.html Sent from the Revolution - User mailing list archive at Nabble.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: [ANN] Dog Tales for iPad
Well, since they are shutting down for a week later in the month, now's the time! ___ 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: [ANN] Dog Tales for iPad
Right after sending that another app got approved, only this one was an update, and it went through in three days. On Dec 6, 2012, at 3:13 PM, Colin Holgate co...@verizon.net wrote: We submitted something last Friday, and it's in the store now too. So things are a couple of days quicker than usual at the moment. ___ 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: Looking for tips on memory mgt in standalones
Hi Tom, Set the 'destroyStack' property of the instance stack to true. That way it is completely removed from memory when it is closed. HTH, Jan Schenkel. = Quartam Reports PDF Library for LiveCode www.quartam.com = As we grow older, we grow both wiser and more foolish at the same time. (La Rochefoucauld) - Original Message - From: tbodine lvhd...@gmail.com To: use-revolut...@lists.runrev.com Cc: Sent: Thursday, December 6, 2012 9:16 PM Subject: Looking for tips on memory mgt in standalones Hi, all. Two questions about standalones... I'm building a desktop app as a standalone that will use separate stacks to store the user's work. A New File button creates the stack under a new name and saves it to the user's document area. When the user closes such a file, it looks like it still persists in memory. (Going by what the Application Browser shows.) What's the best way to remove these document stacks from memory in a standalone? Also, the app will need to save user's preferences. Knowing that main stacks cannot save to themselves, I set it up with a substack that stores prefs in custom properties. However, I see now that the substack is actually part of the main stack file. So doesn't that means the substack will have the same problem of being sandboxed by the OS and unable to save? What solutions do you recommend? Many thanks. Tom Bodine -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Looking-for-tips-on-memory-mgt-in-standalones-tp4657895.html Sent from the Revolution - User mailing list archive at Nabble.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 ___ 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: Looking for tips on memory mgt in standalones
tbodine wrote: I'm building a desktop app as a standalone that will use separate stacks to store the user's work. A New File button creates the stack under a new name and saves it to the user's document area. When the user closes such a file, it looks like it still persists in memory. (Going by what the Application Browser shows.) What's the best way to remove these document stacks from memory in a standalone? The simplest way is to set the stack's destroyStack property to true, which doesn't actually destroy the stack itself but merely removes it from memory when it's closed. Also, the app will need to save user's preferences. Knowing that main stacks cannot save to themselves, I set it up with a substack that stores prefs in custom properties. However, I see now that the substack is actually part of the main stack file. So doesn't that means the substack will have the same problem of being sandboxed by the OS and unable to save? What solutions do you recommend? Data can be saved to mainstacks, provided it's not the stackfile which is the executable. In fact, one can't even save to substacks of the mainstack of the stackfile which is the executable, but as long as its a separate file you're good. Exactly where you should save stackfiles used for prefs data is an item of much contention these days; some say that Apple's HIG recommendation to use the Preferences folder no longer applies unless you use their APIs to read and write it, opting instead to store prefs in an entirely different folder, Application Support. While there's been much discussion of which is best here, I don't think anyone's yet provided a URL to Apple's guidelines on this, though it would be helpful if someone can turn it up. I suppose it's not unthinkable that Apple would attempt to control the file format devs use for prefs, but it seems a bit draconian even for Apple, and I suspect that with so many devs accustomed to being able to control their own file formats there'd be more of an outcry if indeed this is what Apple is now requiring. So I'll leave it for others here to suggest where to put it (I still put prefs in Preferences, but so far I've been avoiding the App Store so I don't know if those reviewers are requiring preferences to be stored outside of Preferences), but as far as the basic mechanics of saving data in a standalone this article from Sarah is very helpful: http://livecodejournal.com/tutorials/saving_data_in_revolution.html -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ambassa...@fourthworld.comhttp://www.FourthWorld.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: Looking for tips on memory mgt in standalones
Hi Tom, Closing a stack still leaves it in memory as you found. The delete stack command will remove it from memory as long as the stack you name is a main stack; for substacks, it literally deletes the substack. And yes, you'll have the issue with your prefs substack. I have taken to storing my prefs in a flat file in different locations depending on platform. OSX: specialFolderPath(Home)/Library/Application Support/appname/prefsfilename Windows: specialFolderPath(26)/appname/prefsfilename Linux: specialFolderPath(Home)/appname/prefsfilename If you have several products, you can optionally include a companyname folder before the appname folder. Pete lcSQL Software http://www.lcsql.com On Thu, Dec 6, 2012 at 12:16 PM, tbodine lvhd...@gmail.com wrote: Hi, all. Two questions about standalones... I'm building a desktop app as a standalone that will use separate stacks to store the user's work. A New File button creates the stack under a new name and saves it to the user's document area. When the user closes such a file, it looks like it still persists in memory. (Going by what the Application Browser shows.) What's the best way to remove these document stacks from memory in a standalone? Also, the app will need to save user's preferences. Knowing that main stacks cannot save to themselves, I set it up with a substack that stores prefs in custom properties. However, I see now that the substack is actually part of the main stack file. So doesn't that means the substack will have the same problem of being sandboxed by the OS and unable to save? What solutions do you recommend? Many thanks. Tom Bodine -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Looking-for-tips-on-memory-mgt-in-standalones-tp4657895.html Sent from the Revolution - User mailing list archive at Nabble.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 ___ 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: Looking for tips on memory mgt in standalones
set the destroyStack property of the document stack to true before closing it. Don't worry, the stack file will not *actually* be destroyed. It's a bad name for the property. It should be called purgeStack imho. Preferences are trickier. You will need to know which platform you are running in, and then you will need to determine the proper place to put preference files for that platform. Search the archives for lots of good info on how to do that. Bob On Dec 6, 2012, at 10:16 AM, tbodine wrote: Hi, all. Two questions about standalones... I'm building a desktop app as a standalone that will use separate stacks to store the user's work. A New File button creates the stack under a new name and saves it to the user's document area. When the user closes such a file, it looks like it still persists in memory. (Going by what the Application Browser shows.) What's the best way to remove these document stacks from memory in a standalone? Also, the app will need to save user's preferences. Knowing that main stacks cannot save to themselves, I set it up with a substack that stores prefs in custom properties. However, I see now that the substack is actually part of the main stack file. So doesn't that means the substack will have the same problem of being sandboxed by the OS and unable to save? What solutions do you recommend? Many thanks. Tom Bodine -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Looking-for-tips-on-memory-mgt-in-standalones-tp4657895.html Sent from the Revolution - User mailing list archive at Nabble.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 ___ 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: Looking for tips on memory mgt in standalones
So If I duplicate a stack for a document, and I tell it 'close this stack'. It doesn't actually remove the stack that was closed from memory? Whoa, I'm in for some refactoring if that's the case. stacks that are destroyed,can they be opened again simply by calling the stack name a-la : go stack stackName (as I often do when I have closed a stack but want it in memory) or do I have to give it the path to the stackfile on disk? If so, whats the point of ever setting destroyStack to false? On Thu, Dec 6, 2012 at 2:40 PM, Robert Sneidar slylab...@me.com wrote: set the destroyStack property of the document stack to true before closing it. Don't worry, the stack file will not *actually* be destroyed. It's a bad name for the property. It should be called purgeStack imho. Preferences are trickier. You will need to know which platform you are running in, and then you will need to determine the proper place to put preference files for that platform. Search the archives for lots of good info on how to do that. Bob On Dec 6, 2012, at 10:16 AM, tbodine wrote: Hi, all. Two questions about standalones... I'm building a desktop app as a standalone that will use separate stacks to store the user's work. A New File button creates the stack under a new name and saves it to the user's document area. When the user closes such a file, it looks like it still persists in memory. (Going by what the Application Browser shows.) What's the best way to remove these document stacks from memory in a standalone? Also, the app will need to save user's preferences. Knowing that main stacks cannot save to themselves, I set it up with a substack that stores prefs in custom properties. However, I see now that the substack is actually part of the main stack file. So doesn't that means the substack will have the same problem of being sandboxed by the OS and unable to save? What solutions do you recommend? Many thanks. Tom Bodine -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Looking-for-tips-on-memory-mgt-in-standalones-tp4657895.html Sent from the Revolution - User mailing list archive at Nabble.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 ___ 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 -- Regards, Andrew Kluthe and...@ctech.me ___ 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: Looking for tips on memory mgt in standalones
You'd normally need to go to the stackfile name to open it again. The only way round that is to use the stackFiles property of your main stack. In it, you can specify a list of short stack names and the full path to the stack file. Then you can go to just the stack name and LC will resolve the reference to the stackfile. But that's probably not much use in a dynamic stack creation situation since any changes you make to stackFiles won;t be saved - back to square one! Pete lcSQL Software http://www.lcsql.com On Thu, Dec 6, 2012 at 3:47 PM, Andrew Kluthe and...@ctech.me wrote: So If I duplicate a stack for a document, and I tell it 'close this stack'. It doesn't actually remove the stack that was closed from memory? Whoa, I'm in for some refactoring if that's the case. stacks that are destroyed,can they be opened again simply by calling the stack name a-la : go stack stackName (as I often do when I have closed a stack but want it in memory) or do I have to give it the path to the stackfile on disk? If so, whats the point of ever setting destroyStack to false? On Thu, Dec 6, 2012 at 2:40 PM, Robert Sneidar slylab...@me.com wrote: set the destroyStack property of the document stack to true before closing it. Don't worry, the stack file will not *actually* be destroyed. It's a bad name for the property. It should be called purgeStack imho. Preferences are trickier. You will need to know which platform you are running in, and then you will need to determine the proper place to put preference files for that platform. Search the archives for lots of good info on how to do that. Bob On Dec 6, 2012, at 10:16 AM, tbodine wrote: Hi, all. Two questions about standalones... I'm building a desktop app as a standalone that will use separate stacks to store the user's work. A New File button creates the stack under a new name and saves it to the user's document area. When the user closes such a file, it looks like it still persists in memory. (Going by what the Application Browser shows.) What's the best way to remove these document stacks from memory in a standalone? Also, the app will need to save user's preferences. Knowing that main stacks cannot save to themselves, I set it up with a substack that stores prefs in custom properties. However, I see now that the substack is actually part of the main stack file. So doesn't that means the substack will have the same problem of being sandboxed by the OS and unable to save? What solutions do you recommend? Many thanks. Tom Bodine -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Looking-for-tips-on-memory-mgt-in-standalones-tp4657895.html Sent from the Revolution - User mailing list archive at Nabble.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 ___ 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 -- Regards, Andrew Kluthe and...@ctech.me ___ 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: Looking for tips on memory mgt in standalones
On 07/12/2012, at 11:46 AM, Peter Haworth wrote: So If I duplicate a stack for a document, and I tell it 'close this stack'. It doesn't actually remove the stack that was closed from memory? Whoa, I'm in for some refactoring if that's the case. Like Robert said you need to set the destroyStack. Actually the design you have above isn't brilliant for maintenance. Stacks are great containers for structured data (particularly if it's not a heap of data in which case I'd use a sqlite db file) but it's much better design to have an invisible stack file with no controls and all the data in custom properties and then a template document viewer that you clone if your app can have multiple documents open. Otherwise version 2 of your app comes out and you need to write routines to move data from version 1 of your document file to version 2. Got caught by that one on a couple of my first LC apps... Cheers Monte -- M E R Goulding Software development services Bespoke application development for vertical markets mergExt - There's an external for that! ___ 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: Looking for tips on memory mgt in standalones
Interesting. That's the direction I'm going... a document editor that clones a template and just stores data in the document stacks as a few arrays in custom properties and formatted text fields in the stack. No code or controls in the documents to avoid the update headaches you described. If this editor is to support multiple documents open at once, then there's the matter of knowing which is the active one at a given moment. I saw in the Dictionary some command that tells which stack the mouse is over. Is there something similar for keyboard focus? What would be ideal is an event triggered in LC when the user clicks a different window activating another document stack. (In Director's Lingo language, there's activateWindow and deactivateWindow event handlers. Anything similar in LC?) I expect these documents will all have similarly named custom properties, so it could get messy keeping track of them with many files open. I'm thinking that when a particular document is active, then its custom props are copied to a global that would be used by the editor's code. And when that document is deactivated, code would write the global back out to that file's custom property. Then the newly selected documents custom props would be loaded into the global. Do you foresee pitfalls with this? Is there a better way? Many thanks for your insights. Tom Bodine -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Looking-for-tips-on-memory-mgt-in-standalones-tp4657895p4657908.html Sent from the Revolution - User mailing list archive at Nabble.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: Looking for tips on memory mgt in standalones
On 07/12/2012, at 2:31 PM, tbodine wrote: What would be ideal is an event triggered in LC when the user clicks a different window activating another document stack. (In Director's Lingo language, there's activateWindow and deactivateWindow event handlers. Anything similar in LC?) resumeStack/suspendStack I expect these documents will all have similarly named custom properties, so it could get messy keeping track of them with many files open. I'm thinking that when a particular document is active, then its custom props are copied to a global that would be used by the editor's code. And when that document is deactivated, code would write the global back out to that file's custom property. Then the newly selected documents custom props would be loaded into the global. Set a customProperty or script local of the template to the name of the data stack. Alternatively your saved file coule be just an arrayEncoded array and you set that as a script local of your template. Fine for not much data. For lots of data use a db. Do you foresee pitfalls with this? Is there a better way? In general a good maintainable design will separate the data from the access to it and the view of it. There can be a few layers in there (eg a db driver). Cheers -- M E R Goulding Software development services Bespoke application development for vertical markets mergExt - There's an external for that! ___ 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
QT player and continuous play of a list of songs problem
on Thu Dec 6 02:04:44 CST 2012, BNig wrote: Note: The playStoppedmessage is sent when a card containing the player closes and when the player's filename property is changed. If the player is hidden, or the movie or sound is not currently running, the message will still be sent. To prevent a playStopped handler from being executed inappropriately, set the lockMessages to true before changing the filename or switching cards: lock messages -- prevent sending playStopped set the filename of me to newFile unlock messages Thanx Bernd. That stopped the LC engine from going to the top of the handler again. But I can't resolve the no audio problem when the next song is set to play. Any ideas on that? Regards, Mark Stuart ___ 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: Does anyone have a copy of the Pop3 Lib that used to be on Sarah's site?
try sarah at troz dot net. -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Does-anyone-have-a-copy-of-the-Pop3-Lib-that-used-to-be-on-Sarah-s-site-tp4657807p4657907.html Sent from the Revolution - User mailing list archive at Nabble.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: a new book idea...
Hi Colin, I was going to write and ask if you were interested in doing a book on LiveCode Web-App Development. I am about to head down that path but have no web server experience, no CGI, or PHP or any of that so something that covers that territory would be immensely of interest to me. Esp from the LC perspective. Maybe some of those ideas could be addressed in a chapter or two? (but sounds like a whole book to me). I've written a couple of RevUP articles on I/O to SQL files that are somewhat unique (like not requiring you to specify the field names) that I would be happy to donate (or spruce up, as needed). -- Mark -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/a-new-book-idea-tp4657832p4657906.html Sent from the Revolution - User mailing list archive at Nabble.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: Looking for tips on memory mgt in standalones
Yep. I have a big pool of data from a database that is formatted to fit nicely in a datagrid. When you click on a row in the datagrid it clones a stack I have and sets the row data as a custom property in the cloned stack. And when I looked at my code for doing this, I realized I must have already known this because destroyStack was already being set. On Thu, Dec 6, 2012 at 7:02 PM, Monte Goulding mo...@sweattechnologies.com wrote: Like Robert said you need to set the destroyStack. Actually the design you have above isn't brilliant for maintenance. Stacks are great containers for structured data (particularly if it's not a heap of data in which case I'd use a sqlite db file) but it's much better design to have an invisible stack file with no controls and all the data in custom properties and then a template document viewer that you clone if your app can have multiple documents open. Otherwise version 2 of your app comes out and you need to write routines to move data from version 1 of your document file to version 2. Got caught by that one on a couple of my first LC apps... -- Regards, Andrew Kluthe and...@ctech.me ___ 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: a new book idea...
Developing with LC Server or livecode clients that interact with webservices that you roll yourself? I have built http interfaces using RevServer (RevIgniter), PHP, and I recently started switching a lot of my REST interfaces over to express on-top-of nodejs. I love building nice little server interfaces for livecode. Not that long ago I designed a livecode/nodejs application that reads data from a truck scale via serial and feeds it to an interface that livecode can hook up to from anywhere in the world. That particular code is owned by my employers, but the technique could be used for lots of thing. On Thu, Dec 6, 2012 at 9:12 PM, Mark Smith mark_sm...@cpe.umanitoba.ca wrote: LiveCode Web-App Development. I am about to head down that path but have no web server experience, no CGI, or PHP or any of that so something that covers that territory would be immensely of interest to me. -- Regards, Andrew Kluthe and...@ctech.me ___ 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: a new book idea...
Andrew Kluthe-2 wrote Developing with LC Server or livecode clients that interact with webservices that you roll yourself? I have built http interfaces using RevServer (RevIgniter), PHP, and I recently started switching a lot of my REST interfaces over to express on-top-of nodejs. I love building nice little server interfaces for livecode. Not that long ago I designed a livecode/nodejs application that reads data from a truck scale via serial and feeds it to an interface that livecode can hook up to from anywhere in the world. That particular code is owned by my employers, but the technique could be used for lots of thing. Yes, exactly... I have no experience with any of that. Its totally a foreign world for me so having someone like yourself collaborate with Colin on a book would be just awesome. -- Mark -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/a-new-book-idea-tp4657832p4657913.html Sent from the Revolution - User mailing list archive at Nabble.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: Looking for tips on memory mgt in standalones
On 12/6/12 9:31 PM, tbodine wrote: If this editor is to support multiple documents open at once, then there's the matter of knowing which is the active one at a given moment. I saw in the Dictionary some command that tells which stack the mouse is over. Is there something similar for keyboard focus? If the user is typing into it, it's usually the defaultstack unless a script has changed that. It's also probably the topstack. What would be ideal is an event triggered in LC when the user clicks a different window activating another document stack. (In Director's Lingo language, there's activateWindow and deactivateWindow event handlers. Anything similar in LC?) As Monte said, suspendstack and resumestack messages are sent. I expect these documents will all have similarly named custom properties, so it could get messy keeping track of them with many files open. I'm thinking that when a particular document is active, then its custom props are copied to a global that would be used by the editor's code. And when that document is deactivated, code would write the global back out to that file's custom property. Then the newly selected documents custom props would be loaded into the global. Do you foresee pitfalls with this? Is there a better way? Why not just read and write properties directly to/from the document stack itself? On openstack or resumestack you could keep track of the stack name if you want to be sure which one you're dealing with, and always refer to it in scripts by name instead of just using the defaultstack. -- 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
