I may have fixed it, or at least it looks promising. I can now:
Make a change -> Save and Quit Xojo -> Run Xojo and make another change -> Save and Quit Xojo -> Run Xojo and the second change has saved.
To get it to this point I deleted the project folder and Cloned the project again from Github (though this is the same version of the project which is not working on my other computer). I also switched to the all new version of the Github Desktop client.
I'm going to have to watch this sucker closely for a few days...
@SaschaSchneppmueller Maybe as a workaround, start your Git Client and see if the Changes have been Saved, befor you Close the Project?
Yes I think that is a good idea and I've been using it in this way, but it's a helluva way to live! ;)
I via iTerm created a new directory, copied the xojo code (not the .git repo) over to the new directory. rebooted (on a Mac I am not sure why I did that). and tried it on the new directory and it worked.
once it worked, I deleted the old directory. renamed the new directory to the old name. rebooted (again not sure why but I did anyways). and it still works. go figure.
@scott b I via iTerm created a new directory...
Thank you Scott. That's essentially what I did, though I just deleted the project folder and re-cloned from Git. The odd part is that the problem existed on two separate Macs after Github Desktop synced the code so I have been thinking that the problem must exist within the folder somehow, eg to one or more of the project items. Anyway I'll try this at work today, keep an eye on it and report back again.
Different problem / Software, same kind of “feature”: saved image is incomplete on Sierra (not High Sierra):
In Preview: copy an image, pasted it into another (in another window), save and only the other is saved (png). Click outside the pasted one (to unselect it), save, worked once, but not all the time. Strange too.
BTW: for once, I do not installed the newly released (High Sierra) OS; I will download it sometimes in the future… (next month ?)
@Emile S BTW: for once, I do not installed the newly released (High Sierra) OS; I will download it sometimes in the future… (next month ?)
I wish I'd been more patient with High Sierra too. The file system change was a big one and, in retrospect, I should have waited a little longer.
@Jason T I wish I'd been more patient with High Sierra too. The file system change was a big one and, in retrospect, I should have waited a little longer.
Yes, but also the way how Apple imposed such a big change and basically assumed that us developers would do their beta testing for them in the 3~4 beta period is really not very responsible of Apple.
Apple should have NOT release APFS with High Sierra, but instead encouraged (or even rewarded) developers and consumers for helping to beta test it and then included it in their next OS update. They should have also made available a tool that can revert the disk back to HFS+. Apple knows exactly how few people back up, and that once the disk is APFS, the user is screwed if they need to revert to Sierra.
IMHO they simply don't care anymore.
@Sam R IMHO they simply don't care anymore.
IMHO they act like everyone else on the Market now. I think we just have to live with this behaviour...
Don't want to start a Win vs. Mac Thing here again. But at my Main Workplace i have to work on Windows 7 + 10 with 32 + 64bits and they have teir issues too. I am still very happy when i'm at my MacBook again... :)
@SaschaSchneppmueller Don't want to start a Win vs. Mac Thing here again. But at my Main Workplace i have to work on Windows 7 + 10 with 32 + 64bits and they have teir issues too. I am still very happy when i'm at my MacBook again... :)
Don't need too, in the last few years the Mac community is already divided, between those frustrated with Apple's current direction and those who either haven't been stung yet or refuse to admit that there's trouble brewing for Apple.
@Gavin S APFS replaced a filesystem that was ancient and inappropriate for 2017. HFS+ has been around since the 80s.
Apple is doomed!! (Since 1976)
Don't make the mistake of believing what I say is doomsday speak. So Apple replaced a 27 year old filing system, effectively overnight. You know and I know that there WILL be problems and Apple knows better than anyone the rate of consumers who backup before applying Apple's updates. Yet they didn't provide a mechanism for people to revert back to HFS, you know and I know they can. So what happened, a whole bunch of people clicked on update, it fucked up and now they can't start their Mac, nor can they revert back to Sierra or whatever version of the macOS they were running before. The only advise from Apple is to wipe the drive and use internet recovery to restore the OS that came with the machine, thus losing all the customers data.
I'm sure that if you were one of these unlucky people, you'd not be making jokes.
@Sam R So Apple replaced a 27 year old filing system, effectively overnight.
While they released it to you and I "overnight" iAPFS has been in development for far longer - you know that
Its not like they sat down in Jan 2017 and said "we need a new file system you have 6 weeks" :P
They told devs about it at WWDC 2016 and didn't release it to the wild until just now
I dont know anyone at Apple that could give me details about when they started work on this but I'd bet its a few years before 2016 even
@Sam R Yet they didn't provide a mechanism for people to revert back to HFS, you know and I know they can.
This one does surprises the heck out of me
Esp since, like you said, they should expect that some people will have issues but ... hey thats Apple
Everyone has brand new Macs with SSD's in them already - right ? So design for that :P
BTW: one thing I forgot to say is that… I installed High Sierra (beta) in a blank external HD (not SSD: none available here). I made testing in that conditions: boot on the beta (external HD) ONLY.
Then, like I wrote above, I do not downloaded the GM nor the two following dot something evolutions.
Nota: my internal SSD (251MB) is always nearly full so when I will replace El Capitan with High Sierra, I will have to make a real backup first.
That said: Jason where are-you with your trouble ?
I’ve been bit by this more than a few times in recent years. Sometimes Xojo will simply not save an event, usually the most recently added event. Other parts of the file will have been written fine, so this isn’t a file system issue.
Unfortunately, I haven’t been able to find the pattern.
If you have two versions of the same project, one saves properly, the other doesn't, and if they're saved in binary format, try using my Arbed app to compare the two projects. Turn on "Show minor diffs" in the menu, and maybe even do the "Raw compare" to see every piece in detail. Maybe that helps to see what's different and causing the issue.