> On Oct 7, 2017, at 8:00 PM, Christian Gagneraud wrote:
>
> On 8 October 2017 at 06:27, Patrick Stinson wrote:
>> Hmm. Actually, I think that the elastic node example is implemented in the
>> same way as my app. Because of the delayed response of the “elasticity” in
>> the algorithm it is not
On 8 October 2017 at 06:27, Patrick Stinson wrote:
> Hmm. Actually, I think that the elastic node example is implemented in the
> same way as my app. Because of the delayed response of the “elasticity” in
> the algorithm it is not possible to demonstrate a solution to my problem
> even if it solve
On 10/07/2017 05:15 PM, interest-requ...@qt-project.org wrote:
On Saturday, 7 October 2017 14:58:03 EDT Andy wrote:
I don't really want to play the "pile on" game (and sorry for hijacking
the
current thread), however as someone who cares about Qt and has been using
it for a long time this is
> Can you suggest a sample size,
8 or 16 maybe ? I find 4 to be a bit pixelated.
> or perhaps give a code example?
QOpenGLWidget* w = new QOpenGLWidget;;
auto fmt = QSurfaceFormat::getDefaultFormat();
fmt.setSamples(16);
w->setFormat(fmt);
view.setViewport(w);
---
Je
On Sat, Oct 7, 2017 at 4:11 PM, Thiago Macieira
wrote:
> On Saturday, 7 October 2017 14:58:03 EDT Andy wrote:
> > I don't really want to play the "pile on" game (and sorry for hijacking
> the
> > current thread), however as someone who cares about Qt and has been using
> > it for a long time this
On Saturday, 7 October 2017 14:58:03 EDT Andy wrote:
> I don't really want to play the "pile on" game (and sorry for hijacking the
> current thread), however as someone who cares about Qt and has been using
> it for a long time this is a particular source of real frustration.
>
> Bug reports often
On Saturday, 7 October 2017 13:27:50 EDT Krzysztof Kawa wrote:
> I don't want to be mean Thiago, because I love Qt, I do appreciate
> your hard work and all the people that make it happen, but you need to
> consider that you're pretty big part of Qt and things around you do
> move in a different pa
I don't really want to play the "pile on" game (and sorry for hijacking the
current thread), however as someone who cares about Qt and has been using
it for a long time this is a particular source of real frustration.
Bug reports often get labelled as "Reported" and then ignored (the
"priority" on
Hmm. Actually, I think that the elastic node example is implemented in the same
way as my app. Because of the delayed response of the “elasticity” in the
algorithm it is not possible to demonstrate a solution to my problem even if it
solved it.
Like the elastic node example, I am implementing Q
Interesting. Can you suggest a sample size, or perhaps give a code example? I’m
sure how this works. Thanks!
> On Oct 7, 2017, at 10:01 AM, Jean-Michaël Celerier
> wrote:
>
> > Don't do that and the anti-aliasing will work.
>
> Or alternatively enable GL antialiasing for instance by using
>
That is correct, this did fix the antialiasing issue at the expense of
performance. I suppose it is a trade off.
> On Oct 7, 2017, at 1:09 AM, Christian Gagneraud wrote:
>
>> On 7 October 2017 at 16:11, Patrick Stinson wrote:
>>
>> Hello!
>>
>> I am seeing the antialiasing is still quite gra
I don't want to be mean Thiago, because I love Qt, I do appreciate
your hard work and all the people that make it happen, but you need to
consider that you're pretty big part of Qt and things around you do
move in a different pace. It's not the same for some of us.
As an example consider this P2 bu
> Don't do that and the anti-aliasing will work.
Or alternatively enable GL antialiasing for instance by using
QSurfaceFormat::setSamples (
http://doc.qt.io/qt-5/qsurfaceformat.html#setSamples) and passing the
format to your GL viewport. However this ends up being quite slow on retina
display in m
On Saturday, 7 October 2017 05:49:00 PDT Roland Hughes wrote:
> I expect, like all OpenSource bugs, it will be ignored until the version
> it is reported against is no longer supported, then it will become a
> "closed" bug.
Except for all the bugs that I close, which are only about the open source
Bug filed.
https://bugreports.qt.io/browse/QTBUG-63650
I expect, like all OpenSource bugs, it will be ignored until the version
it is reported against is no longer supported, then it will become a
"closed" bug.
Thanks for the reporting link though.
On 10/05/2017 05:11 PM, Irfan Omair wrote
On Donnerstag, 5. Oktober 2017 22:25:23 CEST Allan Sandfeld Jensen wrote:
> On Donnerstag, 5. Oktober 2017 21:45:34 CEST Jan Neumann wrote:
> > Hi,
> >
> > I am on Archlinux.
> > We have packages in AUR which should provide widevine, one of them
> > especially for
> > [qt5-webengine](https://aur.a
On 7 October 2017 at 16:11, Patrick Stinson wrote:
>
> Hello!
>
> I am seeing the antialiasing is still quite grainy using a QGraphicsView on
> mac. Is it possible to increase the device pixel ratio, or something similar?
>
> See attached screenshots, expanding to full rez before viewing. Note
>
On 7 October 2017 at 16:08, Patrick Stinson wrote:
> Hi there!
>
> I have a graph-ish diagram app where dragging some objects (like nodes)
> necessitates dragging other objects (like connecting edges). However, if I
> update an edge from the mouse event or ItemChanged(position) event then the
>
18 matches
Mail list logo
