-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Cannot reorder the 'Name' column under Qt5 #2835
Comments
@pmzqla can you confirm on your machine? |
Yes, same here. EDIT: It happens everywhere for the first column, even in "Trackers" where the first column is "#". |
Supposedly QTreeView::setTreePosition with a value of Rant: Are they stupid? If |
qt/qtbase@e0fc088 |
This reverts commit 86f9cc1. Conflicts: configure
I chose not to switch to qt5(by default) for official builds due to this. |
Seems to be working fine with Qt 5.5.1 |
@davispuh Did you try to reorder your first column? Does it work? |
You can because that's not the actual first column. The first column is "#", which is hidden unless you enable torrent queuing from the settings. Try the same in the bottom panels, e.g. Tracker. I quickly looked at the source code of Qt5.5 and the code that prevents movements of the first column is still there. |
indeed, can't move |
This bug is going to be fixed in Qt? If not we can add a new column with size 0 in the first column or some hack. |
It's done on purpose, so I don't think it's going to be "fixed". See the commit I linked here above for more info, it also shows a working hack. |
@sledgehammer999 I think Qt developers are not going to allow reordering the first column. Last week they ported almost all applications included in the KDE desktop to Qt5 (around 150 apps) and in Dolphin (the default file explorer) and in other apps you can't move the first column. |
@ngosang I saw your earlier post about the hack and was pondering over it while on vacation. Today I'll test if adding another dummy column first and hiding it solves the problem. If it does I'll commit it and close this. |
The title says it all.
I discovered this while testing the fix for #2340. I haven't dug into it. A soft(?) dependency for v3.2.0.
PS: This may need a fresh install to manifest.
The text was updated successfully, but these errors were encountered: