View Full Version : thinAir cache (or 'memory')?
Every time I update a version of thinBasic, and go into the thinAir editor, I find that I have to re-save any file I wish to work on.
What I mean by this is that if I load up a file I was working on (say, in v1.7) no edits I make to it (in v1.7.6) have any affect on its execution. Even if I save the file under v1.7.6 or even overwrite an old file with the new version, it will still not record any changes to the source code.
I end up having to create a new blank file, copy all the code into it and then save under a new name (not overwriting any old file) before it will work.
Has anyone else encountered this. Will I have to re-save every file I have been working on? Is there some setting within thinAir which affects this?
... and is the fact that I am using thinBasic through WINE on a linux system related to this?
Thanks for any help :)
Petr Schreiber
21-02-2009, 01:02
Hi,
I do not experience this on WindowsXP, but I can try it on Ubuntu 7.04 PC during the weekend.
Petr
ErosOlmi
21-02-2009, 01:13
In thinAir options (menu Window/Options) under General TAB there is a flag names "Save all before run"
Be sure it is checked in order to instruct thinAir you want to save all your scripts before executing them.
Let me know.
Eros
I'm afraid that doesn't change anything either. Anything I do to the code, whether modifications or deleting sections of it, has no affect whatsoever on the output.
I have even tried checking that Window/Options setting and then manually saving, with both Save and Save As, the problem still persists.
As I say it seems to only affect files which were saved under an older version of thinAir.
It's not a crippling problem, it just causes me to waste some time cutting and pasting code - not to mention the time I spent trying to get a large section of code to work, only to realise that nothing I was doing was changing the executed program. And all along I was thinking that I was making some mistake :o
ErosOlmi
21-02-2009, 02:04
Can you check if script files are (for some strange reason) read-only :?
Grrr!
How could I have missed that? :oops:
That's all it was Eros. The only thing I can think of is that I installed v1.7.6 very soon after a backup restore (and forgetting the default read-only status of the script folder backup), and have only just got round to using it again.
Very embarrassing!
Thanks again.
ErosOlmi
21-02-2009, 02:24
No problem Intio, such things can happen
Even if thinAir was not thought to be executed under Wine, we did some tests and all went quite fine.
I was getting worried about what I could have done in last version to create such a problem.
So, that's fine. We have found the problem and now I'm getting better ;)
Ciao
Eros
ErosOlmi
21-02-2009, 02:26
Maybe this little "frustration" can be seen on the positive side: we need to check if script file is read-only file and emit a kind of warning.
I will pass this request to Roberto and see if he can do this implementation.
Ciao
Eros
Sounds like a good idea, though I'm not sure if anyone else will make my mistake :lol:
I'm glad that there was no problem with thinAir. In fact it has turned out to be one of the better environments I've run under Linux/WINE.