Please help testing upcoming openMSX release!

Page 19/61
12 | 13 | 14 | 15 | 16 | 17 | 18 | | 20 | 21 | 22 | 23 | 24

By pgimeno

Champion (293)

pgimeno's picture

14-05-2020, 22:10

Manuel wrote:

I also had an idea to make the info panel expandable (with some button on it?) to show more detailed information, like the used CPU/frequency and whatever people come up with (ideas?).

Screen Hz

By donluca

Expert (75)

donluca's picture

14-05-2020, 23:43

Here's the output:

Key pressed, unicode: 0x0000, keyCode: 0x0012d, keyName: CAPSLOCK
Changing CAPS lock state according to SDL request

And it stays like that with the CAPS status led continuously blinking on and off, but as soon as I focus another window on macOS it tells me

Key released, keyCode: 0x40012d, keyName: CAPSLOCK,RELEASE
Changing CAPS lock state according to SDL request

and the CAPS led goes off and when I focus the openMSX window again, even though I have CAPS LOCK active on my keyboard on macOS, it isn't active in openMSX.

Also, a very small bug: with the console open, if I try to paste text, it pastes it in Basic instead of inside the console Tongue

By Manuel

Ascended (18073)

Manuel's picture

15-05-2020, 00:32

Aha, so openMSX never received a key release event!
You get the same blinking if you keep your MSX caps lock key pressed.

Are more people experiencing this issue?

The paste was intentionally implemented like that, but it is a nice idea to be able to paste in the console as well. I'll think about how to do that.

By Grauw

Ascended (10005)

Grauw's picture

15-05-2020, 03:25

Manuel wrote:

Aha, so openMSX never received a key release event!
You get the same blinking if you keep your MSX caps lock key pressed.

Are more people experiencing this issue?

I don’t on the built-in keyboard of my Macbook Pro 16" 2019, macOS 10.15.4, keyboard input set to US (international). I built it myself, could be a macOS or Xcode version issue with SDL2. Or a keyboard language setting problem, what if you change it? I also have an 8-year-old Apple bluetooth keyboard laying about somewhere, I could also try that, though I doubt the bluetooth would be the problem…

By ren

Paragon (1855)

ren's picture

15-05-2020, 12:40

Quote:

Well, you only get that drop dialog if it's ambiguous what should happen. So if there is only one cartridge slot, or one diskdrive, it doesn't show. As I said in the first reply, most of the devs already found it a bit overkill to have a dialog at all. So I'd rather not introduce such a dialog in all cases and for all file types that are dropped.

I'm not talking about introducing something new here, just instead of showing 'Select cartridge slot', you could e.g. display 'Select to which cartridge slot Cheese Shooter (1988)(Anma Soft).rom should be assigned'. Or: 'Cheese Shooter (1988)(Anma Soft).rom dropped. Select cartridge slot:' (the title font size would probably need to be made smaller to accommodate for that).

Are there configuration possibilities what extensions are recognized as disk image or ROM file? (Though the default is probably quite in order.)

Quote:

Yeah, the OSD menu does scale. I should rewrite that info panel some day so that it also scales. At first I didn't do that, because at 4x for instance, it takes only a little bit of space in the border. But if it would also scale along, it always takes the same relative space of your MSX screen. I'd rather have it in a not so overlapping place.

I quite like it keeps the same scaling as it's at 1x/2x. As a result you have more room at 3x or 4x. OTOH there's something to say for scaling with the factor like the OSD menu/dialogs. Again: at >= 3x a smaller font size could be used (resulting in more space available). Or that could be made user configurable?

Quote:

I also had an idea to make the info panel expandable (with some button on it?) to show more detailed information, like the used CPU/frequency and whatever people come up with (ideas?).

Yes, so I think the CPU freq would be neat as well (e.g. able to tell MSX2+ runs in turbo mode).
Perhaps an user slot layout (so e.g. 2 cart slots for NMS 8250) displaying what's inserted (instead of the current 'Running software'.) Also show what's inserted in the disk drives when there's a ROM running. Perhaps add another row. Wouldn't become to high/big IMO, as you bring up the panel briefly anyway (as it's an OSD element in the way of the MSX screen (and/or LEDs)) Would be a different story if the MSX screen had framing around it (like blueMSX). What comes to mind now is that it would also be an interesting/cool option to have an auxiliary window in which the info panel (or a variation of it) could be open all of the time. And/or a break-out console window? Smile

As a side note: personally I don't run in FS that much, mostly 3x or 4x windowed. Btw: it's not possible to change the console bg opacity is it?

Another thing I was thinking about, as you brought of the issue of little room available in the info panel: ever thought about tooltips at mouse over? (O/c that could interfere w/ the MSX mouse..)

About an expandable panel: so by default show the standard user cart. slots (and drives) the machine has, and what's in them (empty or not). If there's a slot expander inserted, that could be expanded via a toggle perhaps? (And then there's o/c the possibility of a cassette, HDD(s) and/or ...)

By donluca

Expert (75)

donluca's picture

15-05-2020, 16:40

Grauw wrote:

I don’t on the built-in keyboard of my Macbook Pro 16" 2019, macOS 10.15.4, keyboard input set to US (international). I built it myself, could be a macOS or Xcode version issue with SDL2. Or a keyboard language setting problem, what if you change it? I also have an 8-year-old Apple bluetooth keyboard laying about somewhere, I could also try that, though I doubt the bluetooth would be the problem…

I tried switching to US keyboard layout and same issue happened, nothing changed.

Again, this didn't happen on the stable 0.15, it's happening only in the newest build.

I get the exact same behavior on my Macbook Air, by the way, on macOS 10.13

EDIT: ah, and a feature request, if there's no such option already: the possibility of doing a "hard reset", meaning a reset + RAM wiped clean.

By Sylvester

Hero (536)

Sylvester's picture

15-05-2020, 18:50

I can confirm the caps blinking bug with the latest build, I also have the same problem on my macbook.

By sdsnatcher73

Prophet (2143)

sdsnatcher73's picture

15-05-2020, 19:54

Sylvester wrote:

I can confirm the caps blinking bug with the latest build, I also have the same problem on my macbook.

I have it as well, for some time now actually.

By Manuel

Ascended (18073)

Manuel's picture

15-05-2020, 20:04

Can you find out when it was introduced?

By Grauw

Ascended (10005)

Grauw's picture

15-05-2020, 22:40

@Sylvester @sdsnatcher73 Which macOS versions are you using?

Page 19/61
12 | 13 | 14 | 15 | 16 | 17 | 18 | | 20 | 21 | 22 | 23 | 24