Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

to make it faster #11

Closed
GoogleCodeExporter opened this issue Sep 21, 2015 · 2 comments
Closed

to make it faster #11

GoogleCodeExporter opened this issue Sep 21, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

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
Copy link
Author

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
Copy link
Author

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

  • Changed state: Invalid
  • Added labels: Project-Imaging

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant