A few complaints about my trial of slickedit

[agottem]

Just a few issues I've noticed:


Issue A:

1.  Set the save configuration option to 'Save configuration immediately' (under Application Options > Exit).

2.  Open multiple slickedits

3.  Modify the configuration in one of the most recently launched instances of SE

4.  Observe, you'll see the error: "Failed to save configuration to <path>, Access Denied", click OK, now you'll see the message: "Unable to save the configuration Do you want to exit anyway?" (even though I wasn't trying to exit!), click any of the buttons (yes/no/cancel).  This brings you back to the start of 4, with the access denied message.

5.  The only way to get out of this infinite loop is to close all other instances of slickedit so the configuration can be saved.


Issue B:

Launch slickedit without it loading the last used workspace.  There doesn't seem to be an option to have slickedit start without loading any workspace.  This doesn't really cause any problems, it's just slightly annoying...as I don't want to be loading a workspace I'm not using.


Issue C:

Undo / Redo...seriously, cursor movements erase the redo buffer?  I understand for some this may be desirable behavior, but I'd imagine for others it's completely opposite of what they'd expect.  There are many times I want to undo -> look around the code a little -> redo the changes.  With the current slickedit behavior...I need to be extremely cautious that I don't accidentally move the cursor, otherwise I lose my redo buffer!

This, honestly, is kind of a big deal for me.


Issue D:

I'd like my insertion mode to be sticky.  If I switch to block selection mode, I'd like it to stay there until I switch back.


All the above issues were using v15 of slickedit on Windows.

[SlickEdit Support]

Hi there,

A) Start SlickEdit with the "-st 0" invocation option.

B) Tools-->Options-->Application Options-->Auto Restore-->Set "Auto restore workspace files" to False.
Before you set this you'll need to load a hotfix that resolves and issue with this setting not "sticking". The hotfix is two small files that you can download and load at http://www.slickedit.com/index.php?option=com_content&view=article&id=260&Itemid=41

C) Unfortunately there isn't an option for this yet. (Depending on where you've made a save(s) you can always Diff using Backup History (File-->Backup History for...))

D) Can you be a little more specific on what you're looking for here?

Thanks for the feedback!

[agottem]

Thanks for the reply, I'll give your solutions a try and let you know how they work.

With regards to D:

I'm coming from the 'Crimson Editor' community.  With crimson editor, you hit 'alt-c' to switch to 'column editing mode'.

When in column editing mode, the cursor moves as it normally would with a few changes:

1.  You can move the cursor anywhere, even columns that "don't exist" (similar to how you can right click&hold anywhere in SE, and select content passed the end-of-line).

2.  If you hold the shift key down while in 'column editing mode' you select blocks of text (the equivalent of switching to block selection mode, and selecting text with the arrow keys).

With crimson editor, I stay in column editing mode until I hit 'alt-c' again to switch back to normal selection.  Hope that clarifies it...if not, crimson editor is free now..so you can try it out yourself

[Clark]

Try binding the "brief_select_block" command to a key. This is pretty similar the Crimson editor but you use the arrow keys and not shift+arrows to select.

[mjdl]

The original poster's issue C (undo/redo) is something I'd like to see as an option too, perhaps by being able to select undo/redo mode that records only actual textual changes, ignoring cursor movements. But I understand that this may not be easily changed in the underlying Slickedit core.

In the meantime, I religiously save the file before every set of changes. This allows using the diff command with the automatically recorded file versions to double check my changes whenever I need to. It's a different way of working, that's all, but quite effective when one *really* needs to back out from changes, since the recorded backup versions are there already.