Community

hi everybody,
i am using several worspace (.tws) files; I have created shortcuts of them on my desktop. When I open them (double-clickl), they open *in the same* textpad window, closing the previous one. When I use the context menu/send to/Textpad on the tws file, it opens in a new window.
This is the behaviour I would like to see for double-clicking, too.
Thanks,
Wolfgang

Change the settings for the open command of tws files, add the -m parameter:

-m Start another instance, regardless of the setting for "Allow multiple instances".

Hi,
I tried to add the -m option using regedit,
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TextPad.tws\shell\open\command
but when i double-click the tws file, the entry gets reset (i.e. changed back to the old value).
so, how should i "add the -m option to the open command of tws files".
thanks for your patience,
wolfgang

Do it the official way.

In Explorer, go to folder options (where it is depends on Win version).
Then go to File Types, search for tws, then select Advanced in the bottom box.
Select the open command, click Edit, then add the -m in the
Application used to perform command
and add the -m there.

Might be necessary to remove the check at "Use DDE"

ok, i did as you described.
i am using windows xp. the command line options
for tws is "...textpad.exe" -s
with dde enabled. i change that to "...textpad.exe" -m
and disable dde.
when i double-click on a shortcut to the tws file,
the settings are back to where i started.
double-clicking on a different shortcut to a different
tws file opens the tws in the same window.
so, back to square 1...
thanks again for your help and patience
wolfgang

XP?

Might be necessary to do the change as a user with admin rights....

yes i have admin rights.
if i change the settings for "open", close the dialog,
and open the dialog again, my changes are there.
i double-click on the shortcut to the tws file,
open the dialog again, my changes are gone.
looks like textpad changes the setting back,
or some other weird mechanism does that.
i finally found a work-around though:
i created a new action with a different name
and made that the default action. now it works.
thanks a lot for your help!
wolfgang