On Thu, Dec 20, 2018 at 9:33 PM Mike Krus wrote:
> Hi
>
> I’ve been tracking QEvent::PaletteChange events, like this:
>
> bool MainWindow::event(QEvent *event)
> {
> if (event->type() == QEvent::PaletteChange) {
> QPalette p = palette();
> m_clearColor =
On Fri, 21 Dec 2018 at 14:12, Christian Gagneraud wrote:
> That's a pity, because QtWayland could be used for client side only,
> and Weston+IVI on the compositor side.
> Apparently Weston is "better" Than QtWayland, see 26:36 of
> https://www.youtube.com/watch?v=k9mobviOpFQ (The Modern Linux
On Fri, 21 Dec 2018 at 01:47, Johan Helsing wrote:
>
> Hi Vikas,
>
> it's a bit confusing, since there are multiple ivi protocols around
> (https://github.com/GENIVI/wayland-ivi-extension/tree/master/protocol)
>
> In Qt, we support "ivi-application", which is, as Chris wrote, a dead simple
>
On Wednesday, 19 December 2018 16:34:55 -02 Thiago Macieira wrote:
> 1) Short: 200 lines or less
> 2) Self-contained: single file, no #includes other than Qt's and STL's
> 3) Compileable: unless you meant to show a compilation problem
> 4) Example: demonstrates your problem.
>
>
On Thursday, 20 December 2018 06:48:25 -02 André Hartmann wrote:
> And while you are right, that MSVC is better compatible with most
> Windows libraries, MinGW e.g. provides pthreads and therefore makes
> porting easier.
And if you're not targetting base i386 or base x86-64, GCC generates better
On 20/12/2018 10:48, André Hartmann wrote:
And while you are right, that MSVC is better compatible with most
Windows libraries, MinGW e.g. provides pthreads and therefore makes
porting easier.
It appears to me that Qt's biggest use case is portability? I use it to
build the same codebases on
Hi,
Qt-12 well manages the colors of QWidgets - great job of Qt-developers.
Thank you!
When some background colors are managed by the application,
how to figure out whether it's Light or Dark theme currently in use?
Another question is how to get notification about the switch between the
themes?
I suppose he is just trolling community for whatever reason
and QML is sooo "outdated" that Google created Flutter, where QML was an
inspiration, for my poi
br,
Vlad
On 12/20/18 3:23 PM, Nuno Santos wrote:
Hey Roland,
Sorry mate.. I couldn’t avoid...
How are you writing UIs this days?
Hi!
I am using the new Clang Code Model in Qt Creator to highlight violations.
Recently I introduced some experimental C++20 functions in my code. These
functions are
integrated using a GCC header () that introduces
three
intrinsics that are unknown to clang:
__builtin_FILE()
Hey Roland,
Sorry mate.. I couldn’t avoid...
How are you writing UIs this days? What is modern to you?
I consider myself young. I’m only 36. But I have been writing software for the
last 20 years.
In the last 6 years I have written 4 different apps ALONE! One of them was
written 3 times.
Thiago Macieira wrote:
> Almost all the compression libraries support streaming mode. Some will have a
I'm not aware of any libraries that apply HFS compression to a stream, but
above
all, I'm not aware of any way to write HFS resource forks incrementally. I
never
tinkered with them at this
It's still not modern.
Modern implies "something which learned from past mistakes to overcome
many of them." When something recent fails we simply call it "a new
approach" implying that it failed, generally beyond human comprehension.
Modern implies something succeed in overcoming
Hi Vikas,
it's a bit confusing, since there are multiple ivi protocols around
(https://github.com/GENIVI/wayland-ivi-extension/tree/master/protocol)
In Qt, we support "ivi-application", which is, as Chris wrote, a dead simple
protocol which just support surface identification and resizing.
Hi Markus,
Is there any actual reason why you can't use the prebuilt MSVC
binaries for MSVC 2017?
E.g. the much simpler setup: With the Qt online installer, you can setup
Qt, the compiler and debugger in one go and start coding in Creator
afterwards.
For MSVC, you have to install
14 matches
Mail list logo
