Please help testing upcoming openMSX release!

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

By Grauw

Ascended (10005)

Grauw's picture

15-05-2020, 22:56

sdsnatcher73 wrote:
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.

Ok, I tried the openMSX build from openmsx.dev, and there I can also reproduce the issue.

I recommend upgrading XCode on the build machines. I’m building with XCode 11.4.1 without issues.

By donluca

Expert (75)

donluca's picture

15-05-2020, 23:52

...and for those who don't have XCode but just the command line tools? Tongue

I'll try to compile the latest build myself when I have time and report back.

EDIT 3: deleted all previous edits as those might be misleading.
I have an issue with 12 years old libraries which were 32-bit only which I brought over from the Snow Leopard days and never updated. Those are part of macOS itself, I need to sort this out. Ouch.

By Manuel

Ascended (18074)

Manuel's picture

16-05-2020, 00:55

What's the problem exactly?

By donluca

Expert (75)

donluca's picture

16-05-2020, 01:36

It looks like I have 32-bit only libraries of zlib (libz.dylib) and tcl (whatever.dylib) in my current macOS which are probably due to having the same OS updated and imaged over to new machines in the last... ugh, 15 years?

It might be a leftover from a very old MacPorts, Homebrew doesn't want to touch those libraries as it thinks that they are system libraries.

I've found hints that downloading and re-installing XCode might fix this and it's exactly what I'll be doing tomorrow as it's 1.30am here now. Hopefully that fixes it.

One of those days I'll also have to go through all the homebrew crap I've installed and do a major cleanup.

By Manuel

Ascended (18074)

Manuel's picture

16-05-2020, 01:50

Manuel wrote:

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.

I just implemented pasting in the console with just CTRL-V. Enjoy Smile

By Manuel

Ascended (18074)

Manuel's picture

16-05-2020, 01:52

donluca: how are you compiling openMSX? Did you try the staticbindist method? Then openMSX will download and compile (locally) the required libraries by itself.

By Grauw

Ascended (10005)

Grauw's picture

16-05-2020, 01:58

Manuel wrote:
Manuel wrote:

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.

I just implemented pasting in the console with just CTRL-V. Enjoy Smile

So many times I’ve tried in vain, and now I’ll finally be able to! Awesome!

Although, one little nitpick, on MacOS I would expect the key combination to be CMD-V.

By Manuel

Ascended (18074)

Manuel's picture

16-05-2020, 02:09

ren wrote:

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).

But what is the point if in many cases you don't even get that whole dialog?

Quote:

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

Well, it's the same as what openMSX supports on the command line, plus what a Tcl script extends. E.g. .txt was done there and maps to a type command, see _osd_menu.tcl

Quote:

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?

If we keep flexible scaling in mind, this becomes quite complex. What font size to use at which scale? How to calculate the available space for each size? It's tricky to find out how large a text will display for a given font size.

Quote:

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

With SDL1 that was not possible. But perhaps now it is, but it's quite some work, as that whole concept doesn't exist in the current code.

Quote:

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?

It is possible, it depends on which background image you set. See the consolebackground setting. I only use 4x windowed myself.

Quote:

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..)

We use that for the reverse bar, but indeed, it interferes a bit with the MSX mouse.
How would you use tool tips for the info panel?

Quote:

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 ...)

The list will quickly become very long. Note that there is a variable number of slots and disk drives in a system.

By Manuel

Ascended (18074)

Manuel's picture

16-05-2020, 02:11

Grauw wrote:

Although, one little nitpick, on MacOS I would expect the key combination to be CMD-V.

I know, but bad luck there... the openMSX code is made to manage CTRL-codes. There are quite some implemented in the console. It's not able to handle META stuff atm (check CommandConsole.cc if you want to know the details).

By Grauw

Ascended (10005)

Grauw's picture

16-05-2020, 03:03

I added:

    case Keys::KM_META:
        switch (key) {
#ifdef __APPLE__
        case Keys::K_V:
            paste();
            return true;
#endif
        }

Paste code extracted to a method to avoid duplication, #ifndef __APPLE__ around the CTRL-V case, and it works. CMD+L, CMD-T, CMD-P, etc. also still work as usual while the console is up. That comment there seems to be about using it as a modifier key for typing characters. I can submit the change tomorrow.

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