Frédéric Brière

I defined the command-line argument as a simple ratio (up to 1.0), but maybe a percentage (up to 100.0) would have been more intuitive? Feedback welcome.

It just struck me that there's no need to actually choose between the two: both could be supported at the same time, allowing for either 0.85 or 85 as an...

> Just for example: >  Fixed in #204. Thanks! >  This string is within a `.ui` file, and is therefore automatically marked: https://github.com/LubosD/twinkle/blob/aaa3593b1e1f1c43ccb62028071842e376341c5e/src/gui/syssettingsform.ui#L897-L899 >  This string is...

Ah, I finally see the misunderstanding! I thought you were a *user* pointing out strings left in English in the *GUI*, while you're actually a *translator* pointing out the lack...

As I stated in #104, I've now had a chance to actually test G.729, and this code seems to work fine, in that it does not have any impact when...

@wifimaclet Would it not be possible to create two ALSA devices, with the `pulse` and `jack` plugins respectively, and use them (as "ALSA: other device") instead of the default?

> the call overlay window does not follow the 200% zoom. Am I correct in assuming that this also affects the incoming call popup, as well as Twinkle as a...

Hmm, I guess each application is supposed to individually enable this on its own, after confirming that it does indeed behave correctly in this situation. This is what I observed...

> All Test without any QT env variables: > > The Image above is taken from a 3k display with 200% UI Scaling in Gnome. > > The APP UI...

> Result 2: Surface 3k "QT_AUTO_SCREEN_SCALE_FACTOR=0 QT_SCALE_FACTOR=2.0 twinkle" Can you confirm that `QT_AUTO_SCREEN_SCALE_FACTOR=1 twinkle` works just as well on the tablet? > the ring overlay is now "somewhere" on the...