PAL ( http://www.adrianboeing.com/pal/index.html )
but I prefer the "Qt way" of doing C++.
Thanks,
d3fault
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
the name of
performance" -- but I can't find the exact quote.
d3fault
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
HBoxLayout *myLayout = new QHBoxLayout();
myLayout->addWidget(new QLabel(tag), 0 /*you might want to use
1 here for stretch*/, Qt::AlignLeft);
myLayout->addWidget(new QPushButton("x"), 0, Qt::AlignRight);
setLayout(myLayout);
}
};
d3fault
___
tc.).
>
If "something in memory" is your requirement, you could give QSettings
a filePath on a tmpfs. Then after the QSettings object has gone out of
scope, open that filePath with QFile.
d3fault
___
Interest mailing list
Interest@qt-proje
mercial modules are useless
to me.
d3fault
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
On 5/13/19, Bernhard Lindner wrote:
>> QFile::rename should rename always or fail! It should never do
>> completely different operation - copy!
>
> I agree.
>
Adding a non-copying rename method to QFile/etc seems justified. Maybe
call it: fastRename, tryRename, or a
uot;signals & slots interface", so
it's guaranteed that all derived classes will ultimately inherit QObject.
Lastly, I'll mention that I didn't come up with any of these techniques. I
picked them up over the years from random blogs/forums/IRC/lists/etc.
d3fault
>
SignalsSlotsInte
e, 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, Interface::someSlot);
>
That does not compile. (even
es, so the above is usually what a solution
looks like
d3fault
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
and since it generates itself, it “generates output
from this application in it’s original […] form”.
Am I incorrect in my interpretation? Does that file need to fulfill
the requirements of the GPLv3? I hope I’m wrong.
Please feel free to surround your response with IANAL
files, rendering
and calling QPdfWriter::newPage() where appropriate.
d3fault
[0] - http://qt-project.org/doc/qt-5.0/qtgui/qpdfwriter.html
[1] -
http://qt-project.org/doc/qt-5.0/qtwebkitexamples/webkitwidgets-framecapture.html
___
Interest mailing list
. Just call QUrl::queryItems()
[3] to get your list. There could be negative implications in doing it
this way, so using QString yourself/manually might be safer.
d3fault
[0] -
http://stackoverflow.com/questions/8582138/how-can-i-split-a-string-according-to-delimiters-in-qt
[1] - http://qt
raeg,
d3fault
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
this.
d3fault
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
I hope they port QtWebkit next, that way I can write my GUI in
html/javascript to then have it rendered by Webkit, which will
incidentally be running as html/javascript. The html/javascript
html/javascript renderer. mind = blown (is dat sum bootstrap?)
Ok I'll shutup now,
d3fault
and Bread Crumbs would
be drag-n-drop enabled breadcrumbs, where hovering over the breadcrumb
while holding down the mouse during a drag-n-drop changes to the
folder for dropping into. Xfce's file manager does this, though it
does copy/paste instead of cut/paste.
d3fault
in videographicsitem.pro and videoplayer.cpp
d3fault
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
want? Or should I steal the code from
however signals/slots does it?
d3fault
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
the args
m_ArgHolder1 = customArg1;
m_ArgHolder2 = customArg2;
}
void YourObjectThread::run()
{
//pass them in
YourObject *obj = new YourObject(m_ArgHolder1, m_ArgHolder2);
exec();
delete obj;
}
d3fault
-project.org/pipermail/releasing/2012-September/000634.html
d3fault
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
++ 98 compliant.
MOC can definitely do this :). At least hackily (signals/slots are
hacks imo... just really amazing ones!!!).
For now I still think just with a single T it's a pretty sweet/clean
design. I hope I don't run into unforeseen problems during the rewrite
=o.
d3fault
(thanks to all those who contributed to
that, directly or indirectly).
I think I'm just going to stick with QThread. Choose the right tool
for the job.
d3fault
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo
, SIGNAL(clicked()), obj,
SLOT(doSomethingPleaseAndThankYou()));
connect(obj, SIGNAL(somethingHappenedDde()), this,
SLOT(handleSomeoneStoleMyCarDude()));
//etc
}
New Qt class or what?
d3fault
___
Interest mailing list
Interest@qt
Quick fix:
On 10/23/12, d3fault d3faultdot...@gmail.com wrote:
emit readyForConnections(obj); //Would be dangerous to call methods
etc on this object. Should only connect to it's signals/slots
What I meant to say is that listeners to that signal should not call
methods on the object
on a per-project basis isn't a dirty hack
(separation of concerns!)... and if QtConcurrent really performs that
much better... I'll probably use it for the rewrite. Thanks :)
d3fault
___
Interest mailing list
Interest@qt-project.org
http://lists.qt
/iteration. Example: read an image,
convert it, write it to disk, schedule another. You'd be IO bound so the
threading overhead would be cheap by comparison.
d3fault
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo
changed them to
pointers (I remember this subject being discussed a while ago on the
mailing list. delete ends up being called on non-new'd variables or
something).
d3fault
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org
guh sorry wrong list
mfw 2012 and we still have to change that
On Oct 21, 2012 10:20 PM, d3fault d3faultdot...@gmail.com wrote:
volatile bools work, but just know that every time you check it you are
doing a non-cached memory read (relatively slow). It can't read from the
cache/registers (much
-4.8/qtextstream.html#RealNumberNotation-enum
http://qt-project.org/doc/qt-4.8/qstring.html#number-2
http://qt-project.org/doc/qt-4.8/qstring.html#argument-formats
d3fault
Alex
On Fri, Oct 5, 2012 at 3:59 PM, Rui Maciel rui.mac...@gmail.com wrote:
Is it possible to manipulate QTextStream so
it to the
application layer fml). A proper solution requires more thought. It
probably wouldn't be too complicated. Famous last words?
Such a class could greatly simplify application protocol creation.
Weee http://xkcd.com/1081/
d3fault
___
Interest mailing
figure it out from the context. You mean message re-ordering?
Reminder to Konrad: Don't use any of my protocols, ever.
d3fault
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
in the receiver's transport layer... worthless
information to the sender's application layer). Can now stop the
re-transmit timeout or whatever.
You're right about one thing: this argument is futile.
d3fault
___
Interest mailing list
Interest@qt-project.org
http
.
I don't think anyone's proposing doing that... as it would break in a lot
of cases but it's still 'possible'
This discussion isn't going anywhere anymore, but I sure learned a lot :)
d3fault
___
Interest mailing list
Interest@qt-project.org
, if that was the case.
I tried looking through the Qt source for an answer, but really
couldn't even find any related code (Ima newb to Qt internals).
qtcpsocket.cpp, qtcpsocket.h, and qtcpsocket_p.h told me nothing.
[0] - http://qt-project.org/doc/qt-4.8/qabstractsocket.html#details
d3fault
::Acknowledged() [signal] though not necessarily
anything to do with QNAM (especially since the QNetworkReply makes a
better acknowledgement in that case lol (and now I'm just confusing
myself)).
[0] -
http://en.wikipedia.org/wiki/Transmission_Control_Protocol#Reliable_transmission
d3fault
like an ugly hack imo.
What would you guys recommend?
d3fault
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
? Any suggestions on re-using buffers in those
situations (am I missing something)?
d3fault
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
The DiagramScene example included with Qt should help. It has nodes and
arrows that are re-drawn when the nodes are moved. Check out
DiagramItem::itemChange in diagramitem.cpp and the Arrow class itself.
d3fault
___
Interest mailing list
Interest@qt
-Nokia/
d3fault
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
to share it?
I also don't agree with the recent subject change to OT. This is very
much on topic if you are intested in Qt's future.
d3fault
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
large in general for the community to even finish before it even gets
to a maintainable status. I'll be sad if we lose QTheQuick along with it
:-/.
d3fault
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo
work on Qt (which is the same long term effect as Microsoft
buying Nokia), then we could stop wondering what to do and literally
everyone would agree on the fork and we'd just do it... now.
d3fault
___
Interest mailing list
Interest@qt-project.org
http
to be an interesting next few months,
d3fault
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
On Fri, Jun 15, 2012 at 12:02 PM, Thiago Macieira thiago.macie...@intel.com
wrote:
On sexta-feira, 15 de junho de 2012 11.42.07, d3fault wrote:
The Qt Trademark and the Nokia Corporation might die (except Qt won't
ever
'officially' die. It's in Nokia/Microsoft's best interest to not let
?)... but Microsoft will pressure
Nokia into keeping it non-BSD regardless. Should Microsoft buy Nokia, they
wouldn't want it to be BSD'd either, for obvious reasons (more permissive
license = attracts more developers = less .Net developers = less vendor
lock-in = less money in their pocket).
d3fault
you and were being forced to work on certain features
that you didn't think belonged in the Qt Project *cough*QML*cough* sorry
there's a phallic object lodged in my throat ok I'll shut up now).
d3fault
___
Interest mailing list
Interest@qt-project.org
http
that moves out of Qt is
still considered a part of Qt. I bet a lot of the modules that were never
in QtBase aren't included in the BSD Clause either.
On Fri, Jun 15, 2012 at 3:43 PM, Thiago Macieira
thiago.macie...@intel.comwrote:
On sexta-feira, 15 de junho de 2012 15.35.52, d3fault wrote
.
Alternatively... how about a more noob friendly Qt-Interest list? Some
people get off on helping noobs (helps them sleep better at night I
guess)... but I think most of us just get annoyed by his(her?) noise.
d3fault
Alex
Le 15/02/2012 14:34, Sujan Dasmahapatra a écrit :
Dear Friends
Can we
48 matches
Mail list logo
