On Tue, 17 Jan 2006, Adam wrote:
Anyway, the reason I'm posting here... JMB says:
"The other issue (of running an application whose !Run file is
typed to HTML) is so unlikely to occur in the real world that
I'm not inclined to fix it."
Well, fair enough - it's not a big bug! I only came across it by chance in
constructing my (unrelated) bug report. Presumably, however, the very fact
I happened across it means it's not /wildly/ unlikely - and surely it's
still a "bug", if a minor one.
I didn't say it wasn't; I just said it wasn't worth fixing. As my comment
said, this situation only arises when an application's Run file is typed
as HTML and NetSurf is already running.
Also - why does it happen? I thought double-clicking an application
same as Filer_Run-ing the !Run file?
Not quite. The Filer broadcasts a DataOpen message for the file
double-clicked on (so in the case of an application, it'll fill in the
message's type field with that reserved for application (&1000, iirc)). If
this then bounces, the Filer will then look for an Alias$@RunType_XXX
variable (where XXX is the type of the application's Run file). If one is
found, the Filer will issue the equivalent of *@RunType_XXX ...!App.!Run
If none is found, you get an error message informing you that the Filer
can't find an application to handle the file you clicked on.
In the case of double-clicking on the Run file, the Filer will broadcast
a DataOpen with the Run file's information contained within it. Bounce
behaviour is the same as for applications.