Arch Linux User Repository

This package is already outdated upstream and they don't have plans to continue the development (the next release of openmsx will not need this frontend anyways).

I will orphan this package, so feel free to adopt if you want to continue supporting it or maybe, with luck, update it upstream.

This package is already outdated upstream and they don't have plans to continue the development (the next release of openmsx will not need this frontend anyways).

I will orphan this package, so feel free to adopt if you want to continue supporting it or maybe, with luck, update it upstream.

if someone is having trouble with the new icu package conflict (74 against 73), just make these symbolic links:

sudo ln -s /usr/lib/libicudata.so.74 /usr/lib/libicudata.so.73
sudo ln -s /usr/lib/libicui18n.so.74 /usr/lib/libicui18n.so.73
sudo ln -s /usr/lib/libicuuc.so.74 /usr/lib/libicuuc.so.73

Done.

Hi,

I suggest changing the version requirement condition to greater-than-or-equal. ("openmsx=${pkgver}" to "openmsx>=${pkgver}")

The version differences are (almost certainly) not so great that catapult would cease functioning with a more recent version. But more importantly, having an exactly equal condition results requiring the user to force the upgrade or remove openmsx-catapult temporarily at every upgrade, which is certainly not optimal.

Committed and tested, thanks @pjag.

Minor thing I discovered while submitting upstream - I deleted two flags I shouldn't have and it made the rendering dropdown offcenter, here is the more correct patch: https://pastebin.com/LkVWQszZ

@pjag thanks for the patch. I've added the patch to the package for now. It's a good idea to talk with upstream, they're very friendly about useful modifications.

I think I was right (not sure why the environmental variable workaround didn't work though), this patch removes invalid flags and warnings are gone after I apply it:

https://pastebin.com/CUiS2KYC

I think it also fixes some jank when you resize the main window (although it's hard for me to say which behaviour was intended).

I will submit this upstream but there is still something weird with scaling options (4x doesn't work, and in fullscreen the window doesn't center), but I'm not sure this is a Catapult issue.

My bet would be incompatible changes with wxWidgets 3.2, there's a relatively sizable list here: https://raw.githubusercontent.com/wxWidgets/wxWidgets/v3.2.0/docs/changes.txt

My guess would be for this: "Using invalid flags with wxBoxSizer or wxGridSizer items now triggers asserts when done from the code or error messages when done in XRC" and they even advise to set WXSUPPRESS_SIZER_FLAGS_CHECK to suppress the warnings but it didn't work for me, so maybe that's not it.

There's still some hiccups when you run the application (some dialogs shows a XRC error about wxALIGN_CENTER_VERTICAL), but I don't know how to fix that.