The Win32 API offers very limited image conversion. There are many third party libraries, some free, others not. I'm currently looking at CxImage to replace Leadtools, which is now even more expensive than before and isn't royalty free. If you are willing to pay more, one royalty free library I've used is http://www.gdpicture.com/[^]. The ActiveX part always annoyed me, but it had a good PDF viewer component, so I lived with it. I'm also going to evaluate http://www.data-tech.com/products/imaging/imageman-dll.aspx[^]. (I work for none of these companies.)
If you are interested in audio development, I made a simple SDK to tag audio libraries patches. There is ton of things people are waiting for on this topic: - analyze a WAV file and extract tagging informations (Percussive, Smooth ...) - extract informations from REX files and convert them in tags
Plug-ins can be .NET assemblies or native DLL
as Universal Patch Finder is free, the idea is to let all of this entirely free.
Where would I specify this directory in Visual C++ 6.0
Are you working in MFC, if yes then you can use the class wizard to generate the class based from OCX,TLB or DLL
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow Never mind - my own stupidity is the source of every "problem" - Mixture
<pre lang="text"> What is the basic difference in processing system messages in MFC? Should I use message map or WindowProc? In my included sample the WindowProc get executed first ( as expected ) , but I really do not do any message processing in this case. So my secondary question would be - what is considered by OS as processed message? </pre>
Never. MFC has an inbuilt message pump and MessageProc() handler which distributes the messages according to your MESSAGE_MAP entries. If you add your own MessageProc() then you break the connection between those entries and your message handlers.
One of these days I'm going to think of a really clever signature.
I would agree with NEVER... use message maps in MFC. If you find it doesn't do something specific that you needs, that's when you go around the framework, other than that... it's best to try to use the framework that's there.
Messages use WindowProcs, but MFC handles that for you. There's really very few cases where you'd have to go around what MFC already does. Only reason to code your own WindowProcs would really be if you're doing native Win32 coding.
Last Visit: 31-Dec-99 19:00 Last Update: 10-Dec-16 18:20