#923 Remove ConsoleWriterFactory#926
Conversation
|
Tests:
Anything else anyone can think of? |
|
Will do, but it will either be later today or else tomorrow. |
|
I can look into it tomorrow |
|
Thanks :) |
| QString strWelcomeMessage = ""; | ||
| QString strClientName = ""; | ||
|
|
||
| #if !defined(HEADLESS) && defined(_WIN32) |
There was a problem hiding this comment.
I assume this is the first time we change coding style?
There was a problem hiding this comment.
Still to be tested (real world test), but since you couldn't find issues, I will approve it.
Memory usage does increase (it was at 1.1 MB and after having connected & disconnected multiple clients enabled and disabled the recorder). It now stays at 1.5 MB on my Debian 10 laptop
|
I saw in several places the comment What environments has compilation been tested on so far? I can test on Linux(RPi) and Mac(Mojave), but not (yet) PC. |
|
The CodeQL check makes sure that it compiles on all 3 OS. So this should be ok. Raspberry Pi is untested but I‘m quite sure if it compiled on Debian and Ubuntu (both amd64) armhf should work too. |
I have much to learn! Not sure what this is.
Just trying this now. |
softins
left a comment
There was a problem hiding this comment.
Compiles and runs fine on RPi too, so approving.
Would still like to understand the reason for originally moving to ConsoleWriterFactory and why this no longer applies.
|
It would appear that my review doesn't count - presumably I don't have write access:
|
|
Does it work now? I just changed the role maindeveloper role to have write access and made you an organisation admin. I think we can merge this now |
Thanks, github is now happy with my approval.
I agree. |
|
Merged. @pljones I think we should still do some real world tests. |
It basically tests if the code compiles and to some extent checks it for vulnerabilities. |
Qt4 compatibility. We gave up on that some time last year, I think. |
Before the push I did and it seemed to work okay -- all the main.cpp messages appeared - also adding -v stopped start up still. I also did and tested the various recorder messages with SIGUSR1, SIGUSR2 and clients connecting and servers registering / unregistering. |
Ah, cool, understood. Thanks! I remember that happening. |
All instances of
ConsoleWriterFactoryhave been removed.In addition, on Windows (when not headless), the console has been attached once on start up to ensure messages appear. This only happens when run from the command line - otherwise the messages don't appear.
Parameterised messages use
QStringformatting but that's needed an extraqUtf8Printablecall to pass the result toqInfo()etc.A few of the start up messages were warnings, so they're now
qWarning(), rather thanqInfo(). Start up failure is now displayed asqCritical()messages.As we've generally moved to
qInfo()etc, I removed the QT version check where it was in place.Unrelated bits...
--centralserverto use the term "server list".--ctrlmidichand--clientnameto be consistent with the other long opt-only options.