-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Navigating profiles changes the project window #87
Comments
Can you elaborate and provide replication steps @FejZa , not sure what the specific issue is that you are referring to here? |
#Nudge @FejZa |
No replication steps needed. Simply select any profile in the service manager inspector and watch the project window switch to whatever directory that profile is in. |
The profile selection "thing" uses the editor function "Selected.IsActive" which causes the project window to navigate to the selected object, is this not required behaviour? |
I guess it's a preference. IMO it is super annoying and a "bug". Because usually I'll be within a folder in the project window that I am currently working with and then when I navigate service profiles I keep jumping from one directory to another leaving the project window folder hierarchy expanded and everything. It just makes for a very bad UX. If you ask me. I can endure the pain though if we decide to keep it this way. |
If it is causing you issue in your workflow, then let's remove that. Devs will still be able to select the profile in the inspector which will still give the same behaviour. I just need to remove the Editor.Selected references from the custom editor(s) |
Reality Collective - Service Framework Bug Report
Describe the bug
Navigating the service configuration permanently changes the project window. This is super frustrating as usually when you navigate service profiles you want to assign things etc. and you'll have to look the folder containing it up every time you change profiles. It generally makes for a really bad UX and is a productivity killer.
The text was updated successfully, but these errors were encountered: