Will not solve Ray's problem but may help him and others in the future from
being bitten.
What with the consistent flow of updates (thank you), flavours of LC to
test (depending if Cocoa or Unicode is your top priority) or if you are
just testing verses in production; I was sick and tied of openin
Hey, if you decide to try the object copy thing, you can use this:
https://dl.dropboxusercontent.com/u/11957935/mdbRevisionPlugin.livecode
Heres the disclaimer though. If you have a stack and substacks (this
includes having a datagrid substack) the results may be unpredictable.
Meaning you might
Interesting... I'll add this to my list of things to try tomorrow when
I have time and get back up and running. (My wife and I are in the
middle of a move this weekend.)
On 1/10/2015 2:39 AM, Brahmanathaswami wrote:
Ray, I also was sweating it out yesterday with a very important
project/stac
Mike I'll try this idea tomorrow first thing. I'll also try turning off
messages before I save the stack. I just thought of that and I haven't
tried it yet. And Jackie, thanks for your suggestion regarding RR
support. I'll use that as a last resort.
On 1/9/2015 10:56 PM, Mike Bonner wrote:
Ray, I also was sweating it out yesterday with a very important
project/stack that was stuck in 7.0.1 which is, as you say so full of
bugs as to be useless...but would not open in 6.6.2 (pretty stable...)
What I did was
created a new button on the first card and in my naïveté:
on mouseup
s
On 1/9/2015 5:15 PM, Ray wrote:
Already tried it. I'm actually sticking with 6.5.2. I can create a new
stack file from scratch in 7.0.1, save it as legacy 5.5 and then re-pen
it in 6.5.2 fine. I just can't open /my stack file/ the same way,
although it continues to open correctly and function
I have an idea. (probably a stupid idea) if you select the stack, and
copy it to the clipboard, then save the clipboarddata["objects"] to a
file..
THen in 6.5.2, grab the data in that file, shove it back into the
clipboarddata["objects"] and then "paste" does that allow you to get the
stack po
FWIW my test results were the same as Scott's, unable to reproduce this
issue.
--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web
ambassa...@fourthworld.com
ing on the legacy saving ability. Both
of these have failed leaving me pleading for suggestions.
Anybody?
Original message
From: Mike Bonner
Date:01/09/2015 12:38 PM (GMT-04:00)
To: How to use LiveCode
Cc:
Subject: Re: Can't Move Backward
You might turn off messages before op
ecode. Meanwhile, 7.0.1 is so full of bugs (even
>>> playing a sound after 'waiting till sound is done' crashes) I can barely
>>> use the stack. I failed to maintain piles of old versions of my project
>>> trusting Livecode's claim that a release i
of my project trusting Livecode's
claim that a release is stable and relying on the legacy saving ability. Both
of these have failed leaving me pleading for suggestions.
Anybody?
Original message
From: Mike Bonner
Date:01/09/2015 12:38 PM (GMT-04:00)
To: How to use
l of bugs (even
>>> playing a sound after 'waiting till sound is done' crashes) I can barely
>>> use the stack. I failed to maintain piles of old versions of my project
>>> trusting Livecode's claim that a release is stable and relying on the
>>>
the legacy saving ability. Both
of these have failed leaving me pleading for suggestions.
Anybody?
Original message
From: Mike Bonner
Date:01/09/2015 12:38 PM (GMT-04:00)
To: How to use LiveCode
Cc:
Subject: Re: Can't Move Backward
You might turn off messages before ope
ng for suggestions.
>
> Anybody?
>
> Original message
> From: Mike Bonner
> Date:01/09/2015 12:38 PM (GMT-04:00)
> To: How to use LiveCode
> Cc:
> Subject: Re: Can't Move Backward
>
> You might turn off messages before opening the stack t
ng ability. Both of these have failed leaving me pleading
for suggestions.
Anybody?
Original message
From: Mike Bonner
Date:01/09/2015 12:38 PM (GMT-04:00)
To: How to use LiveCode
Cc:
Subject: Re: Can't Move Backward
You might turn off messages before opening the stack
You might turn off messages before opening the stack to see if it loads.
Also, if you're double clicking to open the stack, try using the file menu
instead.
On Fri, Jan 9, 2015 at 7:19 AM, Ray wrote:
> I'm trying a "Save As" on a stack file last saved in 7.0.1 so I can open
> it in 6.5.2, the la
I'm trying a "Save As" on a stack file last saved in 7.0.1 so I can open
it in 6.5.2, the last stable version of Livecode that I know of.
The choices are:
Legacy Livecode Stack (5.5)
Legacy Livecode Stack (2.7)
Legacy Livecode Stack (2.4)
I would imagine my copy of Livecode 6.5.2 would
17 matches
Mail list logo
