| Groups | Blog | Home |
dotnet drawing api : What site contains the OctreeQuantizer code you'd recommend
Once I saw an implementation of OctreeQuantizer that did not require the
Unsafe keyword. Now that I want it I can't find it. Do you know how to find that site? Also do you have a comment about reasons for using the "safe" or the "unsafe" OctreeQuantizer code. What site contains the code you'd recommend? Thanks
I got it.
What's the down side of unsafe code for a Windows application? Thanks [quoted text, click to view] "Bob Powell [MVP]" <bob@spamkillerbobpowell.net> wrote in message news:77397E75-A709-4E8F-A8FC-E991B38AD858@microsoft.com... > The article has been moved or deleted from MSDN. I wish those guys would > learn to keep reference links constant! > > Here is another article on the same subject: > http://msdn2.microsoft.com/en-us/library/aa479306.aspx > > The reason for using unsafe code in any graphics application is of course > speed. Direct access to memory via a pointer is guaranteed to be faster > than any other method and optimization of graphics processing is > important. > > > -- > -- > Bob Powell [MVP] > Visual C#, System.Drawing > > Ramuseco Limited .NET consulting > http://www.ramuseco.com > > Find great Windows Forms articles in Windows Forms Tips and Tricks > http://www.bobpowell.net/tipstricks.htm > > Answer those GDI+ questions with the GDI+ FAQ > http://www.bobpowell.net/faqmain.htm > > All new articles provide code in C# and VB.NET. > Subscribe to the RSS feeds provided and never miss a new article. > > > "Academia" <academiaNOSPAM@a-znet.com> wrote in message > news:OsmuQ07MIHA.5720@TK2MSFTNGP04.phx.gbl... >> Once I saw an implementation of OctreeQuantizer that did not require the >> Unsafe keyword. >> >> Now that I want it I can't find it. >> >> Do you know how to find that site? >> >> Also do you have a comment about reasons for using the "safe" or the >> "unsafe" OctreeQuantizer code. >> >> >> >> What site contains the code you'd recommend? >> >> >> >> >> >> Thanks >> >> >> >> >> >> >> >> >
The article has been moved or deleted from MSDN. I wish those guys would
learn to keep reference links constant! Here is another article on the same subject: http://msdn2.microsoft.com/en-us/library/aa479306.aspx The reason for using unsafe code in any graphics application is of course speed. Direct access to memory via a pointer is guaranteed to be faster than any other method and optimization of graphics processing is important. -- -- Bob Powell [MVP] Visual C#, System.Drawing Ramuseco Limited .NET consulting http://www.ramuseco.com Find great Windows Forms articles in Windows Forms Tips and Tricks http://www.bobpowell.net/tipstricks.htm Answer those GDI+ questions with the GDI+ FAQ http://www.bobpowell.net/faqmain.htm All new articles provide code in C# and VB.NET. Subscribe to the RSS feeds provided and never miss a new article. [quoted text, click to view] "Academia" <academiaNOSPAM@a-znet.com> wrote in message
news:OsmuQ07MIHA.5720@TK2MSFTNGP04.phx.gbl... > Once I saw an implementation of OctreeQuantizer that did not require the > Unsafe keyword. > > Now that I want it I can't find it. > > Do you know how to find that site? > > Also do you have a comment about reasons for using the "safe" or the > "unsafe" OctreeQuantizer code. > > > > What site contains the code you'd recommend? > > > > > > Thanks > > > > > > > >
In my opinion, the only possible downside to unsafe code is that the
requirement to understand the physical layout in memory of an object or data structure is still of paramount importance whereas safe code takes that responsibility away from the programmer and lightens the load. For an old C++ programmer like me it's a useful and fast tool. -- -- Bob Powell [MVP] Visual C#, System.Drawing Ramuseco Limited .NET consulting http://www.ramuseco.com Find great Windows Forms articles in Windows Forms Tips and Tricks http://www.bobpowell.net/tipstricks.htm Answer those GDI+ questions with the GDI+ FAQ http://www.bobpowell.net/faqmain.htm All new articles provide code in C# and VB.NET. Subscribe to the RSS feeds provided and never miss a new article. [quoted text, click to view] "Academia" <academiaNOSPAM@a-znet.com> wrote in message
news:er$DCBDNIHA.5988@TK2MSFTNGP02.phx.gbl... >I got it. > > What's the down side of unsafe code for a Windows application? > > Thanks > > "Bob Powell [MVP]" <bob@spamkillerbobpowell.net> wrote in message > news:77397E75-A709-4E8F-A8FC-E991B38AD858@microsoft.com... >> The article has been moved or deleted from MSDN. I wish those guys would >> learn to keep reference links constant! >> >> Here is another article on the same subject: >> http://msdn2.microsoft.com/en-us/library/aa479306.aspx >> >> The reason for using unsafe code in any graphics application is of course >> speed. Direct access to memory via a pointer is guaranteed to be faster >> than any other method and optimization of graphics processing is >> important. >> >> >> -- >> -- >> Bob Powell [MVP] >> Visual C#, System.Drawing >> >> Ramuseco Limited .NET consulting >> http://www.ramuseco.com >> >> Find great Windows Forms articles in Windows Forms Tips and Tricks >> http://www.bobpowell.net/tipstricks.htm >> >> Answer those GDI+ questions with the GDI+ FAQ >> http://www.bobpowell.net/faqmain.htm >> >> All new articles provide code in C# and VB.NET. >> Subscribe to the RSS feeds provided and never miss a new article. >> >> >> "Academia" <academiaNOSPAM@a-znet.com> wrote in message >> news:OsmuQ07MIHA.5720@TK2MSFTNGP04.phx.gbl... >>> Once I saw an implementation of OctreeQuantizer that did not require the >>> Unsafe keyword. >>> >>> Now that I want it I can't find it. >>> >>> Do you know how to find that site? >>> >>> Also do you have a comment about reasons for using the "safe" or the >>> "unsafe" OctreeQuantizer code. >>> >>> >>> >>> What site contains the code you'd recommend? >>> >>> >>> >>> >>> >>> Thanks >>> >>> >>> >>> >>> >>> >>> >>> >> > >
I kind of guessed that maybe the user might need more Windows privileges or
something. Thanks, that's good to know. [quoted text, click to view] "Bob Powell [MVP]" <bob@spamkillerbobpowell.net> wrote in message news:86BFEC24-D182-4D58-B608-59525B41696C@microsoft.com... > In my opinion, the only possible downside to unsafe code is that the > requirement to understand the physical layout in memory of an object or > data structure is still of paramount importance whereas safe code takes > that responsibility away from the programmer and lightens the load. > > For an old C++ programmer like me it's a useful and fast tool. > > -- > -- > Bob Powell [MVP] > Visual C#, System.Drawing > > Ramuseco Limited .NET consulting > http://www.ramuseco.com > > Find great Windows Forms articles in Windows Forms Tips and Tricks > http://www.bobpowell.net/tipstricks.htm > > Answer those GDI+ questions with the GDI+ FAQ > http://www.bobpowell.net/faqmain.htm > > All new articles provide code in C# and VB.NET. > Subscribe to the RSS feeds provided and never miss a new article. > > > "Academia" <academiaNOSPAM@a-znet.com> wrote in message > news:er$DCBDNIHA.5988@TK2MSFTNGP02.phx.gbl... >>I got it. >> >> What's the down side of unsafe code for a Windows application? >> >> Thanks >> >> "Bob Powell [MVP]" <bob@spamkillerbobpowell.net> wrote in message >> news:77397E75-A709-4E8F-A8FC-E991B38AD858@microsoft.com... >>> The article has been moved or deleted from MSDN. I wish those guys would >>> learn to keep reference links constant! >>> >>> Here is another article on the same subject: >>> http://msdn2.microsoft.com/en-us/library/aa479306.aspx >>> >>> The reason for using unsafe code in any graphics application is of >>> course speed. Direct access to memory via a pointer is guaranteed to be >>> faster than any other method and optimization of graphics processing is >>> important. >>> >>> >>> -- >>> -- >>> Bob Powell [MVP] >>> Visual C#, System.Drawing >>> >>> Ramuseco Limited .NET consulting >>> http://www.ramuseco.com >>> >>> Find great Windows Forms articles in Windows Forms Tips and Tricks >>> http://www.bobpowell.net/tipstricks.htm >>> >>> Answer those GDI+ questions with the GDI+ FAQ >>> http://www.bobpowell.net/faqmain.htm >>> >>> All new articles provide code in C# and VB.NET. >>> Subscribe to the RSS feeds provided and never miss a new article. >>> >>> >>> "Academia" <academiaNOSPAM@a-znet.com> wrote in message >>> news:OsmuQ07MIHA.5720@TK2MSFTNGP04.phx.gbl... >>>> Once I saw an implementation of OctreeQuantizer that did not require >>>> the Unsafe keyword. >>>> >>>> Now that I want it I can't find it. >>>> >>>> Do you know how to find that site? >>>> >>>> Also do you have a comment about reasons for using the "safe" or the >>>> "unsafe" OctreeQuantizer code. >>>> >>>> >>>> >>>> What site contains the code you'd recommend? >>>> >>>> >>>> >>>> >>>> >>>> Thanks >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>> >> >> >
Hi Bob,
I guess you know pointers are not always guaranteed to be faster. Bounds checks can be removed by the JIT compiler in some cases, and I was surprised to find some low level rendering code was about equal in speed accessing memory directly using pointers, or using an array of unsigned integers (4 bytes per pixel). Byte arrays are not especially fast using the CLR, but for 4 byte size elements, arrays are about as fast as pointer access. The primary thing to avoid is marshalling data. Regards, Frank Hileman check out VG.net: http://www.vgdotnet.com Animated vector graphics system Integrated Visual Studio graphics editor [quoted text, click to view] "Bob Powell [MVP]" <bob@spamkillerbobpowell.net> wrote in message news:77397E75-A709-4E8F-A8FC-E991B38AD858@microsoft.com... > The article has been moved or deleted from MSDN. I wish those guys would > learn to keep reference links constant! > > Here is another article on the same subject: > http://msdn2.microsoft.com/en-us/library/aa479306.aspx > > The reason for using unsafe code in any graphics application is of course > speed. Direct access to memory via a pointer is guaranteed to be faster > than any other method and optimization of graphics processing is > important. > > > -- > -- > Bob Powell [MVP] > Visual C#, System.Drawing > > Ramuseco Limited .NET consulting > http://www.ramuseco.com > > Find great Windows Forms articles in Windows Forms Tips and Tricks > http://www.bobpowell.net/tipstricks.htm > > Answer those GDI+ questions with the GDI+ FAQ > http://www.bobpowell.net/faqmain.htm > > All new articles provide code in C# and VB.NET. > Subscribe to the RSS feeds provided and never miss a new article. > > > "Academia" <academiaNOSPAM@a-znet.com> wrote in message > news:OsmuQ07MIHA.5720@TK2MSFTNGP04.phx.gbl... >> Once I saw an implementation of OctreeQuantizer that did not require the >> Unsafe keyword. >> >> Now that I want it I can't find it. >> >> Do you know how to find that site? >> >> Also do you have a comment about reasons for using the "safe" or the >> "unsafe" OctreeQuantizer code. >> >> >> >> What site contains the code you'd recommend? >> >> >> >> >> >> Thanks >> >> >> >> >> >> >> >> >
Hi Frank,
You're definitely right about the chunk size. Actually images are aligned on four byte boundaries for just this reason. Thanks for pointing this out. -- -- Bob Powell [MVP] Visual C#, System.Drawing Ramuseco Limited .NET consulting http://www.ramuseco.com Find great Windows Forms articles in Windows Forms Tips and Tricks http://www.bobpowell.net/tipstricks.htm Answer those GDI+ questions with the GDI+ FAQ http://www.bobpowell.net/faqmain.htm All new articles provide code in C# and VB.NET. Subscribe to the RSS feeds provided and never miss a new article. [quoted text, click to view] "Frank Hileman" <frankhil@no.spamming.prodigesoftware.com> wrote in message
news:%23EaXBGoNIHA.4808@TK2MSFTNGP05.phx.gbl... > Hi Bob, > > I guess you know pointers are not always guaranteed to be faster. Bounds > checks can be removed by the JIT compiler in some cases, and I was > surprised to find some low level rendering code was about equal in speed > accessing memory directly using pointers, or using an array of unsigned > integers (4 bytes per pixel). Byte arrays are not especially fast using > the CLR, but for 4 byte size elements, arrays are about as fast as pointer > access. The primary thing to avoid is marshalling data. > > Regards, > Frank Hileman > > check out VG.net: http://www.vgdotnet.com > Animated vector graphics system > Integrated Visual Studio graphics editor > > "Bob Powell [MVP]" <bob@spamkillerbobpowell.net> wrote in message > news:77397E75-A709-4E8F-A8FC-E991B38AD858@microsoft.com... >> The article has been moved or deleted from MSDN. I wish those guys would >> learn to keep reference links constant! >> >> Here is another article on the same subject: >> http://msdn2.microsoft.com/en-us/library/aa479306.aspx >> >> The reason for using unsafe code in any graphics application is of course >> speed. Direct access to memory via a pointer is guaranteed to be faster >> than any other method and optimization of graphics processing is >> important. >> >> >> -- >> -- >> Bob Powell [MVP] >> Visual C#, System.Drawing >> >> Ramuseco Limited .NET consulting >> http://www.ramuseco.com >> >> Find great Windows Forms articles in Windows Forms Tips and Tricks >> http://www.bobpowell.net/tipstricks.htm >> >> Answer those GDI+ questions with the GDI+ FAQ >> http://www.bobpowell.net/faqmain.htm >> >> All new articles provide code in C# and VB.NET. >> Subscribe to the RSS feeds provided and never miss a new article. >> >> >> "Academia" <academiaNOSPAM@a-znet.com> wrote in message >> news:OsmuQ07MIHA.5720@TK2MSFTNGP04.phx.gbl... >>> Once I saw an implementation of OctreeQuantizer that did not require the >>> Unsafe keyword. >>> >>> Now that I want it I can't find it. >>> >>> Do you know how to find that site? >>> >>> Also do you have a comment about reasons for using the "safe" or the >>> "unsafe" OctreeQuantizer code. >>> >>> >>> >>> What site contains the code you'd recommend? >>> >>> >>> >>> >>> >>> Thanks >>> >>> >>> >>> >>> >>> >>> >>> >> > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |