G'day One convenient thing about having robust exception handling on when an error occurs is that the file path to the file is displayed, and - if one is developing locally - one can copy and paste that into a "File Open" dialogue, and crack on with editing the file. Or at least in CF one can.
On OpenBD the file path is using the wrong separator: a fwd slash instead of a backslash (I'm on Windows here... obviously / would be fine on *nix). This means if one pastes the "path" into a file-open dialogue, the Windows Explorer Shell just goes "huh? Wazzat?". Whilst either slash will work within code, I think using the wrong slash in outwardly-facing situations (like the UI) is suboptimal, as well as being a hindrance (as per above). Is there any reason OBD is using the wrong separator character here? I also notice there's a link next to the file path, which uses the "txmt" protocol, which I am guessing is something to do with TextMate? That's a bit "niche", innit? If the URL was just a "file://" link, then the file would open in whatever app has the file association for that file. Wouldn't that be a better solution? Cheers. -- Adam -- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon official manual: http://www.openbluedragon.org/manual/ Ready2Run CFML http://www.openbluedragon.org/openbdjam/ mailing list - http://groups.google.com/group/openbd?hl=en
