There is a report in bugzilla that "launch document" doesn't always work for everyone, and it turns out that if you don't have file associations set up properly it will fail. All that "launch document" does is sent a shell command to the OS. I suspect that "launch URL" does the same thing. If that's true, then checking file associations might be the answer.
Two issues with this:
1. If you are deploying an app to many users, you cannot expect them to have things set up a certain way. You must make sure your code covers the contingencies.
2. Even my previous code (prior to Rev's adding launch url) for launching an url failed on Windows. What used to work, now does not. I went back to a previous version of a working app I had created, that I know beyond a doubt launched urls before on my same WinMachine, now it does not. I went back to a build prior to 2.9, with an app that worked. On a machine that worked.
So this isn't a 2.9 issue. Or a new code doesn't work issue. Something must have changed on Windows.
Best guess is that some sort of Windows update has broken it. If this is the case, I'm a bit lost how to repair it. My code cycles thru several attempts to go to a web page, do this, if it fails do that, etc.
That machine hasn't had any new Windows installs, only patch updates. -- Humorous sports t-shirts http://www.villagetshirts.com WlND0WS and MAClNT0SH shareware games http://www.gypsyware.com _______________________________________________ metacard mailing list [email protected] http://lists.runrev.com/mailman/listinfo/metacard
