Am 14.05.12 10:13, schrieb Thiago Macieira:
> On segunda-feira, 14 de maio de 2012 10.03.47, Till Oliver Knoll wrote:
>> However I noticed a warning message in the console output which
>> appears just after the listen() call above:
>>
>>QSocketNotifier: Can only be used with threads started wit
Am 14.05.2012 um 18:34 schrieb Thiago Macieira :
> On segunda-feira, 14 de maio de 2012 17.49.03, Till Oliver Knoll wrote:
>> I prefer:
>>
>> class Foo : public QObject {
>> Q_OBJECT
>> public:
>> FOO_API Foo(); // c'tor
>> FOO_API virtual ~Foo();
>
> ...
>
> If you try to derive from th
Am 14.05.2012 um 20:21 schrieb Michael Jackson :
>
> On May 14, 2012, at 2:00 PM, Till Oliver Knoll wrote:
>
>> Am 14.05.2012 um 16:35 schrieb Mike Jackson :
>>
>>> ...
>>>
>>> 19>QLeeMarchingCubesWidget.obj : error LNK2001: unresolved external
>>> symbol "public: static struct QMetaObject con
Am 14.05.2012 um 16:35 schrieb Mike Jackson :
> ...
>
> 19>QLeeMarchingCubesWidget.obj : error LNK2001: unresolved external
> symbol "public: static struct QMetaObject const
> QFilterWidget::staticMetaObject"
> (?
Hmmm, it just crossed my mind that something else could go wrong here:
staticMeta
On segunda-feira, 14 de maio de 2012 17.49.03, Till Oliver Knoll wrote:
> I prefer:
>
> class Foo : public QObject {
> Q_OBJECT
> public:
> FOO_API Foo(); // c'tor
> FOO_API virtual ~Foo();
That's a bad idea. That causes those problems of missing virtual table and
meta object because the FOO
On May 14, 2012, at 11:49 AM, Till Oliver Knoll wrote:
> 2012/5/14 Michael Jackson :
>>> ...
>>> Could it be that it needs to be:
>>>
>>> PipelineBuilderLib_EXPORT class WFilterWidget : public ...
>>>
>>> instead?
>>> ...
>> Putting "PipelineBuilderLib_EXPORT" before the "class" keyword just re
On May 14, 2012, at 11:54 AM, Till Oliver Knoll wrote:
> 2012/5/14 Mike Jackson :
>> ...
>> The link errors occur when I am creating a plugin library
>> (SurfaceMeshPlugin) which uses the library that the QFilterWidget is
>> compiled into (PipelineLib).
>
> Oh, and just as to rule out the very o
2012/5/14 Mike Jackson :
> ...
> The link errors occur when I am creating a plugin library
> (SurfaceMeshPlugin) which uses the library that the QFilterWidget is
> compiled into (PipelineLib).
Oh, and just as to rule out the very obvious: so I understand you have
at least two DLLs at this point: y
2012/5/14 Michael Jackson :
>> ...
>> Could it be that it needs to be:
>>
>> PipelineBuilderLib_EXPORT class WFilterWidget : public ...
>>
>> instead?
>> ...
> Putting "PipelineBuilderLib_EXPORT" before the "class" keyword just results
> in a bunch of compiler warnings
Ah sorry, my wrong:
http
Jason:
On Fri, May 11, 2012 at 12:15 PM, Jason Dictos wrote:
> What I’ve done to work around this is to always have a dummy item called
> “Loading…” as the first item in the list. Then when that node expands, load
> and replace it. That has turned out to be a pretty good user experience as
> well
Hi Jan
Thanks for your reply. I've responded to a few things inline below.
On Mon, May 14, 2012 at 7:59 AM, Jan Kundrát wrote:
>
> I'd strongly encourage to check your model using ModelTest [1]. The
> trouble with Qt models is that any error you make will usually result in
> subtle errors or se
On May 14, 2012, at 11:17 AM, Till Oliver Knoll wrote:
> Am 14.05.2012 um 16:35 schrieb Mike Jackson :
>
>> ...
>>
>> This is the top part of the class declaration for QFilterWidget:
>> class PipelineBuilderLib_EXPORT QFilterWidget : public QGroupBox
>> {
>> Q_OBJECT;
>> public:
>
> Could it
Am 14.05.2012 um 16:35 schrieb Mike Jackson :
> ...
>
> This is the top part of the class declaration for QFilterWidget:
> class PipelineBuilderLib_EXPORT QFilterWidget : public QGroupBox
> {
>Q_OBJECT;
> public:
Could it be that it needs to be:
PipelineBuilderLib_EXPORT class WFilterWidge
On 04/30/12 20:18, Jan Kundrát wrote:
> Another thing would be to build on top of the QDeclarativeWebViewPrivate
> class, letting it use a specific QNAM -- that must be doable, but looks
> like a huge amount of work (I haven't used *graphical* items implemented
> in C++ from QML yet, just some basi
On 05/11/12 20:25, Adam Light wrote:
> I have tried emitting SourceModel::dataChanged() when a node goes from
> not having children to having children, but that does not cause the view
> to update correctly. Emitting layoutAboutToBeChanged()/layoutChanged()
> *does* cause the view to be updated cor
I am trying to create a shared library for a part of my project that
contains a class derived from QFrame called QFilterWidget. If I build
the code as a shared library I am getting link errors with the
following output.
19>QLeeMarchingCubesWidget.obj : error LNK2001: unresolved external
symbol "pu
2012/5/14 Till Oliver Knoll :
> 2012/5/13 Thiago Macieira :
>> On domingo, 13 de maio de 2012 18.36.02, Till Oliver Knoll wrote:
>>> this seems to be an ever recurring topic: How does one get notified in a
>>> child process (started via QProcess) once there is data to be read on
>>> stdin (in a pla
2012/5/14 Till Oliver Knoll :
>>> ...
>> How about using QSharedMemory for the actual JPEG data, and use either
>> the QLocalServer/Socket or a StdIn/StdOut approach for the notifications
>> that there is something to read? Seems more efficient than (de-)
>> serializing images all the time.
>
> I a
[*sigh* very sorry about that - here again to the proper recipient!]
2012/5/14 André Somers :
>>> ...
>>> How does one get notified in a *child* process (started via QProcess) once
>>> there is data to be read on stdin (in a platform-independent matter - but
>>> for now mostly OS X)?
>> I came
On 14/05/2012 10:06, ext Thiago Macieira wrote:
> The Windows side is very, very complex. Take a look at the
> QProcessPrivate::waitForReadyRead function: it actually does a busy-wait
> trying to read from the pipe and sleeps. It's horrible.
In Qt5 QProcess (on Windows) creates named pipes with o
On 05/11/2012 09:09 PM, ext Pierre-Étienne Messier wrote:
> Hello all,
>
> I wrote a small demo application using a OpenGL render thread similar to
> the solution presented in QQ
> (http://doc.qt.nokia.com/qq/qq06-glimpsing.html#writingmultithreadedglapplications
> / http://mih.voxindeserto.de/thr
Op 13-5-2012 19:51, Till Oliver Knoll schreef:
> Am 13.05.2012 um 18:36 schrieb Till Oliver Knoll:
>
>> Hello,
>>
>> this seems to be an ever recurring topic: How does one get notified in a
>> *child* process (started via QProcess) once there is data to be read on
>> stdin (in a platform-independ
On Mon, May 14, 2012 at 10:05 AM, wrote:
>> In turn, necessitates reloading them by the user code, or alternatively -
>> Can I
>> save the import list off the running App UX QDecelerativeContext - and
>> reload them into the context myself, before the user's code is expecting to
>> find them wh
2012/5/14 Thiago Macieira :
>> > ...
>> > There isn't a platform-independent way.
>>
>> And yet there is a Qt API on the "sender side" (parent process) ...
>
> Because on the parent side, we have the low-level OS structure: a pipe, which
> we createed. ...
Thanks for this very informative reply! :
I will check!
Thanks
2012/5/11 Alex Malyushytskyy :
> Are you sure you need mouse press event?
> Would listening to void QTableWidget::cellPressed ( int row, int column )
> signal help?
>
> If not you can always install event filter, look for
> void QObject::installEventFilter ( QObject * filterO
On segunda-feira, 14 de maio de 2012 10.03.47, Till Oliver Knoll wrote:
> However I noticed a warning message in the console output which
> appears just after the listen() call above:
>
> QSocketNotifier: Can only be used with threads started with QThread
Run the sub-process with QT_FATAL_WARNIN
On segunda-feira, 14 de maio de 2012, às 09.29.11, you wrote:
> 2012/5/13 Thiago Macieira :
> > On domingo, 13 de maio de 2012 18.36.02, Till Oliver Knoll wrote:
> >> this seems to be an ever recurring topic: How does one get notified in a
> >> child process (started via QProcess) once there is dat
Hi,
I thought I'd share some of my experience I made so far with regards
to Mac OS X "Sandboxing" and splitting my application into several
processes which then need to communicate with each other in some way
or another.
The idea is to give the parent process the "Entitlement" file access
(as spe
[Forwarding to the proper recipient]
-- Forwarded message --
From: Till Oliver Knoll
Date: 2012/5/14
Subject: Re: [Interest] QProcess: child read from stdin - no data received?
To: Thiago Macieira
2012/5/13 Thiago Macieira :
> On domingo, 13 de maio de 2012 18.36.02, Till Oliv
[This time to the proper recipient:]
2012/5/13 Thiago Macieira :
> On domingo, 13 de maio de 2012 18.36.02, Till Oliver Knoll wrote:
>> this seems to be an ever recurring topic: How does one get notified in a
>> child process (started via QProcess) once there is data to be read on
>> stdin (in a p
> -Original Message-
> [...]
> Another solution that comes to mind is that if it is a real app flow (e.g.
> not the
> mock up UX test & rate client) I can have the app restarted through the
> platform it runs on. My guess an update warranting a restart will be accepted
> by users. (just li
> -Original Message-
> From: siv...@gmail.com [mailto:siv...@gmail.com] On Behalf Of ext Sivan
> Greenberg
> Sent: Saturday, May 12, 2012 4:45 PM
> To: Koehne Kai (Nokia-MP/Berlin)
> Cc: interest@qt-project.org
> Subject: Re: [Interest] Having two QDeclerativeContexts , setSource of one
>
32 matches
Mail list logo
