>
> Sure enough, If I "Turn on ClearType"
>
> Start->ControlPane->Display->
> AdjustClearTypeText/TurnOnClearType
>
> The fonts are rendered anti-aliased.
> But, I think I told Qt to override this with
>
> painter.setRenderHint(QPainter::TextAntialiasing,true);
>
> Also, I don't think
Am Dienstag, 3. Februar 2015, 11:36:55 schrieb Felix morack:
> we had a similar problem. We solved it by having the updatePixamp()
> function set a flag and doing the actual drawing the in paint() method, ie:
> [...]
This is what Michael also suggested. I tried it, the quality of the pixmap is
mu
Am Dienstag, 3. Februar 2015, 11:29:05 schrieb Ilya Diallo:
> Not sure it's related, but that reminds me of that old issue:
> https://bugreports.qt.io/browse/QTBUG-25896
Yes, looks very similar...
--
Alexander
___
Interest mailing list
Interest@qt-proj
Am Dienstag, 3. Februar 2015, 11:06:08 schrieb Michael Sué:
> You can set a breakpoint in Curve::Paint, go up in the stack trace and look
> for yourself. It is way more than just QPixmap pixmap(width,height).
I'll do that. But maybe later :-)
> But seeing your attachment I have another idea: Ther
Am Dienstag, 3. Februar 2015, 10:59:44 schrieb René J.V. Bertin:
> I have no experience whatsoever in doing this kind of thing in Qt, but
> looking at the 2 images in the OP it strikes me that the image prepared in
> the background simply has (been scaled up from) a much lower resolution.
No, there
(So this time I *am* cross-posting a message from lldb-dev ...)
Jim, you're invited to send an example .o file you get warnings about to Greg
Clayton (directly), so he can try to figure out what's going on. I presume the
offer extends to others too, but it's probably counter-productive if we ope
How does Xcode do it? Xcode is quite reliable stepping through code.
> On Feb 3, 2015, at 10:37 AM, André Pönitz wrote:
>
> In any case, that's not really caused by Qt, and there's also not much Qt
> Creator can do about.
-John Weeks
___
Interest mai
On Tuesday February 03 2015 19:37:21 André Pönitz wrote:
...
> In any case, that's not really caused by Qt, and there's also not much Qt
> Creator can do about. I've seen it happening myself, and when it happens,
...
Thanks, I'll transfer the information!
René
___
On Mon, Feb 02, 2015 at 03:11:48PM -0800, Jim Prouty wrote:
> I'm hoping someone can tell me how we can fix our Qt development environment
> to avoid this frustration:
>
> Way too often Qt Creator 3.3 completely locks up when it hits certain
> breakpoints in our app using our self-compiled Qt 5.4.
Hi,
issue is solved. I forgot to set a parent for C++ object.
QML was able to take ownership of the object.
http://doc.qt.io/qt-5/qtqml-cppintegration-data.html
Changing object creation to
*TestObject *testObject = new TestObject(&myObjectListModel);*
solves the problem with the crashes.
Git re
we had a similar problem. We solved it by having the updatePixamp()
function set a flag and doing the actual drawing the in paint() method, ie:
void updatePixamp()
{
dirty = true;
repaint();
}
void repaint(...)
{
if(dirty)
{
//update pixmap
}
//blit pixamp to screen
}
2015-02-03 11:29
Not sure it's related, but that reminds me of that old issue:
https://bugreports.qt.io/browse/QTBUG-25896
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
> Yes, I think so too. Now I just need to understand the difference between
> the
> QPainter passed to QGraphicsImem::paint() and the painter I localy create in
> Curve::updatePixmap(). On the other hand, what I'm doing in
> updatePixmap() is
> pretty much the standard way to draw on a QPixmap acco
Am Dienstag, 3. Februar 2015, 10:18:10 schrieben Sie:
> Here I do not mean the image you attached to your first mail. I mean the
> QPixmap you create in Curve::updatePixmap(), which is the one that then
> gets scaled afterwards, which itself is the JPG you attached, or not? If
> the QPixmap of Curv
> This was what we did before. But for big data sets (say > 50k points) painting
> of the lines and symbols is slow.
I understand completely.
> > 1) Does your QPixmap look correct if you save it to a file?
> No.
Here I do not mean the image you attached to your first mail. I mean the
QPixmap you
Am Dienstag, 3. Februar 2015, 09:40:02 schrieb Michael Sué:
> 1) Does your QPixmap look correct if you save it to a file?
No.
> 2) We do something similar in a QGraphicsView derived class with the
> following differences:
>
> - we use a QImage object (as we have to fill it pixel by pixel)
> - we
Hello all,
I’m currently using Qt3D 1.0 - I intend to upgrade to 2.0 ASAP but at this
point, for the purposes of finishing my university project, I need to stick
with the previous version.
I have a few questions about ownership of various objects passed to
QGLSceneNode. For example, setTransfo
1) Does your QPixmap look correct if you save it to a file?
2) We do something similar in a QGraphicsView derived class with the following
differences:
- we use a QImage object (as we have to fill it pixel by pixel)
- we draw the QImage in drawBackground
This way SmoothPixeltransform works def
> Which Qt version?
> https://bugreports.qt.io/browse/QTBUG-42330
> Is perhaps related?
4.8.5 in openSuse 13.1
Actually, without painter.setRenderHint(QPainter::SmoothPixmapTransform,
true); the quality is even worser... But I don't really understand why this
render hint has an effect at all.
Which Qt version?
https://bugreports.qt.io/browse/QTBUG-42330
Is perhaps related?
Harri
On 03/02/2015 08:55, Alexander Semke wrote:
Hi,
I'm one of the developers of LabPlot, a KDE-application for interactive
plotting and analysis of data. I'm struggling with a problem since long time
that pr
20 matches
Mail list logo
