Sorry, I guess I didn’t scroll far enough. I thought Window1 was simply the definition for the window settings. Further down is the code, albeit not highly readable withe the #tags but I’m sure I’ll get used that!
Reading it this way definitely encourages pulling all the code out of the Window!
A bit more difficult to see what it is I wrote, and what is code/settings done by xojo…
No
And it wouldnt help that much anyway as the IDE doesnt live reload
So if you pushed chnages into git xojo wouldnt notice and pull them in live
Nor would it know what to do with the code inthe IDE that you had altered that is now being pulled in
It just wasnt ever architected for such a thing
Best you CAN do is just “revert to saved”
I do this frequently in the IDE with my svn & git repos when I have to pull in other changes
Fork is cross platform native for one!
(GitKraken is another Electron based one to avoid)
The last time I looked at GitHub Desktop it was like FisherPrice Git. It is quite possible a lot has changed since.
Another thing I liked about Fork was it’s similarity to Versions for Subversion which helped me learn and understand Git. The verbs with Git can be confusing early on.
if you work on teams (lots of people working on same code base) the fork app is nicer about working with merges, rebases, diffs, etc. if you are the only person working on the code then it doesnt matter.