-
Notifications
You must be signed in to change notification settings - Fork 241
Own fader to first position #1809
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -308,6 +308,12 @@ CClientDlg::CClientDlg ( CClient* pNCliP, | |
| // View menu -------------------------------------------------------------- | ||
| QMenu* pViewMenu = new QMenu ( tr ( "&View" ), this ); | ||
|
|
||
| // own fader first option: works from server version 3.5.5 which supports sending client ID back to client | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Feature doesn't work if connected to server prior to version 3.5.5. |
||
| QAction* OwnFaderFirstAction = | ||
| pViewMenu->addAction ( tr ( "O&wn Fader First" ), this, SLOT ( OnOwnFaderFirst() ), QKeySequence ( Qt::CTRL + Qt::Key_W ) ); | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @gilgongo Not sure if we could improve the wording here?
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Not sure - "Show own fader first" perhaps? "Put your fader first"? (I don't think the initial capitals are in style BTW) At least, I don't think "first" is ambiguous so that it needs "position" as well: "They came first in the race" vs "They came in first position in the race". "To put your own interests first" vs "To put your own interests in first position". "Position" feels redundant.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Talking of being 100% precise... I am still of the opinion that having the user's own fader at the left is good in the default (unsorted) sort, but I don't see any reason for the user to have the option to turn it on and off. If I play violin, and I sort by instrument, I would expect my fader to be right there with the other violins. If I am in London and I sort by city, I would expect my fader to be right there with the other London people. I also haven't seen any convincing argument of why a user would need to both:
Users don't have that option now. But is there somebody that really wants to do exactly that ? And if so, is that need strong enough to justify an extra setting ? Especially one that (in my view, at least) conflicts with the wording of the existing sort options ...? I personally would really struggle to come up with 100% precise accurate wording for all the sort options that would no longer be strictly correct.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I agree with every point you made here. |
||
|
|
||
| pViewMenu->addSeparator(); | ||
|
|
||
| QAction* NoSortAction = | ||
| pViewMenu->addAction ( tr ( "N&o User Sorting" ), this, SLOT ( OnNoSortChannels() ), QKeySequence ( Qt::CTRL + Qt::Key_O ) ); | ||
|
|
||
|
|
@@ -325,6 +331,9 @@ CClientDlg::CClientDlg ( CClient* pNCliP, | |
| QAction* ByCityAction = | ||
| pViewMenu->addAction ( tr ( "Sort Users by &City" ), this, SLOT ( OnSortChannelsByCity() ), QKeySequence ( Qt::CTRL + Qt::Key_T ) ); | ||
|
|
||
| OwnFaderFirstAction->setCheckable ( true ); | ||
| OwnFaderFirstAction->setChecked ( pSettings->bOwnFaderFirst ); | ||
|
|
||
| // the sorting menu entries shall be checkable and exclusive | ||
| QActionGroup* SortActionGroup = new QActionGroup ( this ); | ||
| SortActionGroup->setExclusive ( true ); | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ngocdh
There might be issues with the code here (see #2738) can you please look at this again?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(And note, again, I'd prefer if all this "state" information was held by the client - the UI should be responsible for no more than displaying that information as held.)