Community

Can there be a setting which will tell Textpad to always open workspaces in a new instance of Textpad. If I have a workspace that I am working with, and I click on a different workspace it launches in the most recently opened Textpad instance, closing out the workspace that is currently opened in it.

The only work around I have found, is to open a blank Textpad before clicking a workspace. This works well enough, but seems unnecessary.

Am I missing a setting somewhere?

-E

I definitely agree with this one, it would be very useful.

I tried setting it up by making "textpad -m" the command associated with workspace files, this worked until TP re-wrote the registry (which it seems to like to do)!

(bringing topic out of the dustbin)

Any thoughts on this from the textpad people... i don't see that this would be a difficult thing to implament.

-Echo

VoxEcho wrote:(bringing topic out of the dustbin)

Any thoughts on this from the textpad people... i don't see that this would be a difficult thing to implament.

-Echo

And if there are any thoughts, here's a related idea that would tie this up even better ...

There are some things that I always want to do in an instance of TP with no WS. The most common is using the context menu to open a file, because this action is normally unrelated to any workspace I'm in the process of using.

I'd like this action to either a) if there is an instance of TP open without a WS, use that, or b) if there is no such instance, open a new one.

It would be nice if this "open without a workspace" attribute could be optionally applied to each type of opening method - context menu, file association, send-to menu , etc.

Thoughts?

Yep, basic functionality upgrade that's relatively easy to implement - should be done.