The invalid filename ‘Scripts\Add “#pragma unused”.arbs’ is back in the Windows zipfile.
Was fixed in a previous beta.
I’m also having several problems with this beta (on Windows 7 64-bit, Dutch language)
After having dragged a project to the Arbed Drop Pad, Arbed opens the project Window. After that I seem to be unable to use File Exit in Arbed. I can close the window with the top right x, but then Arbed remains in memory and I have to use the task manager to shut Arbed down. If I haven’t opened a project yet, the File Exit works
Sometimes using File Exit actually crashes Arbed (haven’t been able to reproduce reliably, but it happened more than once). I’ll e-mail you the report.wer crash report. Maybe you can see something there.
Switching on “enable debug messages” under preferences seems not to do anything. No Arbed-DebugLog file is created on the desktop.
I’m noticing a difference with externals items in xml with this beta (b15) as compared to the release version (1.6.3).
The beta notices something the release doesn’t, but even the beta seems to be a bit inconsistent with what happens. Hopefully this can be improved.
Hopefully the following description should explain what I see.
We use Microsoft Visual SourceSafe with a project that is full of external xml items (using Xojo 2013r2) for its windows, classes, modules…
This means that the main file (RBMain.xojo_binary_project) is locked by SourceSafe. In fact all files are locked by SourceSafe unless we check them out. Since you can’t work with a locked project file in xojo (it will lose any changes to checked out files, since the project file can’t get updated), our workflow is as such.
a. Start SourceSafe
b. Get Latest version of all project files
c. Open the RBMain.xojo_binary_project file in Xojo
d. Save this project as RBMain001.xojo_binary_project
e. Close Xojo (to prevent thing going wrong, because at this point sometimes Xojo seems to think that the new RBMain001.xojo_binary_project is also readonly even though it isn’t.)
f. Open the RBMain001.xojo_binary_project file and start working
Now when opening RBMain.xojo_binary_project or RBMain001.xojo_binary_project, Arbed seems to be handling it fine.
When opening RBMain.xojo_binary_project and the RBMain001.xojo_binary project by dragging them on Project Comparison, I get a lot of warnings about External Item… Inconsistent file references on both files, even though we have just saved the RBMain001 project so that is should be a perfect copy of the RBmain file with the same links to the external files. The project comparison window then is to empty other than references to encrypted file that it can’t compare and buildflags, as expected, since the 001 file is a copy of the main file.
If I then close the comparison window and drag the two files to the project editor, Arbed opens the projects, and most external files show up as External (Code) with a ResolvedFilePath. I then do not get to see the code in these windows, modules, classes at this point, since the project editor on the right does not show me the code, but the ResolvedFilePath instead. Hopefully this can be improved, since the file location seems to be resolved.
Some other files show up with <ambiguous [multiple files found]>. These seems to be the files that show up when dragging the files to compare projects. So it looks like the beta signals that there is a problem when comparing the files, whilst the release version didn’t say anything. What I do notice is that if I close the comparison window in the release version, and open one of the projects again by dragging it to the project editor, I also get the <ambiguous [multiple files found]>. When I rightclick the file and choose “reveal on disk”, it does show the file, and it is the same file on disk. Since both projects seem to correctly find the file through “reveal on disk”, I don’t think there should be any ambiguous files. Maybe the file names are encoded differently?
That’s what I have so far.