[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Scripts
In article <5b0aa74058.John@xxxxxxxxxxxxxxxxxxxxxx>,
John Rickman <rickman@xxxxxxxxxxxxx> wrote:
> In message <bec39d4058.fjgraute@xxxxxxxxx>
> Fred Graute <fjgraute@xxxxxxxxx> wrote:
> >> No, my scripts are not protected. It is something that StrongED is
> >> doing.
> > That seems very unlikely to me as all that StrongED does on a Select
> > click is to issue a *command: "Filer_OpenDir <StrongED$ScriptsDir>".
> > Check filename shown in the title bar of the directory viewer. Is there
> > something odd about it? What happens if you navigate to this directory
> > manually?
> This is what happens:
> Select-click on process icon:
> this opens a filer window containing a the Lua directory
> the title bar says:
> StrongED_Read:Tools.!ScriptSED.Scripts
> Adjust-click on close opens:
> StrongED_Read:Tools.!ScriptSED
> Adjust-click again, opens:
> StrongED_Read:Tools
> Adjust-click again, then
> nothing - ie filer window closes
> But now is the curious thing:
> Select-click on process icon again, opens:
> SCSI::SSD.$.Apps.S1.!StrED_cfg.UserPrefs.Tools.!ScriptSED.Scripts
> Ie it now works as Richard and you say it should.
> Obviously something is not being initialised when I run StrongED.
> I will investigate further.
This seems to be to do with canonicalisation, or lack of. It (or something
very similar - can't remember) happened to me once recently but is not
reproducible. Could it be boot order or speed sensitive? My ARMX6 can be a bit
iffy on Boot after a crash.
Canonicalisation is now something StrongED does - but something it has to
accept!
--
Richard Torrens.
http://StrongED.Torrens.org for StrongEDinstructions (in preparation) and mailing list archives