LineMover 1.1 does not work

Tom,

Oops !

I have mapped the actions to Ctrl-Shift-Up/Down since ages. With the
latest update it stopped working: no reaction, when pressing
Ctrl-Shift-Up/Down, although still mapped without conflicts. Do others
also have this problem?

>

I'm afraid it's caused by
- my renaming the actions, and
plus
- IDEA being silent about orphans shortcut mappings.

I did so for naming consistency when I added the 2 news actions, and
their shortcuts, Alt-Shift-Ctrl I/K,
BUT I didn't think about the annoying result.

Sorry.

Alain

Alain Ravet wrote:

I'm afraid it's caused by
- my renaming the actions, and
plus
- IDEA being silent about orphans shortcut mappings.

>


I'm going to fix this now - reuse the old names, so if you can wait a
little..

Alain

Could you please add these actions to a menu, too? Thanks in advance for
this nice little tool. It's hard without it - like without Rearranger or
other plugins I have installed :)

Tom

Should I, or Should I NOT?
Please vote.


Tom,

Could you please add these actions to a menu, too?

I was about to post the fix, but I'll wait a little.

What do people think about adding a new entry in the Edit Menu, with the
4 line mover actions ?

Example:

Menu:
Edit
LineMover
Up
Down
Top
Bottom

NO.


reason:
- the menu is already bloated,
and
- these are keyboard only actions.

Alain

If you mind cluttering the Edit menu with 4 new actions (BTW, I just
knew Move Up/Down), you can create a submenu "Move Line(s)" in the Edit
menu, containing your 4 actions.

Tom

- these are keyboard only actions.

I don't understand this. Why shouldn't they work from the menu (if
placed there)?

BTW, putting them into the menu makes the user able to find them without
reading an extra documentation, that they are mapped by default to
Xxx+Yyy/zzz.

Tom

Tom

>> - these are keyboard only actions.
>

I don't understand this. Why shouldn't they work from the menu (if
placed there)?

They would, of could, but that wouldn't be an efficient to use them, so
there must be another reason to bloat the menu...

BTW, putting them into the menu makes the user able to find them
without reading an extra documentation, that they are mapped by
default to Xxx+Yyy/zzz.

I agree. It makes me think about making 2 versions: 1 silent, and 1 that
install itself in the Edit Menu.
But then, I will bloat the plugin repository :(

Alain

I agree. It makes me think about making 2 versions: 1 silent, and 1 that
install itself in the Edit Menu.
But then, I will bloat the plugin repository :(

Alain

So have the "Put in Edit menu" feature configurable
Amnon

Amnon

>> I agree. It makes me think about making 2 versions: 1 silent, and 1
>> that install itself in the Edit Menu.
>> But then, I will bloat the plugin repository :(
>>
>> Alain
>
>

So have the "Put in Edit menu" feature configurable

But then I would bloat the config dialog, just to add 1 checkbox !? :(



And btw, there is still talk about having this feature being implemente
into standard IDEA. This would allow adding a small checkbox somewhere
in an official dialog.


Alain

Yeah, I guess you're right.

Hey, may be IDEA menus should behave like MS Office ('collapse' unused
menu items over time).

Is that something Linux using people are used to as well?

Amnon

Alain Ravet wrote:

Amnon

>>> I agree. It makes me think about making 2 versions: 1 silent, and 1
>>> that install itself in the Edit Menu.
>>> But then, I will bloat the plugin repository :(
>>>
>>> Alain
>>
>>
>>
>> So have the "Put in Edit menu" feature configurable

But then I would bloat the config dialog, just to add 1 checkbox !? :(



And btw, there is still talk about having this feature being implemente
into standard IDEA. This would allow adding a small checkbox somewhere
in an official dialog.


Alain

Hey, may be IDEA menus should behave like MS Office ('collapse' unused
menu items over time).

NO! This is a terrible GUI blooper, because the visual content of the
menus change, which confuse the user ("I know, somewhere in the left
most menu, there was menu item Xxx, but I cannot find it any more.").

Tom

Alain Ravet wrote:

What do people think about adding a new entry in the Edit Menu, with the
4 line mover actions ?

I say go for it, it a lot more useful than the "Delete" action in the
edit menu. I like the name "Move Line(s)" for the submenu better than
"LineMover" though.

Bas

Thomas Singer (MoTJ) wrote:

BTW, putting them into the menu makes the user able to find them without
reading an extra documentation, that they are mapped by default to
Xxx+Yyy/zzz.

+1 for the documentation aspect

+/-0 for adding anything to the edit menu, I don't use it anyway. I'd also
prefer a submenu over 4 new entries though.

Sascha

TS> submenu "Move Line(s)" in the
TS> Edit menu, containing your 4 actions.

+0.5 The edit menu is not that cluttered.

Doesn't much matter. The line moving functionality was just announced as implemented in-product in build 3201. Congratulations, LineMover is now legacy.

--Dave Griffith

Dave Griffith wrote:

>The line moving functionality was just announced as implemented in-product in build 3201. Congratulations, LineMover is now legacy.

>


It's funny, but I'm a little sad my request was eventually implemented,
after 29 months!!
All good stories have an end...



To those who may find it useful, the lates build still offers 2 "unique"
actions

Move selected text to Bottom of file
Move selected text to Top of file

I use them to clear my plain text todo files, à-la double Bubble-sort
way: what's important goes up, what's less important goes down. I wonder
if other people would find this useful. I'll maintain it for myself,
anyway..

Alain