Pixel Crushers Forum

Hi there!

Was just wondering, is there a way that when we're tracking a database asset, it doesn't track the canvas scroll position and the canvas zoom?

Oten times, I will reference an older database and look at previous ways we've done things.

However, looking at this makes it such that the scroll and zoom are tracked as git changes. Is there a way to ignore this specfic part?

Thank you!

Hi,

Unfortunately, no. The options were:

1. Save the canvas position in the database asset so the canvas returns to the same position when you reopen the database.

2. Or don't save the canvas position (so it doesn't register as a change in git) but you have to manually scroll to your previous position every time you reopen the database.

3. Or save the canvas position in EditorPrefs, which is not project-specific. The downside of this is that we can't know when it's reasonable to clear old saved positions from EditorPrefs, so we could end up glutting EditorPrefs with a lot of junk positions that are no longer needed.

The majority feedback was to remember canvas positions since most devs reopen the same database more often than anything else.