Skip to content
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

Feature Request: Autohide of dock mechanism #635

Open
imikejackson opened this issue May 2, 2024 · 8 comments
Open

Feature Request: Autohide of dock mechanism #635

imikejackson opened this issue May 2, 2024 · 8 comments

Comments

@imikejackson
Copy link

I like the idea of the auto hide docks and having docks being minimized on any side of the application. What are your thoughts on the ability that would allow the dock to be hidden like normal to a side of the application window, but clicking on that minimized dock put the dock back its original location before it was hidden/minimized?

For example, in CLion, this is when the "Structure" tab is hidden/minimized.
Screenshot 2024-05-02 at 12 40 32

This is after I click the tab on the side of the app. It always knows to go back to this original location.

Screenshot 2024-05-02 at 12 40 46

Thanks for keeping this library up to date.

@githubuser0xFFFF
Copy link
Owner

What is the previous location if the user dragged various dock widgets around and closed two other dock widgets after he minimized a dock widget?

@imikejackson
Copy link
Author

I would say what ever the last dock position a dock was in (when it is not in the minimized state) is the position that it would jump back to. In our own application, we have implemented this basically as a row of icons along the QStatusBar widget. You can toggle the visibility of a Dock widget. I would like to combine that feature with QtADS to show the dock along what ever side the user wants.

@imikejackson
Copy link
Author

Initial State of the app

Screenshot 2024-05-03 at 13 05 12

Clicking the "Pipeline Dock" 'pin' button collapses the dock to the left.

Screenshot 2024-05-03 at 13 05 19

Clicking that collapsed dock's button along the left side:

Screenshot 2024-05-03 at 13 05 27

Unpinning the dock does not put it back to the original location. I was hoping that I would get the original image back.

Screenshot 2024-05-03 at 13 05 33

I am sure your design goals are different than ours. Maybe we are not selecting the proper set of config flags? not sure.

@githubuser0xFFFF
Copy link
Owner

Yes, I understand your problem. But the feature that you want only works, if the user does not change anything in the current dock layout. As soon as your user drags your bookmarks dockwidget to another location or closes it, the previous position of the Pipeline Dock is gone. Therefore I asked the question:

What is the previous location if the user dragged various dock widgets around and closed two other dock widgets after he minimized a dock widget? The previous location maybe does not exist anymore.

Are you willing to spend some money for this feature?

@imikejackson
Copy link
Author

Ahh.. I had to think of the scenario that you were coming up with. Now I understand the scenario. That is an interesting situation. I wonder if it does not exist, you could programmatically "recreate it"? The user could certainly recreate it through dragging. This probably isn't trivial to figure out.

Paid Support: Are you US based?

@githubuser0xFFFF
Copy link
Owner

No Germany. No, not paid support. Just to get the feature implemented. I have no intention to implement it, because I don't need it. So some money could be a motivation for me to implement this :-)

Or we just wait for a pull request from someone.

@zyrkiel
Copy link

zyrkiel commented Nov 6, 2024

I have opened a new issue that could be an intermediate step for the feature requested here: #672

@char101
Copy link

char101 commented Nov 27, 2024

Isn't this doable by adding CDockWidget.toggleViewAction to a bottom QToolBar?

If you click on the button of the toggle view action, it will hide and show the widget in the same location.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants