Re: [StrongED] Re: Export from StrongED

[Fred Graute <fjgraute@xxxxxxxxx>]

In message <5700af181ddave@xxxxxxxxxxxxx>
          Dave Symes <dave@xxxxxxxxxxxxx> wrote:

> In article <b18c750057.fjgraute@xxxxxxxxx>,
>    Fred Graute <fjgraute@xxxxxxxxx> wrote:
> > In message <mpro.p9jm6500fgn2h08bx.pittdj@xxxxxxxxxxxx>
> >           David Pitt <pittdj@xxxxxxxxxxxx> wrote:

[snip]

> > > Reinstate this line from 4.69f9 :-
> > > Set StrongED$ExportDir <StrongED$ScrapDir>
> > > into SE4.70a12's !StrED_cfg.UserPrefs.StartUp.UserInit
> >
> > Yes, that's how it's supposed to be. :-)
> 
> Ye gods, how is a geezer supposed to understand all this stuff...
> 
> My SE4.70a12  "!StrED_cfg.UserPrefs.StartUp.UserInit" file  already
> contains that line, as shown above, but it still will not exportSED.

The error you mentioned in an earlier post is this:

  19:03:18.16 ** WimpError ** from ExportSED
    Error  : &00000000
    Message: Invalid MessageTrans descriptor block (code254)
  19:03:22.57 TaskClose &5A603A18 ExportSED

Is that still the case?

If so, then it's an error in ExportSED and not in the system variables.
It's an error I've not seen from ExportSED and I've no idea (yet) what
the cause might be.

> Maybe it's because two lines below the above noted line is this:
> 
> Do IfThere StrongED_Read:Tools.!ScriptSED Then Obey
> StrongED_Read:Tools.!ScriptSED.!Boot

ScriptSED is completely unrelated to ExportSED.

> Hasn't someone already noted the SED script is not in .Tools but somewhere
> else... Checks...
> 
> Oh yes... "Defaults.Tools.!ExportSED"

That's not a problem. StrongED uses a two tier lookup to locate its
resources. First it looks in UserPrefs and if not found there then it
looks in Defaults.

Cheers,
Fred.

-- 
StrongED Developer
http://www.stronged.iconbar.com/

-- 
To unsubscribe send a mail to StrongED+unsubscribe@xxxxxxxxxxx
List archives and instructions at
http://stronged.torrens.org/index.html