Re: Quitting with the close box on Mac
I agree Stephen. Sometimes software companies make changes because they, “have to do something!” I don’t think that is a good reason for changing anything. Look at Microsoft! Every three years on EVERY SOFTWARE PRODUCT THEY SELL, they HAVE to produce a major upgrade, or risk pissing off millions of people who bought Software Assurance contracts. But what if the last version was as good as it ever was or could ever be? Why, then you are going to get a downgrade. Period. I liked Office XP better than anything they have since produced. Why did we need ribbons again? And where in the HELL is my damned page setup??? Bob S On May 28, 2014, at 24:43 , stephen barncard stephenrevoluti...@barncard.commailto:stephenrevoluti...@barncard.com 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
Bob Sneidar wrote: Why did we need ribbons again? I first learned of the Ribbon through a post Dan Shafer made here on this list back in 2005: http://lists.runrev.com/pipermail/use-livecode/2005-October/067709.html I might have been more skeptical, but citing Jakob Nielsen made it interesting for me, so I read Dan's post, then Jakob's article, then subscribed to the RSS feed for the MS Office design blog. Learned a lot from all that. One of the things I've come to respect most about MS' design team is their very disciplined data-driven approach. Sure, we rarely see their best work because between the usability lab and the product box marketers step in and muck it up. But the core design team does some good work, at times very good IMO. Long after it shipped one of the Ribbon team leaders, Jensen Harris, gave this talk at a UX conference - long, but IMO well worth the time: UX Week 2008: Jensen Harris, The Story of the Ribbon http://vimeo.com/3305642 -- 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
On Fri, Jun 6, 2014 at 2:32 PM, Bob Sneidar bobsnei...@iotecdigital.com wrote: liked Office XP better than anything they have since produced. Word 5.1/Excel 4 for the Mac. It's been downhill since then . . . -- Dr. Richard E. Hawkins, Esq. (702) 508-8462 ___ 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- Friday, June 6, 2014, 2:46:57 PM, you wrote: Long after it shipped one of the Ribbon team leaders, Jensen Harris, gave this talk at a UX conference - long, but IMO well worth the time: UX Week 2008: Jensen Harris, The Story of the Ribbon http://vimeo.com/3305642 Yes,that's probably my favorite UX talk. It simultaneously shows how innovative the team was, the different variables they were juggling, and how out of touch with reality Microsoft is. Mindbending and fascinating and worth every minute. -- -Mark Wieder ahsoftw...@gmail.com This communication may be unlawfully collected and stored by the National Security Agency (NSA) in secret. The parties to this email do not consent to the retrieving or storing of this communication and any related metadata, as well as printing, copying, re-transmitting, disseminating, or otherwise using it. If you believe you have received this communication in error, please delete it immediately. ___ 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
On 29 May 2014, at 12:38 pm, J. Landman Gay jac...@hyperactivesw.com 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
That said, there's an auto-save plugin (RevSmartSave) that ships with LC for those who want it. LcStackBrowser does this too, either at timed intervals or on request, along with an optional user supplied comment. Versions can be restored from a list showing the creation date and time along withe comment. Versions are retained based on a count or age or can be manually deleted. ___ 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
On May 29, 2014 7:49 AM, Igor de Oliveira Couto i...@semperuna.com wrote: 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?… LcStackDiff provides a way to view all the changes between two versions of a stack including scripts, objects, and properties. Not as seamless as the Apple feature since the stack has to be loaded into a database. ___ 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
On Thu, May 29, 2014 at 12:55 AM, J. Landman Gay jac...@hyperactivesw.com wrote: Except for Preview, which is document based but auto-closes. On my Mavericks 10.9 3 and Preview 7.0 (826.4), Preview is in a league of it's own. With all the other mentioned auto-close apps, when the last window is closed then the app closes, it's name no longer appear at top left and whatever the 2nd to last app you were using now comes to the foreground. With Preview, when I close the last window Preview is still listed as the current running app at top left, but if I select any other app it then Auto Closes Preview. As I said, Mavericks is more temperamental than other OS X versions and it appears to me that everyone seems to get vastly different mileage out of apparently the same beast. ___ 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
On 28 May 2014, at 1:54 pm, Kay C Lan lan.kc.macm...@gmail.com 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
Re: Quitting with the close box on Mac
On Tue, May 27, 2014 at 8:26 PM, Igor de Oliveira Couto i...@semperuna.comwrote: 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
I understand how you feel: On 28 May 2014, at 5:43 pm, stephen barncard stephenrevoluti...@barncard.com 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
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
-- Forwarded message -- From: divya navaneeth divya.r...@gmail.com Date: Wed, May 28, 2014 at 3:05 PM Subject: Re: Quitting with the close box on Mac To: How to use LiveCode use-livecode@lists.runrev.com 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
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 i...@semperuna.com 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: Quitting with the close box on Mac
stephen barncard wrote: This dumbing down crap should be optional, not forced on us. Björnke version: Options can get expensive over time, introducing a form of technical debt. TL/DR version: http://livecodejournal.com/blog/2014-05-28-design-options.html -- 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
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: Quitting with the close box on Mac
My Version? Excuse me? What? A minor annoyance on Mavericks is that Text Edit does indeed close automatically when the last text file is closed, slightly less annoying, so does preview. Sadly, I do expect more apps to follow in the next version of OS X. I do like the new saving behaviour tho, 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 ambassa...@fourthworld.com 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: http://livecodejournal.com/blog/2014-05-28-design-options.html -- 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
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: http://livecodejournal.com/blog/2014-05-28-design-options.html My Version? Excuse me? What? Consider it a customized summary. :) http://lists.runrev.com/pipermail/use-livecode/2014-May/201606.html -- 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
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 ambassa...@fourthworld.com wrote: My Version? Excuse me? What? Consider it a customized summary. :) http://lists.runrev.com/pipermail/use-livecode/2014-May/201606.html -- 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
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
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: Quitting with the close box on Mac
On May 27, 2014, at 5:55 PM, J. Landman Gay wrote: It used to be that a Mac app should never quit when its last window was closed, except in the case of single-window utilites. The menubar remained and the app kept running. Now that Mavericks quits apps for you when the last window closes… Another reason for me to delay running Mavericks as long as I possibly can. Is this true for apps like Word and TextEdit, too??? If so, my motivation is further reinforced. What the hell is Apple thinking of, changing its longstanding GUI conventions??? ... (whether you want it to or not) should a Mac LC app do the same? The problem with a LC app that uses the splash screen approach is that all visible windows may be closed but the main app is still running, and the OS will never quit it. Should the app be doing that itself now? In my admittedly few (and amateur) standalones, all built with the splashstack model, when I quit the primary working stack, it quits the application. I have to script it, but my assumption has been that this is what users expect from a standalone. But my apps have all been utility apps, and I don't want the OS making assumptions for me. An app that creates documents of any kind, each of which is in its own window, should most definitely NOT close when you close the last document. That's crazy. My attachment to Apple is being eroded step by step. It used to be a user-friendly, intuitive system. -- Peter Peter M. Brigham pmb...@gmail.com http://home.comcast.net/~pmbrig ___ 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
On 28 May 2014, at 12:39 pm, Peter M. Brigham pmb...@gmail.com wrote: Another reason for me to delay running Mavericks as long as I possibly can. Is this true for apps like Word and TextEdit, too??? I have been using Mavericks exclusively in all my Macs since it came out, and have now upgraded several server machines to use it as well. My experience is that it is a highly likeable and reliable system, with a workflow that is easy to learn and adopt for new users - more so than previous ones. The current iWork apps - Pages, Numbers and Keynote - do not quit when you close all documents. They stay open, like before. This does not mean that there haven’t been some radical changes in the latest versions of OS X - indeed, there have been many. For instance: because of pervasive auto-saving - all Apple apps now auto-save your work in incremental steps as you go, whether it’s work that is being stored in your local HD or in iCloud - the usual Save/Save as.., etc. File menu items have been reworked, and follow a different workflow philosophy. You are no longer expected to open a document and ‘Save As…’ before you start making changes, in fear of overwriting the old file. If you accidentally save changes to a document that you shouldn’t have, you can Revert to previous versions, so there is no need to always work on a ‘safe copy’. If you want to work like before, and make a copy of the document before making any alterations, you can use the “Duplicate” command first, and then save that duplicate as you wish. If you simply want to change the name of the document, you can use the ‘Rename” command. Save as”, therefore, in now unnecessary. For those of us who have been following the ‘old way’ of working with documents, this new way of working, and these new commands, seem like an 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. AFAIK, Apple does not make changes to long-standing GUI conventions very lightly. They are, however, constantly conducting research on usability, and sometimes this research shows that in order to keep improving, they have to break their own convention, and rewrite the rules. I hope this information helps. 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
Re: Quitting with the close box on Mac
On Wed, May 28, 2014 at 10:39 AM, Peter M. Brigham pmb...@gmail.com wrote: Another reason for me to delay running Mavericks as long as I possibly can. Is this true for apps like Word and TextEdit, too??? If so, my motivation is further reinforced. What the hell is Apple thinking of, changing its longstanding GUI conventions??? There may be other reasons* not to upgrade to Mavericks, but this may not be one of them. 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. I should point out that my Mavericks set-up isn't 'typical', so maybe that also has something to do with whether an app closes when the last window is closed. I believe most people are now slaves to the auto-save feature and the old black dot in the red traffic light icon that use to indicate that your working file had unsaved changes has been deprecated and now is only seen on 'old' apps. On my Mac I still have the black dot in red traffic light icon for all Apple and non-Apple apps as I do not have the auto-save feature turned On. To turn Off Auto-Save you check the cryptically named 'Ask to keep changes when closing documents' preference in the General pane of the System Preferences. *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. ___ 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
