Re: stackfileversion

2015-07-04 Thread Mark Wieder
On 07/04/2015 11:20 AM, Klaus major-k wrote: according to TextEdit it is still REVO7000 with LC 8 dp 2. Oppps, sory, stackfileversion is also still -> 7.0 Thanks. Yeah, I had opened a stack with 0xEd and seen the header, but I wasn't sure if the stackfileversion was staying the

Re: stackfileversion

2015-07-04 Thread Klaus major-k
> Am 04.07.2015 um 20:15 schrieb Klaus major-k : > > Hi Mark, > >> Am 04.07.2015 um 20:06 schrieb Mark Wieder : >> >> Could someone with a working LC 8.x tell me what the latest stackfileversion >> is? I'm attempting to future-proof some code and L

Re: stackfileversion

2015-07-04 Thread Klaus major-k
Hi Mark, > Am 04.07.2015 um 20:06 schrieb Mark Wieder : > > Could someone with a working LC 8.x tell me what the latest stackfileversion > is? I'm attempting to future-proof some code and LC 8.0 is non-functional on > linux. The Release Notes.pdf that comes with LC

stackfileversion

2015-07-04 Thread Mark Wieder
Could someone with a working LC 8.x tell me what the latest stackfileversion is? I'm attempting to future-proof some code and LC 8.0 is non-functional on linux. The Release Notes.pdf that comes with LC 8.0 is amusing in a nostalgic sort of way but otherwise not much help. -- Mark W

Re: LC7 stackfileversion

2015-05-02 Thread Scott Rossi
Just save the stack. You don't need to use Save as or set stackFileVersion -- when the stack is saved in v7 it can use the features of that version. Regards, Scott Rossi Creative Director Tactile Media UX/UI Design > On May 2, 2015, at 10:36 AM, Peter Haworth wrote: > > I hav

LC7 stackfileversion

2015-05-02 Thread Peter Haworth
I'm subjected to the problem that LC wants to open the "saved as" stack and has a problem because there's already a stack in memory with the same name. Finally clicked enough buttons to get out of that, closed LC, reran it, opened the "saved as" version of the stack

Re: stackfileversion and locking 6.5.2

2015-02-05 Thread Bob Sneidar
Probably unrelated, but I have noticed that text that has been produced in a PDF via their OCR tool will have hidden characters in it that will prevent me from inserting or updating records in my SQL database with that data. The SQL generates an error as though there were nothing beyond the firs

Re: stackfileversion and locking 6.5.2

2015-01-30 Thread Geoff Canyon
as is? > > -- Tom Bodine > > > > > > > > -- > > View this message in context: > > > http://runtime-revolution.278305.n4.nabble.com/stackfileversion-and-locking-6-5-2-tp4688290p4688300.html > > Sent from the Revolution - User mailing li

Re: stackfileversion and locking 6.5.2

2015-01-30 Thread Mike Bonner
he new > stack format while leaving the legacy stack as is? > -- Tom Bodine > > > > -- > View this message in context: > http://runtime-revolution.278305.n4.nabble.com/stackfileversion-and-locking-6-5-2-tp4688290p4688300.html > Sent from the Revo

Re: stackfileversion and locking 6.5.2

2015-01-30 Thread tbodine
nabble.com/stackfileversion-and-locking-6-5-2-tp4688290p4688300.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 m

Re: stackfileversion and locking 6.5.2

2015-01-30 Thread Eric Corbett
0, 2015 at 3:40 AM, Geoff Canyon wrote: > >> I have a stack that I moved to 7.0.2 for a few days without thinking, and >> I want to move it back. I tried this in the message box: >> >> >> set the stackfileversion to 5.5;lock messages;save stack >> "versionPr

Re: stackfileversion and locking 6.5.2

2015-01-30 Thread Geoff Canyon
t I moved to 7.0.2 for a few days without thinking, and > I want to move it back. I tried this in the message box: > > > set the stackfileversion to 5.5;lock messages;save stack > "versionProblem";close stack "versionProblem" > > > and after that if I o

stackfileversion and locking 6.5.2

2015-01-30 Thread Geoff Canyon
I have a stack that I moved to 7.0.2 for a few days without thinking, and I want to move it back. I tried this in the message box: set the stackfileversion to 5.5;lock messages;save stack "versionProblem";close stack "versionProblem" and after that if I open it in 6.5.2