My main development machine had a corrupt user and I had to do a complete reinstall. Now I wanted to open a Xojo binary project with external items. Xojo wants to contact a remote machine (“There was a problem connecting to the server Trixis Mac Pro”). But this is the same machine!!! The project without icons load fine so I think that the icons are the problem.
I suppose that behavior happens only with this project ?
Can you borrow a bit of time of another OS X machine (at work), download the current 2015 or 2016) last Xojo version, and try to open it ?
If this works, export the project (save with a different name and try to open it when back to your own OS X machine.
[quote=255886:@Beatrix Willius]@Michel: The server is my previous configuration - the hard disk that I reformatted. It’s gone now. But the paths/username/everything else is the same.
I can’t save as XML because the project doesn’t open.[/quote]
Names being the same doesn’t fool OS X aliases
They know that it’s NOT the same volume etc
And its what makes it possible for you to move a file around on disk and not break your project
[quote=255892:@Michel Bujardet]OK. I just opened a binary project in a text editor, and it appears the path is in clear. So you can edit it as well. Make a copy before you modify it, but you should be just fine.
The path is store as absolute path.[/quote]
Its more than likely the “saveinfo” blob and doing this is more than likely going to break the project in really fun ways
Do have any local OSX machine in your network
If yes then.
Preferences >Sharing,Change the computer Name to old (Trixis Mac Pro)
Then >Finder >Go >Connect to server
smb://ServerName/ShareName or smb://The IP
ant try to open the Project after…
Ignore all “cant find server” messages (and yes this will take a while)
Save as plain text (which doesn’t use save info)
Reopen project and relocate all items that are missing
Renaming a machine is unlikely to fix it even if you put it at the same IP
Aliases are sometimes too darned smart for their own good
For future reference I’d caution you about using external items in binary projects / xml projects that reside on servers
They DO use save info which embeds an alias an that is the preferred means to locate the file because it wont break if you move files around on your local machine. However if you add items from remote machines that go away (which is what it believes has happened here) then you have this issue.
It should be possible to use the “Convert to XML” command in Arbed, while unchecking the “… External…” checkboxes. That way, Arbed should not even attempt to resolve the bad Aliases. Then you can edit the XML project file and remove the bad aliases.