Thanks, Andy. You're quite right. Now I'm trying to think about troubles I've
had that require parens, and can't remember... Maybe I was mixing bitwise & and
bitwise | (or). And certainly it's easy to write buggy code mixing && and ||.
I was primed to find something wrong: I've been getting what
Bitwise "&" has precedence over logical "&&", so I think this is alright.
https://en.cppreference.com/w/cpp/language/operator_precedence
(Regardless I would always use parens in cases like this to make it easier
for humans reading the code.)
---
Andy Maloney // https://asmaloney.com
twitter ~
Isn't this a bug?
bool QCocoaWindow::isTransitioningToFullScreen() const
{
NSWindow *window = m_view.window;
return window.styleMask & NSWindowStyleMaskFullScreen &&
!window.qt_fullScreen;
}
Seems like the bitwise & needs parens.
This is from Qt 5.12.9. Haven't checked Qt 5.15.
-John
Il 27/08/20 20:46, Bernhard Lindner ha scritto:
This is recommended anyway, regardless of your problem. Always #include the
module output for your headers in your corresponding .cpp files.
Can you explain that general recommendation? It seems to me that such includes
are only
useful in special
Hi Thiago!
> Add to your module.cpp:
>
> #include "moc_module.cpp"
Works well, thank you!
> This is recommended anyway, regardless of your problem. Always #include the
> module output for your headers in your corresponding .cpp files.
Can you explain that general recommendation? It seems to m
On Wednesday, 26 August 2020 12:40:31 PDT Bernhard Lindner wrote:
> Hi!
>
> Currently I am facing a problem with a Qt Creator managed Qt 5 project.
>
> The projects consists of a lot of modules and implements a special but
> useful file concept. Each module has 3 files:
>module.hpp - Public t
Hi!
> I wonder how clients of the class declared in the .hpp file can use that
> class at all.
> Unless I am missing something, they won’t be able to (at least not in the
> general case)
> unless they also include the .inl file.
Depends from what part of the module API you want to use. E.g. if
On Thu, Aug 27, 2020 at 5:43 AM Bernhard Lindner <
priv...@bernhard-lindner.de> wrote:
> > You might also use a custom extra compiler -- that still invokes moc,
> > but for each foo.h also tells moc to include foo.inl, bar.h -> bar.inl,
> > and so on...
>
> Hm, I see. Has something like that been
Hi Bernhard,
I use plain .pro and .pri files with qmake to Visual Studio projects.
Moc has a feature that prevents the output files being treated as
separate compiles - if it finds the include in the relevant module
.cpp. It works really well for us with thousands of modules. I not
sure ho
> On 27 Aug 2020, at 14:42, Bernhard Lindner
> wrote:
>
> Hi!
>
>> Can you make an example of your structure (what's exactly in each of the
>> three files)? It's not entirely clear.
>
> Ok, I attached an example of a module containing some pseudo code. Please
> tell me if you
> need more inf
Hi!
> Can you make an example of your structure (what's exactly in each of the
> three files)? It's not entirely clear.
Ok, I attached an example of a module containing some pseudo code. Please tell
me if you
need more information.
> You might also use a custom extra compiler -- that still inv
Hi,
Can you make an example of your structure (what's exactly in each of the
three files)? It's not entirely clear.
Il 27/08/20 13:26, Bernhard Lindner ha scritto:
Hm. I am not sure I get it. That is a global option, right? I have a LOT of
modules, each
with a different name. When adding an
Hi!
> > I added all .hpp file names to the .pro file using Qt Creator. All moc
> > relevant
> > .hpp files are parsed fine by moc and a moc_module.cpp file is generated for
> > each module as usual.
>
> Have you tried adding the .inl files to HEADERS instead?
Yes. But it didn't work. Even more
Spam detection software, running on the system "mx.qt-project.org",
has identified this incoming email as possible spam. The original
message has been attached to this so you can view it or label
similar future email. If you have any questions, see
the administrator of that system for details.
C
14 matches
Mail list logo
