Ok… I found an old RealBasic/Studio post that showed how to start/stop GDI+
and when I implement it… I get the dashed lines I expected…
HOWEVER… I get nothing else … comment out that code… and use solid lines… and all works
Gotta love Windows… (well no, actually I don’t 
)
Direct2d will do it, and since Mac and Windows now can both do dashes, no reason for Xojo not to expose the ability.
At some time.
https://msdn.microsoft.com/en-us/library/windows/desktop/dd371301(v=vs.85).aspx
Oh the feeels, they cuts me, cuuuts to the heart 
They are still in there Dave, they still work 
Dave, post a test program highlighting the problem I’ll take a look.
[quote=340452:@Jeff Tullin]Direct2d will do it, and since Mac and Windows now can both do dashes, no reason for Xojo not to expose the ability.
[/quote]
That has been true for a LONG time, along with a lot of other graphics capabilities… The lowest common denominator these days OS wise is a LOT higher than what the Xojo framework supports , and has been for a LONG time.
[quote=340484:@]Oh the feeels, they cuts me, cuuuts to the heart
They are still in there Dave, they still work
Dave, post a test program highlighting the problem I’ll take a look.[/quote]
Not worth taking the effort to produce a sample project…
It doesn’t work, informatin from 3 Xojo engineers indicate that it doesn’t work, the suggestion of one allowed it do draw dashed lines at the cost of drawing anything else… I have posted the declares above…
For now I have a work around that doesn’t sacrifice much speed for Windows users
[quote=340452:@Jeff Tullin]Direct2d will do it, and since Mac and Windows now can both do dashes, no reason for Xojo not to expose the ability.
At some time.
https://msdn.microsoft.com/en-us/library/windows/desktop/dd371301(v=vs.85).aspx[/quote]
but nobody seems to know how to utilize it, or if they didn’t they are not talking
Would it kill you to post an example and see if the community comes up with an answer? The community (mainly Julian) already figured out some very fundamental flaw on the windows side which has been present since forever it seems, and that until now it was erroneously thought to be some win32 vs .net limitation. Why not give him a chance.
PLEASE REFER TO ABOVE… THE CODE IS POSTED ALREADY