I have a serious problem. I am using PureBasic to create a texture browser DLL for my main program. The problem is that the program fails to load any image other than a bitmap, when compiled in a DLL. It works fine as an executable.
There seems to be some weird interaction that causes the decoders to fail when some other DLL's are called (also PureBasic), but it usually works on its' own. There is no pattern I can find, and the error doesn't really seem to be dependent on my code, but rather, just the way PB does things internally.
I am requesting a better method to force use of the image decoders. I am presently loading the image in the main program, then creating a new PB image, and copying the pixels, but this method is very slow. I have been developing this program for months, and now I am looking at the possibility of it being potentially crippled because of this issue I cannot control.
Image Decoders Fail in DLL - major issue for my application
I take it you are using all the *Decoder() procedures?
If you can provide some source that outlines the problem I'm sure someone can make a suggestion (or a bug report!).
If you can provide some source that outlines the problem I'm sure someone can make a suggestion (or a bug report!).
-Mitchell
Check out kBilling for all your billing software needs!
http://www.k-billing.com
Code Signing / Authenticode Certificates (Get rid of those Unknown Publisher warnings!)
http://codesigning.ksoftware.net
Check out kBilling for all your billing software needs!
http://www.k-billing.com
Code Signing / Authenticode Certificates (Get rid of those Unknown Publisher warnings!)
http://codesigning.ksoftware.net
Is what product dead?
You just said that you can't reproduce the problem you see. Perhaps it isn't a problem with PB at all? It sounds like the project you speak of is pretty large, so the problem could be many places..
What exactly happens? You say it fails, but you don't say how, when or with what image. Can you provide some source code or even an image that causes it to fail?
If you can provide some circumstance or code that defines the problem I'm positive someone will fix it. I have several image manipulation programs working very well, written in PB, using the encoders and decoders native to PB.
You just said that you can't reproduce the problem you see. Perhaps it isn't a problem with PB at all? It sounds like the project you speak of is pretty large, so the problem could be many places..
What exactly happens? You say it fails, but you don't say how, when or with what image. Can you provide some source code or even an image that causes it to fail?
If you can provide some circumstance or code that defines the problem I'm positive someone will fix it. I have several image manipulation programs working very well, written in PB, using the encoders and decoders native to PB.
-Mitchell
Check out kBilling for all your billing software needs!
http://www.k-billing.com
Code Signing / Authenticode Certificates (Get rid of those Unknown Publisher warnings!)
http://codesigning.ksoftware.net
Check out kBilling for all your billing software needs!
http://www.k-billing.com
Code Signing / Authenticode Certificates (Get rid of those Unknown Publisher warnings!)
http://codesigning.ksoftware.net
Can you show any examples of this happening? Again, nothing can be done if all this is just speculation. Fred and company need working examples (or, rather, broken ones)!
-Mitchell
Check out kBilling for all your billing software needs!
http://www.k-billing.com
Code Signing / Authenticode Certificates (Get rid of those Unknown Publisher warnings!)
http://codesigning.ksoftware.net
Check out kBilling for all your billing software needs!
http://www.k-billing.com
Code Signing / Authenticode Certificates (Get rid of those Unknown Publisher warnings!)
http://codesigning.ksoftware.net

