Pascal Georges wrote:
Hi!
> On my Suse distro I get a crash after "package require
> tdom" ... Would it be possible to incorporate the
> necessary code in Scid ? As a workaround I wrote catch {
> package require tdom } so Scid can be launched, but for
> the least this exception should be caught if no other
> solution is possible (that is inhibit correspondance stuff
> if tdom is missing).
I've added some logic that will disable _internal_
Xfcc-suppot if tDOM fails. It will also disable the ability
to switch it on. Config will store an "off" state, so later
on one could reenable it if a working tDOM is available.
As only the internal Xfcc-interface requires tDOM, all other
fuctions of CC will be usable without it and of course one
could use an external helper for Xfcc.
I'd still prefer a working tcl implementation though, but if
the libs provided by tcl do not work as expected that will
be a bit hard for me to achieve.
--
Kind regards, / War is Peace.
| Freedom is Slavery.
Alexander Wagner | Ignorance is Strength.
|
| Theory : G. Orwell, "1984"
/ In practice: USA, since 2001
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Scid-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/scid-users
