Re: Next Version of GDI+ (maybe GDI+ 2.0)

This comes up quite often - its the amount of memory that is required to
convert this into an internal bitmap format used by GDI+. 10000x10000 is a
big image anyway, have you considered resizing it or breaking it up, perhaps
by using a library such as FreeImage (untested).

http://freeimage.sourceforge.net/

James

--
Create interactive diagrams and flowcharts with ERM Diagram at
http://www.crainiate.net

Take the ERM Tour at http://www.flowchartcontrol.com


"Benny" <google@xxxxxxxxxxxxxxxxx> wrote in message
news:1118227284.846209.267750@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Hello,
>
> does somebody know something new about the release of next Version of
> GDI+?
> My last hope was with the release of Visual Studio 2005 and .NET 2.0,
> but my testings yesterday with the Beta 2 showed the same slowness as
> before.
>
> Big mono TIF drawings with a size of more than 10.000x10.000 (around
> 300-500kb) pixel can't load if other applications are open and eating
> ram.
> Smaller Images are working fine like before :/
>
> I'm checking nearly daily Bob Powells faq site for news.
>>>From time to time I'm more frustrated about the GDI+ speed topic.
>
> Greets,
> Benjamin
>


.

Relevant Pages

  • Re: Next Version of GDI+ (maybe GDI+ 2.0)
    ... I have heard that some database handlers do not need to load the full ... > convert this into an internal bitmap format used by GDI+. ... > Create interactive diagrams and flowcharts with ERM Diagram at ...
    (microsoft.public.dotnet.framework.drawing)
  • Re: No DrawFocusRect method?
    ... Answer those GDI+ questions with the GDI+ FAQ ... > Create interactive diagrams and flowcharts with ERM Diagram at ... > Jens Weiermann wrote in message ...
    (microsoft.public.dotnet.framework.drawing)
  • Re: Does GDI+ use hardware acceleration?
    ... It is possible to call GDI routines, such as BitBlt from a GDI+ managed ... application and get the benefit of hardware acceleration that way. ... Create interactive diagrams and flowcharts with ERM Diagram at ...
    (microsoft.public.dotnet.framework.drawing)
Loading