Thanks a lot!!
I realized I have put forword a stupid question. And now I know what I can do
with LCMS.
James Burgess <[EMAIL PROTECTED]> 写道：
I have used the LCMS library in an MFC application. It worked just
fine. LCMS (as Guy pointed out) has got nothing to do with whether
you application is a command line based on or a windowed one. The
library itself doesn't do any kind of console I/O so there is no
concern there.
Specifically though you can call sprintf from a MFC application if
that was your concern. Nothing in the lcms library needs to be
rewritten to link it into an MFC application. Microsoft puts routines
like sprintf in what they call the C Runtime Library often referred
to as the crt.
Also you say looking at the command line code is difficult. This is
confusing since MFC applications are vastly more complex than command
line ones. Maybe you are looking at the command line utilities and
wondering how to convert them into an windowed MFC application?
That's not really anything to do with LCMS and is a rather large topic.
- James
On Jun 4, 2008, at 8:34 PM, Guy K. Kloss wrote:
> On Thu, 05 Jun 2008 3:11:12 pm 小草 wrote:
>> If i want to call some of the functions, i have to rewrite them in
>> VC MFC
>> functions, ig, replace "sprintf" with "AfxMessageBox" or
>> something, so as
>> to use them in my MFC programmes. I wonder if anyone else
>> encounters the
>> same problem?
>
> I don't get what you mean.
>
> sprintf is not to generate output, but to create a formated string.
> And LCMS
> is a library, not an end user application. So it should be used
> that way, and
> it MUST be kept as openly/freely usable as possible. That includes
> keeping
> things like Wintendo/Microsoft specifica out as well as any POSIX
> specifica.
> If it has to deal with them, then they must be abstracted out into
> some
> utility code that behaves differently on every platform
>
> As for your problem: You should be just able to use LCMS in your
> environment
> to code against its API and use it. It shouldn't handle any output,
> dialogues, messages, etc. for you, that's YOUR task.
>
> However, on the subject of error handling I have to complain a bit,
> too.
> Setting an error handler is nice, but that's not really possible
> within some
> applications. An exception with proper exception handling would be
> preferable
> for that reason. But that note is besides the track of your
> request ...
>
> Guy
>
> --
> Guy K. Kloss
> Institute of Information and Mathematical Sciences
> Te Kura Putaiao o Mohiohio me Pangarau
> Room 2.63, Quad Block A Building
> Massey University, Auckland, Albany
> Private Bag 102 904, North Shore Mail Centre
> voice: +64 9 414-0800 ext. 9585 fax: +64 9 441-8181
> eMail: [EMAIL PROTECTED] http://iims.massey.ac.nz
> ----------------------------------------------------------------------
> ---
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/
> index.php_______________________________________________
> Lcms-user mailing list
> Lcms-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/lcms-user
---------------------------------
雅虎邮箱，您的终生邮箱！-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Lcms-user mailing list
Lcms-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lcms-user
