Bug-fix updates for Odyssey?

@Maijestro

It is standard - for MUI programs, that is.

BTW, in the MUI settings, you can choose to have a drop-down (or pop-up) gadget in the top of the window containing among other things the snapshot function, that makes it easily accessible. I have made that setting in the global MUI prefs (in the Windows pane), so it is present for all MUI programs I run.

Best regards,

Niels

It's been a good weekend, not only did I learn how to change that, but I found similar settings and fixed the same problem for multi view and notepad too :D (in their case staring me in the face in the menu bar mind you!)

Things I should have solved long ago, but there was always something else to fiddle with instead. On top of that, got e-UAE and glUAE working nicely so it's been pretty productive.

Anyway, apologies for going O/T...

In early August, 'deadwood' Śmiechowicz released a first test build of the 64-bit Odyssey browser for AROS... but the really interesting thing is that In this test build the WebKit engine was updated from August 2015 to February 2019.... apparently back then it wasn't that impossible to update the core without having to rewrite the entire browser from scratch...

Update of the engine caused a number of regressions in the browser UI, but I don't see anything that can't be fixed or is a show stopper.

Odyssey is currently rebased to webkitgtk 2.24.4 which is close enough to Wayfarer branch 1.x (webkitgtk 2.30) to allow porting functionality (BE patches?) from that branch.

If anyone is interested in trying to compile this version, please get in touch with me.