Den 8 dec. 2016 1:02 fm skrev "Ch'Gans" :
>
> Hi,
>
> The documentation of QPainterPathStroker's curve threshold says:
>
> Specifies the curve flattening threshold, controlling the granularity
> with which the generated outlines' curv
Hi,
The documentation of QPainterPathStroker's curve threshold says:
Specifies the curve flattening threshold, controlling the granularity
with which the generated outlines' curve is drawn.
The default threshold is a well adjusted v
Em quarta-feira, 7 de dezembro de 2016, às 10:39:33 PST, Mike Jackson
escreveu:
> Is there a road map for when Qt 5.6.x precompiled binaries would be
> available for VS2017 after it is release? Are we looking at next spring,
> summer or not until 2018?
There is a roadmap: Qt 5.9 will have VS2017
Nevermind, this seems to be tied to strange scoping rules (variables are
"leaking" outside their scope refusing to get their value changed).
Using named templates + params did the trick
Le 07/12/2016 à 17:17, Sébastien Le Ray a écrit :
Hi list,
I've a strange behavior with xsl:variables and
Hi list,
I've a strange behavior with xsl:variables and nested scopes.
First, something like :
Does not work under Qt (xsltproc is fine), tracking down the issue it
appears that $localId is not set when the XPath get evaluated, not a big
deal, I thought, I simply did so
On Wed, Dec 7, 2016 at 8:14 AM, Sean Harmer wrote:
> On Wednesday 07 December 2016 13:03:26 Philip Schuchardt wrote:
> > It doesn't appear to be supported in the current documentation (5.7).
> > Another way to solve this is by rendering each object with a unique
> picking
> > color and the queryi
Is there a road map for when Qt 5.6.x precompiled binaries would be
available for VS2017 after it is release? Are we looking at next spring,
summer or not until 2018?
We are just trying to gauge our plans to move forward from VS2013
tooling and what that time frame might be.
Thank You.
--
Mi
My approach so far is a choice based on lod, from low to high:
- draw nothing
I would despise a system where repeated zoom-outs
eventually resulted in "draw nothing". If you draw
nothing then I am lead to believe that there is
nothing there.
- draw the bounding rect
- draw the rectangles d
On Wednesday 07 December 2016 13:03:26 Philip Schuchardt wrote:
> It doesn't appear to be supported in the current documentation (5.7).
> Another way to solve this is by rendering each object with a unique picking
> color and the querying the pixel color under the mouse. This could
> probably be d
It doesn't appear to be supported in the current documentation (5.7).
Another way to solve this is by rendering each object with a unique picking
color and the querying the pixel color under the mouse. This could
probably be done by setting up a framegraph and use a RenderCapture
(although, I have
Thanks, Gunnar, the patch works!
diff --git a/qmake/generators/win32/msvc_nmake.cpp
b/qmake/generators/win32/msvc_nmake.cpp
index ae139c2..41bec4c 100644
--- a/qmake/generators/win32/msvc_nmake.cpp
+++ b/qmake/generators/win32/msvc_nmake.cpp
@@ -409,14 +409,21 @@ void NmakeMakefileGenerator::init(
On 7 December 2016 at 21:13, Michael Sué wrote:
> Hi,
>
>>I used some naive approach, based on QPainter world transform, and the width,
>>height and area of the bounding box.
>
> You probably know that there is system support for this with the function
> "QStyleOptionGraphicsItem::levelOfDetailF
12 matches
Mail list logo
