Hmm. That seems backwards to me; surely the logic would be more useful if a specified image file over-rode the embedded image? Then simply starting the VM would run the embedded image but d-click on an image would run that image.
The use case is for securely distributing applications. So one *doesn't* want to allow a vm with an embedded image to run an arbitrary image. It *must* run the image embedded within it.
>
>
> Log Message:
> -----------
> Finish arg parsing work for embedded images on Windows. Don't attempt to open
> argv[1] as an image if there is an embedded image.
tim
--
tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim
Strange OpCodes: WDS: Warp Drive, Scotty!