You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if a file changes on disk while the file is loaded by gen3hex, there is no mechanism in place to detect that change. Having a way to (semi-)automatically reload a file from disk would let me use the editor in conjunction with other editing programs, and switch between them in a more seamless way.
In my mind there are two distinct scenarios for which the behavior might need to differ. The first is when the file is clean, and the version in memory matches the old version on disk, prior to it being modified externally. Visual Studio Code handles this by automatically loading the changes from disk, but allowing you to access the previous version through undo. Visual Studio prompts you to optionally reload it, and tells you that you have no unsaved changes in that editor.
The second scenario is when the file in memory is dirty, and unsaved changes exist. It appears the Visual Studio Code does not do anything in this case, while Visual Studio alerts you that the file has been changed in both places and prompts you to optionally reload it.
The text was updated successfully, but these errors were encountered:
Currently if a file changes on disk while the file is loaded by gen3hex, there is no mechanism in place to detect that change. Having a way to (semi-)automatically reload a file from disk would let me use the editor in conjunction with other editing programs, and switch between them in a more seamless way.
In my mind there are two distinct scenarios for which the behavior might need to differ. The first is when the file is clean, and the version in memory matches the old version on disk, prior to it being modified externally. Visual Studio Code handles this by automatically loading the changes from disk, but allowing you to access the previous version through undo. Visual Studio prompts you to optionally reload it, and tells you that you have no unsaved changes in that editor.
The second scenario is when the file in memory is dirty, and unsaved changes exist. It appears the Visual Studio Code does not do anything in this case, while Visual Studio alerts you that the file has been changed in both places and prompts you to optionally reload it.
The text was updated successfully, but these errors were encountered: