On Sat, Jun 4, 2016 at 6:48 PM, Konstantin Tokarev
wrote:
>
> 04.06.2016, 18:10, "charleyb123 ." :
> > This is to free the developer from considering implications of (2).
>
> I disagree, (2) is still present as the choice of make-function. It's up
> to you to decide if it will be Foo(...), std::ma
Hello,
Since this is opinion based I will give my opinion without explicitly
stating it's just a personal view on the subject on every line.
On Sat, Jun 4, 2016 at 3:55 PM, Антон Жилин wrote:
> A trend in modern C++ is AAA idiom.
>
The newest and hottest fad, which I consider to be a complete a
On Fri, Jun 3, 2016 at 4:23 PM, André Somers wrote:
> Windows tends to mess with you here, applying the same kinds of tricks
> they introduced for the registry long ago to the file system now too.
What tricks do you mean? Perhaps I'm not up to date with the win API, but I
don't remember somethi
Hello,
Yes, you are correct, I forgot all about that although I was thinking more
of a platform-specific solution. Also the class is somewhat inconvenient as
the behaviour is a bit different on Windows and *nix.
You could try some platform-specific code handling it (e.g. Windows does
allow for glo
Hello,
Have you tried a system semaphore? It should work in this case as far as I
know.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
On Thu, Apr 7, 2016 at 4:34 PM, Peter M. Groen wrote:
> I'm expecting the output would be in ascending order, but every once in
> a while, the output is all thrown together.
>
What do you mean by that exactly?
On Thu, May 19, 2016 at 11:01 AM, Jay wrote:
> I think that Signal and Slot mechani
>
> Should I just do it from the constructor?
That would be what I usually do. Still there's overhead of repeatedly
registering the same type, so if you have a better place on hand (a root
object/entry point of your application/library) that'd be better.
> Would I need to worry about thread saf
On Fri, May 13, 2016 at 2:43 PM, d3fault wrote:
> It's to work around the diamond inheritance problem, so yea admittedly
> it's ugly. Know a cleaner way? I'm all ears.
>
Declare your signals directly into the classes that provide them and
connect compatible methods, that'd be the cleaner way. B
>
> query for the interface implementation
>
To be read as: "query for the interface being implemented
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
On Sun, May 8, 2016 at 8:27 AM, d3fault wrote:
>
> You're right, my example didn't suffer from the diamond inheritance
> problem. But suppose you want to inherit from a QWidget derived class (or
> any of the QObject derived classes in Qt xD) in addition to the
> signals/slots interface: if the int
PS.
I just realized you're worried that the functions are virtual. Well this is
of no consequence, the vtable is respected (if I remember correctly that's
specified in the standard). So the following should also be working without
any problem:
QObject::connect(a, Interface::someSignal, b, Interfac
On Sat, May 7, 2016 at 10:34 AM, d3fault wrote:
> Nobody's mentioned that Qt4-style connect syntax is required to solve the
> diamond inheritance problem that frequently appears when using a
> signals/slots interface.
> [snippet]
>
I don't see any multiple inheritance that forms a diamond. And a
On Sat, May 7, 2016 at 12:54 AM, Thiago Macieira
wrote:
>
> > Yes, by actually using a QSharedPointer for the constructor (as
> > QWeakPointer is a weak reference to a shared pointer).
>
> That's not the same thing. For a while, we had deprecated QPointer in
> favour
> of QWeakPointer for trackin
>
> Well you can't have implicit upcasting ...
>
That's a typo, I meant downcasting.
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
On Fri, May 6, 2016 at 8:35 AM, Tom Isaacson
wrote:
> I'm moving some Qt4.8.2 code which uses QWeakPointer to Qt5.6.
> Simplifying a lot it looks like this:
> [snippet ..]
> but when I compile under Visual Studio 2013 I get this error:
> error C2664: 'QWeakPointer::QWeakPointer(const QSharedPoint
>
> Well, that's not quite true of course. If you want to show a dialog
> created on the stack, you will have to use it's exec() method. That spins
> an event loop, and that means that a lot can happen in the mean time. It
> can vary from an incoming DBUS messages causing the application to
> termi
On Thu, May 5, 2016 at 4:22 AM, Nikos Chantziaras wrote:
>
> On 05/05/16 01:44, Nye wrote:
>
>> No one said it does. Perhaps I'm misunderstanding, are you searching for
>> a silver bullet for memory management?
>>
>
> I already found it. Question is how to
> From what I can tell, QPointer does not delete the object, so that's a no
go.
No one said it does. Perhaps I'm misunderstanding, are you searching for a
silver bullet for memory management?
> Putting the objects on the stack doesn't work either, because the Qt
object model does not support that
> I've been removing every trance of 'new' and 'delete' from my code and
> switching to something like:
>
>auto obj = std::make_unique(ctor args);
>
> (Or std::make_shared, depending on the situation.)
>
> But for QObjects with a parent, that can go horribly wrong. So I have to
> do annoying st
Hello,
This is ordinarily done with the help of a global locking primitive (for
example a global mutex). On the first run the mutex would be locked, and if
locking fails on the second one, you just exit the application.
IMPORTANT: As any global resource, special care should be taken to release
it i
> I’m really thinking about it actually but I don’t want QtCreator
contributions to go in vein and I think it will come to a point where no
one will use it anymore in someday :(
Well, the thing is many people aren't so willing to switch IDEs they've
worked with for years, even if they admittedly h
sery. :D
Kind regards.
On Thu, Mar 24, 2016 at 7:35 PM, Curtis Mitch wrote:
> I've fixed it with the GameReference class.
>
>
> ------
> *From:* Nye
> *Sent:* Thursday, 24 March 2016 18:28
>
> *To:* Curtis Mitch
> *Cc:* interest@qt-project
I don't see how you can fix this.
On Thu, Mar 24, 2016 at 7:21 PM, Curtis Mitch wrote:
> I've explained the problems with referencing the game object in the bug
> report. :)
>
>
> --
> *From:* Nye
> *Sent:* Thursday, 24 March 2
d luck!
On Thu, Mar 24, 2016 at 6:45 PM, Nye wrote:
> > The "loadedComponents" thing is more or less the same as the GameScope
> thing (I ended up calling it GameReference), except you need to remember to
> increment the count yourself, whereas with GameScope, it does it
&g
nt the count yourself, whereas with GameScope, it does it
> automatically.
>
>
> The problem with the code you posted is as I mentioned earlier: Loader
> never immediately deletes its items, so the code would still reference
> the game object when it shouldn't.
>
>
> --
"Supposedly setting the source of the loader to NULL" to be read as "Supposedly
setting the source of the loader to an empty string"
On Thu, Mar 24, 2016 at 12:25 PM, Nye wrote:
> Okay,
> It might sound stupid, but why not notify the game from your loaders?
> Sup
x27;d still need to identify the
> Loaders that are relevant to (have references to) the game, so you'd end up
> with more or less the same amount of extra QML code (a line or two). It
> also ties it to Loaders, but the same problem exists with the destroy()
> JavaScript function, fo
aseReferenceCount();
>
> else
>
> game->decreaseReferenceCount();
>
>
>
> mGame = game;
>
> }
>
>
>
> GameScope::~GameScope()
>
> {
>
> if (game)
>
> game->decreaseReferenceCount();
>
> }
>
>
>
Hello,
I don't work with QML, but I'm pretty sure the events are processed in the
order of their appearance in the event queue. So if you have a
`deleteLater` call (i.e. you have a QEvent::DeferredDelete, which is
scheduled through the event loop) any queued call to a slot (i.e.
QEvent::MetaCall) t
Maybe, you could also create a "feature" for qmake and use it with CONFIG
+= myfeature.
I've used this approach to keep the MPI wrapper compilers' configurations
separate from the project files.
On Fri, Mar 11, 2016 at 3:44 PM, Roland Winklmeier <
roland.m.winklme...@gmail.com> wrote:
> 2016-03-1
> Initially I just set several widget with setMouseTracking but it didn't
worked.
Well, I'd never had any problem with mouse tracking, but you may have
stumbled on a bug or a platform incompatibility, however remote that
possibility might be. Unfortunately, I haven't any more suggestions to
provid
ou better.
Kind regards,
Konstantin.
On Fri, Mar 4, 2016 at 3:28 AM, Nicolas Jäger
wrote:
> Hi Nye and others,
>
> I use the resize event, the problem is how can I scale properly the QRect,
> because just scaling the
> widget don't resize the QRect. I try to compute the rati
Hello Nicolas,
> if some widget has the setMouseTracking set to true, the event
mouseMoveEvent is detected only when a clicked is perfomed.
This doesn't sound right, enabling the mouse tracking causes mouse move
events to be dispatched to the widget without the need to have a mouse
click (provide
You could intercept the QWidget's resize event either by providing an
override (http://doc.qt.io/qt-5/qwidget.html#resizeEvent) or by installing
an event filter (http://doc.qt.io/qt-5/eventsandfilters.html#event-filters).
Note, however, you'll receive a resize event on initialization of the
widget
me ago, which could be
useful if you decide to have your objects marshaled in a similar manner:
https://forum.qt.io/topic/64277/meta-type-id-of-an-object
I hope that helps.
Kind regards.
On Wed, Mar 2, 2016 at 5:51 PM, Thiago Macieira
wrote:
> On quarta-feira, 2 de março de 2016 13:04:35 PST
I just meant that in my case the classes are defined in the user
application, so the library has no notion whatsoever what classes it has
available to create instances from and it depends on the meta-type system
exclusively for that (while still handling the
serialization/deserialization of said in
> For now there is a design choice which I feel weak myself, to do factory
or to use QMetaType for creating instances.
Depends on the use case I suppose. If you know the types at compile time,
as is usually the case I'd go with the simple solution to make a factory. I
recently, however, had a case
>
> That's not what I meant. I meant that you run your APIs in non-blocking
> mode.
>
> There's only one thing in each thread that is allowed to block and that's
> the
> main loop, the one that QCoreApplication drives.
I'm already running the MPI API in non-blocking mode.
I meant that if you nee
wrote:
> On sábado, 13 de fevereiro de 2016 11:17:22 PST Nye wrote:
> > Thanks! However I'm still going to need to run the dispatcher (default or
> > not) in non-blocking mode, right? Or am I missing something?
>
> Always non-blocking.
>
> --
> Thiago Macieira -
Hello,
On Fri, Feb 12, 2016 at 8:34 AM, Thiago Macieira
wrote:
> Em sexta-feira, 12 de fevereiro de 2016, às 05:01:34 PST, Nye escreveu:
> > Unfortunately, the messages are polled, and I have seen, browsing through
> > the OpenMPI docs, no way of using a file I could sel
Hello,
The only reason to subclass one of Qt's QXxxxPrivate classes is if you're
> developing something as part of Qt.
>
> If you're feeling adventurous, you may want to access one of those classes,
> without deriving from them. But you're still accessing private API and
> you're
> subject to the
t in the future) this doesn't seem to be such a
problem. However, any suggestions on how I could've done better by my code
are greatly appreciated!
Kind regards.
On Thu, Feb 11, 2016 at 7:40 PM, Nikos Chantziaras wrote:
> On 11/02/16 15:45, Nye wrote:
>
>> > You should
> You should not have done that.
How come? I shouldn't have derived from QCoreApplication or shouldn't have
used the private API?
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
n Thu, Feb 11, 2016 at 3:21 AM, Thiago Macieira
wrote:
> On quinta-feira, 11 de fevereiro de 2016 02:48:11 PST Nye wrote:
> > Hello,
> > In qcoreevent.h one could see that a pointer to the forward
> > declared QEventPrivate is declared as a member of QEvent, however I
> wasn
Hello,
In qcoreevent.h one could see that a pointer to the forward
declared QEventPrivate is declared as a member of QEvent, however I wasn't
able to see that class defined anywhere. Is this a leftover from a previous
version or something that was never implemented? As I'm implementing a few
of my
Hello,
Are you shadow-building? Usually this creates some confusion about where
files are to be put, at least this is my experience with win.
Kind regards.
On Wed, Feb 10, 2016 at 5:04 PM, Igor Mironchik
wrote:
> Hi guys,
>
> I'm trying to build my project on windows using MSVC 2013.
>
> Projec
(which
include QCoreApplication, QAbstractEventDispatcher, QObject and so on). I'm
aware of the implications of using the private API, but at this point I'm
willing to suffer through them.
Thanks for the help!
On Tue, Feb 9, 2016 at 9:57 AM, Thiago Macieira
wrote:
> On terça-feira, 9 de fevere
Hello,
I wish to implement my own event dispatcher, so I derived from
QAbstractEventDispatcher. As usual with PIMPL I'd derive my private object
from QAbstractEventDispatcherPrivate and pass it to the public class'
constructor. Unfortunately, even with QT += core-private I don't have the
"qabstract
Hello,
What kind of primitives do you have in your path, lines? If so, you could
"parse" the path by elements and get the normal vectors for each one line,
and check if they (could) pass through your point and at what distance the
point is. If you have curves that might be quite more involved. Is y
in Qt,
but most of the things are available.
Kind regards,
Konstantin.
On Mon, Dec 28, 2015 at 1:34 AM, wrote:
> Hi Nye,
>
> In fact, my regular expression was wrong. Yours works like a charm. I
> appreciate your help. Thank you so much 😊
>
> Regards
> David
>
>
Hello,
Your regular expression is very strange. You have a character class with
two symbols and then you don't have a capture group? Maybe try this:
"(?<=\\s)c:\\s?(.*)$"
Kind regards.
On Mon, Dec 28, 2015 at 12:42 AM, wrote:
> I am currently trying to extract the following chain of character:
Hello Harald,
In my investigations, to be honest, I was not able to use QOpenGLWidget at
all (Qt3D as you've seen requires a QWindow subclass). I ended up creating
a QOpenGLWindow and then integrating it into my layout exactly through the
QWidget::createWindowContainer() function. Hopefully someone
erlay
> window to:
> a. restrict the mouse to the desired area
> b. dispatch other mouse event to widgets below.
>
> Won't be easy, but it seems not impossible.
>
> Regards,
> Jan
>
>
> On 22-12-2015 12:22, Nye wrote:
>
> Hello Jan,
> Thanks for the sugg
n its client area). In
windows the API seems to allow the behavior I'm after (
https://msdn.microsoft.com/en-us/library/windows/desktop/ms648383(v=vs.85).aspx)
but I'm not sure if this is even possible for X11.
Kind regards,
Konstantin.
On Tue, Dec 22, 2015 at 12:52 PM, Jan Dasselaar wr
Hello,
Is it possible to clip the mouse cursor to a specific area of the screen?
I've tried to limit the cursor movement by installing an event filter on
the application object and moving it back when its position got outside of
my target rectangle, but the results proved to be unsatisfactory, as t
example to the
bugreport, so I expect I'll be corrected if in fact I'm doing something the
wrong way. That's for now and thanks for the help.
Kind regards,
Konstantin.
On Thu, Dec 17, 2015 at 12:39 PM, Nye wrote:
> Hello Sean,
> I'm not entirely convinced that it is re
5 at 12:20 PM, Sean Harmer wrote:
> On Thursday 17 Dec 2015 12:17:48 Nye wrote:
> > Hello Harald,
> > In fact this is what I'm attempting, but realized that there is a more
> > "subtle" way to do it. I think that switching the root entity and/or the
> >
pectEngines for offscreen rendering that shares the root
> entity with the other QAspectEngines?
>
> Harald
>
>
> 2015-12-17 10:49 GMT+01:00 Sean Harmer :
>
>> On Thursday 17 Dec 2015 11:37:49 Nye wrote:
>> > Hello,
>> > It (most probably) is a problem
in the cases I tested. Perhaps there's a regression we
> need
> to fix.
>
> Thanks,
>
> Sean
>
> On Thursday 17 Dec 2015 09:51:51 Nye wrote:
> > Hello,
> > It seems for some reason that adding a logic aspect to the aspect engine
> > causes the appl
Hello,
It seems for some reason that adding a logic aspect to the aspect engine
causes the application to "hang" on exit. My guess is that for some reason
the shutdown sequence is not executing properly and the threads in the pool
are left in waiting. Is there currently a workaround for that (i.e.
Hello,
I don't know about the "most efficient", but always have found the
following approach the most readable and easy to manage:
QString thumbPath =
QStringLiteral("%1/thumb_%2.jpg").arg(getProjectDir()).arg(basename);
Kind regards.
On Tue, Dec 15, 2015 at 12:02 PM, Julius Bullinger <
julius.bu
Hello,
I think I get it now. Thanks!
On Mon, Dec 14, 2015 at 5:50 PM, Sean Harmer wrote:
> Hi,
>
> On Monday 14 Dec 2015 17:36:55 Nye wrote:
> > Hello Sean,
> > Thanks, that mostly clears things up. Only one additional question:
> > How are they normalized, to the
Hello Sean,
Thanks, that mostly clears things up. Only one additional question:
How are they normalized, to the window/opengl surface size that I have
passed to the aspect engine?
Kind regards.
On Mon, Dec 14, 2015 at 3:11 PM, Sean Harmer wrote:
> On Monday 14 Dec 2015 12:30:40 Nye wr
Hello,
I understood (by trial and error) that in the axisValueChanged signal I get
a relative offset. I incorrectly assumed it was an absolute value. Is it
scaled or bound somehow, in example to the screen resolution, or is the
value absolute (I'm using it with a mouse device)? Additionally, I'd li
a bit, note the difference in values, although the direction of
the mouse moving was not changed except at the boundaries (where I get the
started/finished actions actually).
I hope this helps in tracking that issue.
Kind regards.
On Wed, Dec 9, 2015 at 1:40 PM, Nye wrote:
> Hello,
>
in the current
architecture are practically always used with a single key.
I'd be willing to contribute source as well, but I'm afraid my knowledge of
the underlying classes is pretty limited.
Kind regards,
Konstantin.
On Wed, Dec 9, 2015 at 12:22 PM, Sean Harmer wrote:
> Hi,
>
&
the action is triggered -
triggered when all the ActionInput-s are set?
}
]
}
That's for now, I hope it's helpful.
Kind regards,
Konstantin.
On Wed, Dec 9, 2015 at 6:10 AM, Nye wrote:
> A guinea pig now, am I? ;)
> Am I assuming correctly that these new changes ar
Use this to
> multiply your calculated velocity (or whatever) by.
>
> Hope this helps. If you have ideas for how to improve this then please let
> us know.
>
> Cheers,
>
> Sean
>
>
> On 08/12/2015 14:51, Nye wrote:
>
> Hello,
> I wish to have the camera movemen
Hello,
I wish to have the camera movement bound to a certain "slice" of the world
space. I didn't see that to be available through the default
implementation, so I assume I'd have to write my own component that
implements the input aspect and attach it to my camera. I've gone through
the sources, b
Oh, that explains it. I have the 5.5.1 version from the repositories.
By the way, great job guys! I'm really impressed with the work and thought
put into Qt3D, it is really impressive!
Kind regards.
On Sun, Dec 6, 2015 at 9:23 AM, Sean Harmer wrote:
> Hi,
>
> On 06/12/2015 08
Hello,
How one goes about setting a light source for a scene? I tried by creating
a QDirectionalLight and adding it as a component to my mesh/root node, but
it doesn't show. Is this part of the Qt3D implemented, or is it just an
interface for now?
Here is the a sample code I'm using:
Qt3D::QDirec
71 matches
Mail list logo
