Hi Sean,
Widgets are normally positioned relative to their owner - the exception
is popup menus, which are screen absolute. I would expect a popup menu
to automatically close when the title bar is clicked. How have you
implemented your captionPopupMenu? Does it capture the mouse when it is
Il 01/10/2018 20:11, Murphy, Sean ha scritto:
So I'm not sure what I need to trigger off from to detect when I need to
reposition the menu. I feel like I'm missing something really obvious, but not
seeing it on a Monday apparently.
I don't think you're missing anything -- if a widget doesn't
Have anybody succeed in configuring such an environment? I'm a bit
stuck with figuring out what to specify as 'workspacePath'.
Regards, Alexander
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
My basic question is how do child widgets get moved or repainted when some
ancestor of theirs moves?
Here's the more detailed issue, first the widget hierarchy:
QMainWindow
CustomerHeaderTable (inherits from QTableWidget)
CustomTableHeader (inherits from QHeaderView, allows you to put
Tuukka Turunen wrote:
> Just to note that more than “two minor fixes” were done related to widgets in
> Qt 5.11.2
Sorry, my bad. I was (wrongly) basing that statement on the contents
of the changelist:
http://code.qt.io/cgit/qt/qtbase.git/tree/dist/changes-5.11.2
If you filter that Jira link to
(I'm asking here because I think my odds of finding a CLion user in a pile of
Qt users is better than finding a Qt user in a bucket of CLion users).
I have a medium-sized Qt+cmake project - it builds fine, Qt Creator is
mostly[1] happy with it. I thought I'd give CLion a try, and it really
Hi,
Just to note that more than “two minor fixes” were done related to widgets in
Qt 5.11.2 of the total 262 fixes: https://bugreports.qt.io/issues/?filter=19635
Widgets is an important area and we are actively maintaining those. There is
less new development than on some other areas, but
Alex Blasche wrote:
> Fact is that Qt is huge and there are not enough work hours in a day to
fix them all.
I'm a maintainer of a pretty large code base myself so I understand that
completely.
> (...) some bugs are simply too hard to fix (...) and (...) there are
things which are too risky to
Those eample were pure Qml, not C++. For the auto size, you are on the
right track with the childrenRect.
I just don't get your example. but just alias to your Rectangle childrens
or data. If you use a delegate (this is normally used for Component
property that will be instantiate).
if you want
Ah, nevermind, I went down a rabbit hole of links, and eventually found the section I wanted. Thanks everyone!
FFR:
http://doc.qt.io/qt-5/qtqml-syntax-objectattributes.html#default-properties
Sent: Monday, October 01, 2018 at 9:58 AM
From: "Jason H"
To: "Jérôme Godbout"
Cc: "Qt
Hm... All that involves C++. I mean to do it all in QML.
Let me give a better example
//MyAutoSizeRectangle.qml
Rectangle {
width: childrenRect.width
height: childrenRect.height
radius: Math.min(width, height) / 2
}
// main.qml
MyAutoSizeRectangle {
color:"red"
On 9/30/18 5:27 PM, Giuseppe D'Angelo wrote:
You stated:
a lot of shortcuts
get taken and are allowed as long as the test-nothing automated test
clears Jenkins.
This is a FALSE STATEMENT, no matter if it's Jenkins or Coin or whatever
CI suite Qt happens to be using. You're not off the hook.
On 9/30/18 5:27 PM, interest-requ...@qt-project.org wrote:
I'm returning there for a few months to participate in a re-evaluation
process. They are considering ditching Qt for Electron. Doing side by
side development on all platforms to see which works best for them.
When we stumble into one of
Hi!
Forgive me for butting into this off-topic discussion about "true software
egnineering"
(which is a horrible wording).
AFAI understand that discussion is about quality.
Well, if you want to know how to develop quality software, you need to look
into safety
(not security!) industry. People
Hi Guiseppe,
> (The topic is still "how to port Qt to another platform".)
It is in the nature of discussions, that they might change direction -
like it happened with the AGILE side track.
> (Yes, I 100% agree that QtQuick could be modularized much further, e.g.
> drop its dependency from
15 matches
Mail list logo
