-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FR: Option to save Frozen state on per-type-basis #35
Comments
Implemented in 0.10.0 |
Working on version I have one little comment to share with you: The frozen status is lost when switching between types and coming back
Step 1: Open Graph Panel in In my humble opinion would be great to store/save the frozen/unfrozen status of a type A when switching to type B and getting back to type A Feel absolutely free to discard this. I was just my instinct of tester/user when using the other types Have a great day! |
Ahhh interesting... so the FR is to save the frozen status on a per-type basis? |
Yes!!!! I'm just stating to understand all types but my feeling is that switching between types to find unseen relations :) The workflow is very dynamic switching between types and the backlinks pane to search for content !
100% agree @SkepticMystic !!! It's the best way to implement this!
Would be AMAZING !!!!! For keyboard lovers this will be fantastic ! If you allow me one comment about this possible future feature :) -> -> Only one command Let me know if you want me to create an FR for that. What a great plugin @SkepticMystic !!!! |
I don't see why this needs to be optional, sounds hard to explain and few people would want to change this i think. If I understand @FelipeRearden correctly, it would save the frozen status and the active list when switching. Technically doable but would require a refactor to be able to save this properly as its currently unloaded on switch. |
@HEmile I guess I agree with it not needing to be optional. And yes, it would require saving the latest results of each component |
Discussed in #33
The text was updated successfully, but these errors were encountered: