Flexible Editor and Asscociated Program Settings
Posted: Sat Sep 01, 2007 2:59 pm
Did the suggestion in this post ever get implemented?
http://newsgroup.xnview.com/viewtopic.php?t=4834
If so, please could someone direct me to how to do this. If not, I'd like to add my request for something similar.
I've just spent some time setting up XnView as a front-end to the PhotoShop Elements editor. It's 100 times better than the Elements "Organiser", but I found this part of the process very tricky, particularly under Vista.
I think XnView should have its own settings for which programs edit and view which filetypes, instead of relying on the operating system defaults, for three reasons:
1. It's actually a very tricky piece of registry editing, since you first have to find the HKCR\.{filetype} item, then find where this is pointing, then in that location create shell\edit\command and shell\open\command items. There's not a lot of help abuut on how to do this.
2. If you install some other software it could easily blow this away and you're back to square one.
3. You might want to have XnView use an editor which is not the operating system default for the filetype.
Please can we reconsider this? Editing the INI file would be fine if a user interface is too much work, but XnView really should have its own settings for this.
Don't get me wrong. I think XnView is a great program and makes Elements much more usable, but this would be a real improvement.
Andrew
http://newsgroup.xnview.com/viewtopic.php?t=4834
If so, please could someone direct me to how to do this. If not, I'd like to add my request for something similar.
I've just spent some time setting up XnView as a front-end to the PhotoShop Elements editor. It's 100 times better than the Elements "Organiser", but I found this part of the process very tricky, particularly under Vista.
I think XnView should have its own settings for which programs edit and view which filetypes, instead of relying on the operating system defaults, for three reasons:
1. It's actually a very tricky piece of registry editing, since you first have to find the HKCR\.{filetype} item, then find where this is pointing, then in that location create shell\edit\command and shell\open\command items. There's not a lot of help abuut on how to do this.
2. If you install some other software it could easily blow this away and you're back to square one.
3. You might want to have XnView use an editor which is not the operating system default for the filetype.
Please can we reconsider this? Editing the INI file would be fine if a user interface is too much work, but XnView really should have its own settings for this.
Don't get me wrong. I think XnView is a great program and makes Elements much more usable, but this would be a real improvement.
Andrew
