search

ARLM-Keller / aforge

Automatically exported from code.google.com/p/aforge
0 stars 0 forks source link

to make it faster #11

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
if you remember we discussed it before and you said that removing locks
will increase the performance i think that this is the solution for that

What steps will reproduce the problem?
1. make methods which directly inputs Bitmapdata
2. make class which handles locking and unlocking of images

What is the expected output? What do you see instead?
faster application and image processing

What version of the product are you using? On what operating system?
[13.06.2006] - Version 2.3.0 winXP

Original issue reported on code.google.com by amar.cha...@gmail.com on 20 Jan 2007 at 2:37

GoogleCodeExporter commented 8 years ago 
sorry i don't want to submit it as a defect but as an enhancement

Original comment by amar.cha...@gmail.com on 20 Jan 2007 at 2:39

GoogleCodeExporter commented 8 years ago 
Please, take a closer look to the AForge.Imaging library from AForge.NET (not 
stand-
alone version). In this library you can find that both IFilter and 
IInPlaceFilter 
have methods to work with already locked data - they work with BitmapData.

So, it looks like you requested for something, what is already implemented.

Original comment by andrew.k...@gmail.com on 20 Jan 2007 at 2:44