Re: Windows MAGICK_CONFIGURE_PATH options

On Fri, 6 Mar 2020, 10bxjfhf wrote:
>
> One would have to; I had a brief look at the Contribute page of GM and was 
> thinking about a wxWidgets version of IMDisplay. That would mean working on

Someone actually did develop a proper wxWidgets-based GUI (much more 
capable than IMDisplay since it supported almost all the available 
operations) using Magick++ a long time ago.  For some reason it did 
not gain any traction and eventually it dissappeared.  However, I 
believe I have a copy of the source code and a sample Windows binary.

The code was based on old wxWidgets and so it would surely require 
some porting to whatever wxWidgets is today.

> two different programs linked to the Magick++ libraries, both trying to use 
> the same config files - no way to really keep things separate as it stands 
> now. And even worse, it would seem, if I wanted to keep a full Graphicsmagick 
> installation for reference or if I needed/wanted to handle 32 & 64-bit 
> versions without cross-interference Who wrote what to which log?
>
> At least I would expect trouble and hence be reluctant to spend the time to 
> try it and fail.

A long journey starts with a single step.  If people were so afraid of 
failure that they don't even start, then Columbus would never have 
discovered America.

> After browsing the code some more, I see that log.mgk seems to support 
> elements like "<include".
>
> Without trying it all directly, I wonder if it might be a way to get what I 
> need?

All of the mgk files do support an include syntax.

> Another approach: Is there any way to intercept the logging events, similar 
> to the error handlers?

I am not aware of any.

Yet another type of event is the progress monitor, and there is a way 
to tap into the progress monitor.

Bob
-- 
Bob Friesenhahn
[email protected], http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/
Public Key,     http://www.simplesystems.org/users/bfriesen/public-key.txt