I am trying to find out 2 things
1) is this a known bug
2) is there a solution or workaround
I am writing an application that needs to use unions of graphics paths and this function flat out does not work. I think it should be an absolute embarassment to have a product out with this kind of hole in it
Thanks
Michael Pau
----- (e-mail address removed) wrote: ----
Are you doing a survey of who knows about the bug or do you have a questio
regarding the bug
try asking this in this newsgroup:
microsoft.public.dotnet.framework.drawing.
You will probably find people who have encountered this problem(bug aka:
Feature) or have a workaround for it.
james
MichaelTPaul said:
I am trying to find out 2 things:
1) is this a known bug?
2) is there a solution or workaround?
I am writing an application that needs to use unions of graphics paths and
this function flat out does not work. I think it should be an absolute
embarassment to have a product out with this kind of hole in it.
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.