[Terminal] midnight commander can't be controlled by a mouse

[diver]

Both konsole and gnome-terminal can control mc by a mouse, but our terminal don't.

[bonefish]

That's just a missing feature. :-)

[oco]

Patch that add mouse support (xterm mode 1003 for now)

[oco]

Here is a patch that should help with this missing feature. At least, it is enough to have mouse support in the freepascal text mode IDE.

[diver]

Great! Did you tried midnight commander? Just ssh to some unix box with mc installed.

[oco]

No, i don't have this here. According to ​http://mc.redhat-club/svn/trunk/FAQ, you may need to invoke "mc -x"

[diver]

​http://mc.redhat-club.org/svn/trunk/FAQ

[axeld]

Thanks oco, applied in hrev30268! There were a number of things to note about your, though:

• The array size of the "destBuffer" was one byte too small.
• Coding style requires upper caps to delimit variables, not underscores; xterm_x, xterm_buttons become xtermX, and xtermButtons.
• Since we're using C++, it's preferred to declare variables when you need them, not at the beginning of a function.
• If you only add a few lines, and need to indent the whole long rest of a function, it's often clearer if you return from your special case, and leave the rest of the code unchanged.
• When you add a TODO comment, it's usually useful to write the comment directly next to the "TODO" so that when you grep for TODO, you will see at least part of the comment (to get an idea).

I'll keep this bug open until we have the confirmation it'll work with midnight commander.

[oco]

After looking at ​http://www.midnight-commander.org/browser/src/mouse.c, midnight commander user xterm mode 1000. A new patch will be needed.

[oco]

Patch that implement xterm mouse mode 9, 1000 and 1002

[oco]

Here is a new patch that implement 3 others xterm mouse mode : 9, 1000, 1002. Only mode 1000 was tested (the freepascal IDE could support it). The remaining mode 1001 (mouse highlight tracking) is not implemented. I have no plan to implement it as i don't fully understand how it should work.

[axeld]

Thanks, I've applied it in hrev30374.

I have some remarks again, though:

• please don't use names like "Btn" - always prefer more descriptive names like "Button" in this case (I've already changed that in the patch). OTOH redundant long naming like SetReportX10Mouse(bool reportX10Mouse) should be avoided.
• When having so many boolean flags, maybe a "uint32 fReportFlags" would be more appropriate; I haven't changed this, though.
• please honour the 80 character per line limit.