-
Notifications
You must be signed in to change notification settings - Fork 225
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
Recorder adjustments #2427
Recorder adjustments #2427
Conversation
"<br/><b>" + tr ( "NOTE" ) + ":</b> " + | ||
tr ( "If the recording directory is not useable, the problem will be displayed in place of the directory." ) ); | ||
tr ( "If the recording directory is not useable, the problem will be displayed in place of the session directory." ) ); |
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.
Translations will definitely change...
"</dd>" + "<dt>" + SREC_NOT_ENABLED + "</dt>" + "<dd>" | ||
#ifdef _WIN32 | ||
+ tr ( "Recording has been switched off by the UI checkbox" ) | ||
+ tr ( "Recording has been switched off by the UI checkbox." ) |
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.
Tiny translations change.
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.
With small, non-language changes like this, it is probably a good idea manually to update the .ts
files to match. Otherwise lupdate
creates it as a new, untranslated entry, and the person translating needs to notice that there is a similar vanished translation that could be used.
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.
That's a bit scary as I never look at them... I'll have a go...
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.
@softins I've added a new commit with my attempt in, including the updated ts and generated qm files.
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.
Should I have tagged the translation
entry at all?
Separate topic: I did notice a lot of translation type="vanished"
entries - are those what would have happened and do they need clearing up?
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.
Should I have tagged the
translation
entry at all?
I think when we do punctuation updates and want to avoid extra work by translators by modifying .ts files directly (which I think is good), we should do the punctuation update in the translated string as well (I currently see Die Aufnahme wurde über die Checkbox in der Benutzeroberfläche ausgeschaltet
without a trailing dot).
Separate topic: I did notice a lot of
translation type="vanished"
entries - are those what would have happened and do they need clearing up?
Yes, I think that's what would have happened and I think they should be kept and not be cleared as they may help translators in the future if this or a similar translation gets re-introduced.
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.
OK, all entries except Chinese updated to add the ".". I don't know - and couldn't tell from context - whether or not to add it there.
(Also convinced vim that some .ts files aren't typescript but are xml.)
QString strCurrentSessionDirAN = tr ( "Current session directory text box (read-only)" ); | ||
lblCurrentSessionDir->setAccessibleName ( strCurrentSessionDirAN ); | ||
edtCurrentSessionDir->setAccessibleName ( strCurrentSessionDirAN ); | ||
|
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.
Moved from line 124.
edtCurrentSessionDir->setWhatsThis ( "<b>" + tr ( "Current Session Directory" ) + ":</b> " + | ||
tr ( "Enabled during recording and holds the current recording session directory. " | ||
"Disabled after recording or when the recorder is not enabled." ) ); | ||
// new recording |
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.
Moved from line 146.
I've raised this because the current UI feels too cramped. I'd also considered moving "New recording" to where the "Session" label is but I wasn't happy with that. It left the box "unlabelled" or took up too much space. It's still not ideal, so I'm open to suggestions. |
b81b258
to
28b9175
Compare
The main thing which confuses me is that the recorder is grayed out if no recording dir is set and there's no hint saying that this needs to be set in "Options". All in all, I think the GUI is still a bit cluttered. Maybe we could structure the tabs a bit like the settings (Server Profile/Recorder/Advanced settings). Basically this would mean: Directory, Server info, Language would go to Server Profile (maybe also the welcome message, but that could also be on the advanced tab) |
That's not changed, AFAIK.
That's a separate issue. But yes - all the registration bits (Genre, Custom Directory, Location ("My Server Info")) could be one tab, the jam recorder on another and the language, delay panning, welcome message and start minimized on a third. The registration bits could then be the third tab ("out of the way"). |
28b9175
to
dd15853
Compare
dd15853
to
5570ccb
Compare
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.
The main thing which confuses me is that the recorder is grayed out if no recording dir is set
That's not changed, AFAIK.
I see if the recording dir is not set, the status message says "Not initialised" (as opposed to "Not recording"). Maybe that message could be more explicit such as "Recording dir not set"?
Apart from that, all looks ok, and I have done a successful build and run.
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.
Looks good to me, thanks!
I see if the recording dir is not set, the status message says "Not initialised" (as opposed to "Not recording"). Maybe that message could be more explicit such as "Recording dir not set"?
I second that.
Again, not a change in this PR. There may also be more to it than just changing some text. |
Recorder adjustments is a bit vague for the changelog. Maybe add something about the fact that the GUI changed a bit. |
Yeah - I couldn't remember when reviewing the ChangeLog what I'd done. This does need amending. CHANGELOG: Server GUI: Re-order Recorder widgets for better use of space (plus Qt6 compliance) |
Short description of changes
Tiny, tiny UI improvement, plus code changes to bring into line with UI. Plus Qt6 bits for recorder.
Before (Windows)
Server Setup tab:
What used to happen was the status text would change length making the session box change size. Also, the session box is used for error messages.
Options tab (running):
Log:
After (Linux)
Server Setup tab:
Now the status text is the last item, so the UI doesn't "move around".
Options tab (running):
Log:
Context: Fixes an issue?
UI improvement, Qt6 compliance.
Does this change need documentation? What needs to be documented and how?
Server screenshots.
Status of this Pull Request
Complete.
What is missing until this pull request can be merged?
2x Approves.
Checklist