Let me clarify it:
I work currently on a bitmap editor and want to edit images pixel by pixel.
I mean using " GetPixel(i,j) and SetPixel(i,j,color) "....
The application has to go through the whole pixels and do the operation by
using" For-Next" loops. It works fine on upto 1000 * 800 bitmaps, but on
higher
resolutions, event with a separate thread for this Sub, the result is really
frustrating. My P4 2.4 GHZ computer hangs and this some times takes a minute
for a simple operation.....
And for the guy who said to use DirectX ....
First of all, direct X does not give all the facilities of GDI+....
Second, I have a lot of limitations concerning the size of my App and its
distribution...
That's why I never go towards DX for those GDI+ operations...
Thanks...
[quoted text, click to view] "Larry Serflaten" <serflaten@usinternet.com> wrote in message
news:u4HgzrVvEHA.1520@TK2MSFTNGP11.phx.gbl...
>
> "Cowboy (Gregory A. Beamer) - MVP" <NoSpamMgbworld@comcast.netNoSpamM>
> wrote
>
>> One issue with VB.NET is when you use the "Crutches" in the language. The
>> extra weight can kill your app if max perf is the issue.
>
> Specifically relating to graphics;
>
> A.
> Dim bmp as Bitmap = New Bitmap(3000,5000)
>
> vs
>
> Dim bmp as Bitmap = New Bitmap(3000,5000, Me.CreateGraphics)
>
>
> B.
> frmGraphics.DrawImage(bmpSource, Dest, Src, GraphicsUnit.Pixel)
>
> vs
>
> frmGraphics.DrawImageUnscaled(bmpSource, 0, 0)
>
>
> The second option in both A and B can significantly increase
> performance in performance critical code. That is to say, there
> are performant routines in the .Net framework, the trick is knowing
> where they are, and how to put them to use...
>
> LFS