[softwarelist] Re: Odd DPlngScan error
- From: Chris Johnson <chris@xxxxxxxxxxxxxxxxxxxxx>
- To: davidpilling@xxxxxxxxxxxxx
- Date: Wed, 07 Dec 2016 20:10:50 +0000 (GMT)
In article <mpro.ohtvhl003fvk30sn2.pittdj@xxxxxxxxxxxx>,
David Pitt <pittdj@xxxxxxxxxxxx> wrote:
It turns out to be a first time around vanilla start up thing.
In the download zip !DPlngScan.!BInstall has this :-
Set Alias$@RunType_C85 Run <DPlngScan$Dir>.!Run %%*0
However double click to run in Choices is off by default.
The multiple instances occur under these conditions.
Yes - I had come to similar thoughts myself, but had not yet got
around to running more tests.
It is basically a question of what the filer and wimp do when a file
is double clicked. It is first offered to all the running programs.
If nothing responds to the wimp message to say 'I'll load the file',
the alias$@runtype is then looked at and the appropriate app is run
with the filename as a cmd parameter. If the alias@run type points to
DPScan, which has initially ignored the load request, then it will be
run. I haven't looked at the source, but I assume that DPScan still
refuses to load the file. Thus a second instance but no image load.
On my system, the Alias$@RunType_C85 points to ChangeFSI after boot,
and DPScan does not seem to change it when it is run. Aaah, trying to
recall contents of source files, I think DPScan rewrites the file
!BInstall when you save your config - yes - mine is datestamped
earlier this evening. The !BInstall contents will reflect the config
settings, and will be changed when new settings are saved. However,
any changes will only take effect after a reboot and rerun - the
alias@ run type var will not be unset on the fly.
It looks like this is due to changing config on the fly, and the two
getting out of step.
I'll have a proper think about this to see if anything needs changing
to remove any ambiguity in the behaviour.
--
Chris Johnson
To unsubscribe or subscribe goto:
//www.freelists.org/list/davidpilling
Other related posts:
