-
Notifications
You must be signed in to change notification settings - Fork 365
[Feature Request]: Improvements of File Explorer perspective #5184
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
Comments
Thank you so much! |
wouldn't it make sense to set that value to 3 or 5 by default? |
I'd prefer the logic to be reversed, with a default value of 999 and a tips in the docs to enable lazy loading if we have a lot of files. |
Could we maybe split it between "local" and remote explorer paths? |
You're right, I forgot about remote files. |
Reduce flicker by restoring folders expanded before setRedraw(true)
What would you like to happen?
I would greatly welcome the following improvements of the "File Explorer" perspective in the perspective toolbar:
Remember expanded folders:
When you expand a folder structure, open a pipeline or workflow via double click, you get to the "Data orchestration" perspective. When you want to open another pipeline/workflow by clicking on "File Explorer" again, all the expanded folders from before are collapsed again, and you have to re-expand them again. It would be very convenient if the previously expanded folders would remain expanded when switching back to "File explorer" perspective.
Bring already opened tab to foreground if file is already open:
Double-clicking on CSVs or JSON files in the "File explorer" perspective opens up tabs with the file content. The tab of the most-recently opened file is in the foreground. When you double-click on a file whose tab is ALREADY opened (but in the background), the tab remains in the background. It would be convenient if the tab would be sent to the foreground after double-clicking an already opened file.
Issue Priority
Priority: 3
Issue Component
Component: Hop Gui
The text was updated successfully, but these errors were encountered: