Wish Function Snapshots

[aaronk]

Hi,

While the current 'Auto Backup' feature is useful for saving the entire project, I think it would be very helpful to have something like 'function snapshots.'

The idea is that whenever you compile or save your project, the IDE could create a snapshot of each function or sub that was changed. Then, next to each function, there could be a dropdown menu to select and restore a previous snapshot. Even keeping the last 10 edits (snapshots) for each function would be enough.

This would be especially useful in situations where you make changes to several subs but later realize you need to roll one of them back to its earlier version. Instead of restoring the whole project or manually copying code from backups, you could simply restore that specific function or sub.

An added bonus would be the ability to hover over a snapshot in the list to preview its code before restoring.

I believe this feature would make rolling back changes much faster and more precise.

 

[LucaMs]

It would be a lot of work for Anywhere Software (which would first have to fulfill all my "Wish"es — and those of the other members, of course).

Above all, there would be a problem. You certainly have multiple versions and copies of your project, and you would end up mixing old Subs into newer versions of the project and vice versa.

It would be much better to use GIT.

 

[aeric]

I usually commented the old version with modified date
e.g.

' Modified by Aeric 2025-09-12 5:08PM
Sub HelloWorld
  Log("Oh Yes, today is Friday!")
End Sub

' Modified by Aeric 2025-09-08 9:06AM
'Sub HelloWorld
'  Log("Oh No, it is Monday again!")
'End Sub

 

[Magma]

I usually commented the old version with modified date
e.g.

' Modified by Aeric 2025-09-12 5:08PM
Sub HelloWorld
  Log("Oh Yes, today is Friday!")
End Sub

' Modified by Aeric 2025-09-08 9:06AM
'Sub HelloWorld
'  Log("Oh No, it is Monday again!")
'End Sub

I also comment many versions sometimes... but without DateTimeStamp - actually your comments are extremely good and clean @aeric !

 

[Magma]

Hi,

While the current 'Auto Backup' feature is useful for saving the entire project, I think it would be very helpful to have something like 'function snapshots.'

The idea is that whenever you compile or save your project, the IDE could create a snapshot of each function or sub that was changed. Then, next to each function, there could be a dropdown menu to select and restore a previous snapshot. Even keeping the last 10 edits (snapshots) for each function would be enough.

This would be especially useful in situations where you make changes to several subs but later realize you need to roll one of them back to its earlier version. Instead of restoring the whole project or manually copying code from backups, you could simply restore that specific function or sub.

An added bonus would be the ability to hover over a snapshot in the list to preview its code before restoring.

I believe this feature would make rolling back changes much faster and more precise.


View attachment 166770

but I love it as interface... especially at level of sub will save us !
Nice Wish - but yes need a lot of work and may be the IDE be heavier..

+1

 

[Magma]

Actually we can have two "arrows" - one downgrade (restore older versions)... and one for upgrade (suggest with AI some optimizing)

 

[aeric]

I also comment many versions sometimes... but without DateTimeStamp - actually your comments are extremely good and clean @aeric !

I use this approach when I started to take over a legacy project since 2021.
I just follow this practice which is actually started by previous developers (or vendors).
I never thought I have maintained on this project until today for so many years.

Until 2 years ago, I have started to move the code to GitHub and this approach has become a bit pointless and messy.
I hope someone who takeover this project in the future won't curse on me when seeing a lot of comments like this.

By the way, the point of the comment is to blame on the developer who modified the code.
In this case is me, who also "me in the future" is going to blame "me in the past"

 

[Magma]

I use this approach when I started to take over a legacy project since 2021.
I just follow this practice which is actually started by previous developers (or vendors).
I never thought I have maintained on this project until today for so many years.

Until 2 years ago, I have started to move the code to GitHub and this approach has become a bit pointless and messy.
I hope someone who takeover this project in the future won't curse on me when seeing a lot of comments like this.

By the way, the point of the comment is to blame on the developer who modified the code.
In this case is me, who also "me in the future" is going to blame "me in the past"

"Don;t mess with messy"

 

[aeric]

"Don;t mess with messy"

You mean Lionel Messi ?

 

[Magma]

You mean Lionel Messi ?

It could be... ;-)