LiveCode can 't open stack (2): forbidden chars ?
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
LiveCode can 't open stack (2): forbidden chars ?
Hi,
LiveCode 7.0.1 can not open the document that it has created and saved 5 minutes before …
I wrote a stack to decrypt/encrypt texts. After all (successful) tests I saved the finished stack and shut off the computer.
Later I tried to open my "enigma" stack directly in Finder: LC was caught in an endless beachball loop …
I started LC, tried to open my stack in the Open File dialog: LC was caught …
I started LC, opened a random stack, tried something like "put the script of stack Enigma into msg": LC was caught …
So far you may know this story from my post of Jan 26, 2015.
Now I wrote a stack to perform only this one task: empty all fields of my "enigma" stack. And behold, I could regain control of my (now empty) stack.
When saved my encryption stack contained fields with character lists and encrypted text, both composed of Mac Roman chars from # 032 to # 255.
Does anyone know of forbidden characters ?
Peter
LiveCode 7.0.1 can not open the document that it has created and saved 5 minutes before …
I wrote a stack to decrypt/encrypt texts. After all (successful) tests I saved the finished stack and shut off the computer.
Later I tried to open my "enigma" stack directly in Finder: LC was caught in an endless beachball loop …
I started LC, tried to open my stack in the Open File dialog: LC was caught …
I started LC, opened a random stack, tried something like "put the script of stack Enigma into msg": LC was caught …
So far you may know this story from my post of Jan 26, 2015.
Now I wrote a stack to perform only this one task: empty all fields of my "enigma" stack. And behold, I could regain control of my (now empty) stack.
When saved my encryption stack contained fields with character lists and encrypted text, both composed of Mac Roman chars from # 032 to # 255.
Does anyone know of forbidden characters ?
Peter
-
- VIP Livecode Opensource Backer
- Posts: 9785
- Joined: Wed May 06, 2009 2:28 pm
- Location: New York, NY
Re: LiveCode can 't open stack (2): forbidden chars ?
It may be necessary for you to post the stack, and see if we can duplicate your problem. Hard to tell otherwise. I am willing to try it.
Craig Newman
Craig Newman
Re: LiveCode can 't open stack (2): forbidden chars ?
Hi,
following Craig's proposal, I post here my specially made stack "pdMacRoman" with empty fields: it shows exactly the same symptoms as my much larger enigma stack. Please store a fresh copy of my stack.
The button "pdMacRoman_Code_Generate" will create a code table of 256 lines and 57344 chars and put it into its corresponding field.
If you save this stack now "in all its glory" (populated fields) and quit LiveCode, you will no longer be able to open it in the Finder, in the LiveCode menu File - Open Stack, from an other stack. Instead you will meet the spinning beachball …
I am very curious about your tests and experiences …
Peter
following Craig's proposal, I post here my specially made stack "pdMacRoman" with empty fields: it shows exactly the same symptoms as my much larger enigma stack. Please store a fresh copy of my stack.
The button "pdMacRoman_Code_Generate" will create a code table of 256 lines and 57344 chars and put it into its corresponding field.
If you save this stack now "in all its glory" (populated fields) and quit LiveCode, you will no longer be able to open it in the Finder, in the LiveCode menu File - Open Stack, from an other stack. Instead you will meet the spinning beachball …
I am very curious about your tests and experiences …
Peter
- Attachments
-
- pdMacRoman.livecode.zip
- (2.43 KiB) Downloaded 260 times
-
- VIP Livecode Opensource Backer
- Posts: 4036
- Joined: Sun Jan 07, 2007 9:12 pm
- Location: Bochum, Germany
Re: LiveCode can 't open stack (2): forbidden chars ?
Hi Peter,
I tested your stack in 7.0.2 rc2 AND in 7.0.1
both times I generated and saved and could reopen the stack after quitting Livecode and restarting it to get a fresh LC.
Could not break it. MacOSX 10.9.5
there was a strange bug report about field content created in 7.0.2 and problems/inability to open in 6.5.2
http://quality.runrev.com/show_bug.cgi?id=14476
but here you want to open the stack in the same version of LC that created it.
Too bad. Love to break things...
Maybe different operating system?
Kind regards
Bernd
I tested your stack in 7.0.2 rc2 AND in 7.0.1
both times I generated and saved and could reopen the stack after quitting Livecode and restarting it to get a fresh LC.
Could not break it. MacOSX 10.9.5
there was a strange bug report about field content created in 7.0.2 and problems/inability to open in 6.5.2
http://quality.runrev.com/show_bug.cgi?id=14476
but here you want to open the stack in the same version of LC that created it.
Too bad. Love to break things...
Maybe different operating system?
Kind regards
Bernd
Re: LiveCode can 't open stack (2): forbidden chars ?
Hi Bernd,
Maybe different operating system?
Yes, MacOSX 10.10.01 …
Peter
Maybe different operating system?
Yes, MacOSX 10.10.01 …
Peter
-
- VIP Livecode Opensource Backer
- Posts: 4036
- Joined: Sun Jan 07, 2007 9:12 pm
- Location: Bochum, Germany
Re: LiveCode can 't open stack (2): forbidden chars ?
Would some kind soul please test Peter's stack in LC 7.0.1 and if possible also in LC 7.0.2 rc1 or 2 on a Mac with Yosemite installed?
Seems to be a strange thing. And if confirmed a serious bug.
Kind regards
Bernd
Seems to be a strange thing. And if confirmed a serious bug.
Kind regards
Bernd
-
- VIP Livecode Opensource Backer
- Posts: 858
- Joined: Wed Jun 24, 2009 1:17 pm
- Location: Plymouth, UK
- Contact:
Re: LiveCode can 't open stack (2): forbidden chars ?
Hi Peter
I tried your stack on Yosemite 10.10.2 with LiveCode versions 7.0.1 and 7.0.2 and in both versions the stack opened fine the second time round with a populated field
I didn't look at your code, only tested ... hope this is good news for you
Kind regards
Dave
I tried your stack on Yosemite 10.10.2 with LiveCode versions 7.0.1 and 7.0.2 and in both versions the stack opened fine the second time round with a populated field
I didn't look at your code, only tested ... hope this is good news for you
Kind regards
Dave
"...this is not the code you are looking for..."