metro
Full Member
Posts: 180
|
Post by metro on Nov 17, 2010 6:24:01 GMT -5
Hi All Got the bug today to setup Rb101 (4 linux) on my PCLINUXOS system had some permission problems initially but all seemed to work fine until I tried to save a new project : www.dkokenge.com/rbp/sqliteDoc.htmcut and paste the code into a new blank project page do a "save as" that works fine but when I try to re-open the saved project its not displayed use my file manager and its there in /home/laurie/rb101/projects I then notice that at least 2 projects that I have deleted in the past still exist in the "open projects" list but physically do not exist in the projects folder (viewed via file manager) any ideas??? thanks in advance Laurie
|
|
|
Post by StefanPendl on Nov 17, 2010 15:59:01 GMT -5
From your signature it seems that you are still using a beta, would you mind upgrading to the latest stable release?
|
|
metro
Full Member
Posts: 180
|
Post by metro on Nov 17, 2010 20:20:31 GMT -5
Sorry Stephan only guilty of not updating signature
I am using Rb1.01 build 2.44
when I try to open one of the projects that exist in the drop down list I get the following
Debug Full Stack Message not understood: #code
* UndefinedObject(Object)>>doesNotUnderstand:
self nil temps t1 a Message with selector: #code and arguments: #() t2 a MessageNotUnderstood t3 nil
* ProjectEditor>>openProjectNamed:
self a ProjectEditor temps t1 'SQLite' inst vars decoration a Seaside.WAStateHolder(a ProjectEditor) code '' parentPage a SessionPage hideCodeEditor nil editorSize nil toolbar a WebToolbar persistentCode nil
* optimized [] in [] in [] in OpenProject>>renderContentOn:
self BlockClosure [] in [] in [] in OpenProject>>renderContentOn: temps self an OpenProject inst vars method CompiledBlock [] in [] in [] in OpenProject>>renderContentOn: outerContext nil copiedValues an OpenProject
* Seaside.WAActionCallback>>evaluateWithArgument:
self a Seaside.WAActionCallback temps t1 'Open' inst vars context a Seaside.WARenderingContext owner a RunBASICPersonal key '42' block BlockClosure [] in [] in [] in OpenProject>>renderContentOn:
* Seaside.WAActionCallback(Seaside.WACallback)>>evaluateWithField:
self a Seaside.WAActionCallback temps t1 'Open' inst vars context a Seaside.WARenderingContext owner a RunBASICPersonal key '42' block BlockClosure [] in [] in [] in OpenProject>>renderContentOn:
regards
Laurie
|
|
|
Post by StefanPendl on Nov 19, 2010 4:18:37 GMT -5
Do you have full rights for the folder structure you have installed RB into?
Where did you install RB into?
|
|
metro
Full Member
Posts: 180
|
Post by metro on Nov 19, 2010 5:40:45 GMT -5
Hi Stephan
path is home/laurie/rb101 when i first setup Rb I did have trouble opening a SQLite Db so I then opened a terminal navigated to my home directory then entered
CHMOD 775 -R rb101
this enabled access to a couple of SQLite Dbs that SU or root had access to.
Today I did create a new *.bas and saved it as a project that was listed in the drop down list but did not physically exist in the folder and the project saved OK so now the issue (error ) described below does not occur when I select that same project
However if I try to save a new project that does not appear in the LIST but does physically exist in the folder I get this
File exists ("/home/laurie/rb101/projects/sqlite_project_project")
OK now I deleted that sqlite_project and tried to SAVE again all is well it saved.
I don't understand because I deleted it as a normal user so if there where permission problems it should not have deleted.
Thanks for your input Stephan I guess it will remain a mystery
regards
Laurie
|
|
|
Post by StefanPendl on Nov 19, 2010 18:35:49 GMT -5
It might come down to a race condition with your AV software, or any other software monitoring file system access, one never knows.
The projects listed in the save and open list should include only the folders in the projects root, which do have a suffix of _project, contain a valid .BAS and a valid workingcopy.xml file. I do not know for sure, since Carl has created this, but I would do it this way.
Might be that those projects have been published and were deleted, but not removed from the published list.
And I thought, that only Windows is mystical, but it seems Linux is going that route now too.
|
|