The final version of MNBIOS will come with GUI, you knows, buttons, textboxs, windows, etc. And also will come with mouse pointer. But not all have a mouse!.

So, by defaut the MNBIOS comes with a emulated mouse driver.

i am thinking about this:

Holding pressed <SELECT>:

* the cursors keys act over the mouse pointer.
* <HOME> is the left click
* <DEL> is the right click
* <INS> + <UP> or <DOWN> acts as mouse wheel

what do you thing about that , is it friendly in your msx?

o.O Mouse wheel on MSX?

Pretty cool

Cool!!

Indeed very nice!

I think it would also boost the development of software that uses mouse since every one would be able to use it.

How about acceleration / speed settings? Are they in there?
Maybe later graphic tablet / paddle support?

Surely the settings will be for some real mouse driver... but not for the default emulated driver (i needs to keep that simple and small).

And about, I doing mouses drivers, no.... they are easy to program... just a couple of routine written in a template, i not thinks that i will lose my time in that.

What about using key combinations like ([SHIFT]+)[GRAPH]+[TAB] to loop over selectable GUI elements? IMHO that's a lot more userfriendly than emulation of mouse pointer movements.

And then use [SPACE] / [RETURN] as left-click and (or sumtn) for right-click...

<TAB> or <CTRL>+<TAB> or <CTRL>+<F4> or <GRPH>+<F4> (remplacing ALT) are also in my mind, but they are keyboard events on GUI.

i thought about <SELECT> key as trigger for mouse emulation because it is normaly the only one key unused on the MSX system.

Offcourse all will go ok, only if there is no GHOSTING problems.

Do mice with scrollwheels exist for MSX? If not, would it be difficult to change the connector of a PC mouse?

i only can imagina a way to convert a PS2 mouse for msx usage under MNBIOS and without any circuitry, just changing the plug.

Joystick are actualy output only, and for a ps2 we needs one input and one output signal.

but in msx we have a connector for that on every msx2 and msx2+, it is the cassette connector, but it iirc hasn't a +5v pin.

so only left the printer port that have one!, how?, just doing a output bit permanently 1, and feeds the mouse from that bit.

Quote:

<TAB> or <CTRL>+<TAB> or <CTRL>+<F4> or <GRPH>+<F4> (remplacing ALT) are also in my mind, but they are keyboard events on GUI. i thought about <SELECT> key as trigger for mouse emulation because it is normaly the only one key unused on the MSX system. Offcourse all will go ok, only if there is no GHOSTING problems.

I think, using [SELECT] key as trigger for mouse emulation is not good, even if its normally the only
key unused on the MSX system. This key could or should be used for SELECT sequences comparable
to ESC sequences, maybe to open windows with further input capabilities. This can easily be done
even if you're not so skilled in programming. Mouse emulation is something special and highly related
to the BIOS, and therefore should be done by using more advanced technics, e.g. SNSMAT to get
the [TAB], [CTRL], [GRPH] etc. -- or combinations of that keys -- states for that purpose. A not so skilled programmer will in most cases not be able to do this, but he -- or she -- can do testing on
[SELECT]. So leave the easy things to the beginners, and implement mouse emulation hidden in the
BIOS.

and why not just using <ESC> for escape secuences?

Of course, you should use [ESC] for escape sequences, have I said something different? I like to
have [ESC] key for escaping out of a program or an input routine. I had my Turbo Pascal 3.0 for MSX modified that I could quit the editor by just pressing [ESC] key, that is more quickly than using
[CTRL][K][D]. In Turbo Pascal, it is quite easy to have an alternative key sequence for a sequence
already existing. So ESC suggests the ability to quickly leaving a routine, and we should be care of
such intuitions!

<ESC> is already implemented in LINEINPUT routine. iirc is there in BETA versions.

offcourse <ESC> as a click on the button that have the DefaultCancel property enabled.

the same for <ENTER> as a click on the button that have DefaultAccept property enabled.

and things like this are 200 more to care about.