@Jose Q Particularly for me is very annoying to have to close the whole project every time that I want to pull changes from my Git repo.
But that's how it works with Xojo IDE.
@Emile S No you have not. Latest Xojo is 2019r3.
In this regard, 2019r3 appears to work the same as earlier versions.
I've been making more use of External Items in my projects. And although it is not documented as a feature, I find most times that if I collapse and expand again an External Item node in the Navigator, the Methods, Properties, etc. get refreshed. I'm just commenting here, not necessarily recommending it as a solution to your question.
@nicoláscanessa have you tried with File -> Revert to Saved? i have never used it, so please do backup of your project before
I do however use "Revert to Saved" regularly, when I know the project file(s) have changed (like after pulling from GitHub) - but I always make sure my current local changes have been saved and committed beforehand. "Revert to Saved" closes and reloads the project in one step. Not an ideal solution, but I'm used to it now.
I am sure that external items are checked for changes every time you select them.
Since Xojo is not a real-time collaboration IDE, why should internal elements be checked for changes? The IDE is already slow enough for some of us... ;)
@Norman P Usually I do
@Brandon W Here is my workflow
Why don't you file a Feedback Request to rename "Revert to saved" to "Reload Project" and have that available anytime (not just when the project is "dirty", e.g. after a simple/silly change). It would save you two steps (1. having to make a change, 2. having to confirm to loose that change).
I'm more interested in being able to check in, compare, view logs, and check out code rather than automatically noticing a change on disk. I'm with you in that I wouldn't want my session to supersede my current edits because of a change made outside of the IDE.
Itsexactly why I do what I do and use SVN/Git and the tools they provde for managing this and then just have Xojo revert project which reloads it from disk when things are ready
I did submit a feature request to be able to right click on a single item and reload that one item from disk which would ease some of this
Feedback Case #58746
@Norman P I did submit a feature request to be able to right click on a single item and reload that one item from disk which would ease some of this
I've requested that feature about two years ago...: Feedback Case #50426
With a .xojo_project, a possible workaround is:
It's downside is that usually the project file gets modified because of that...
@Jürg O It's downside is that usually the project file gets modified because of that...
It would move it order in the manifest since yu'd remove one line and replace it with a new one at a different location
Basically think of it as
array.remove <index of existing item> array.append new item
a "reload" could avoid such a thing
We pointed out the dangers of this in 2013, but nothing happened with the ticket (it still says reviewed).
Both me and Gino pointed out the risk over overwriting changes that you make to code.
Since we work with external xml code we've been bitten by this multiple time.
It's very annoying that is you forget to reload you end up overwriting the code you pulled in (or changed in another project that uses the same external).