OpenXTalk Forums

I wonder why, having selected and copied an image on one stack, when I go to paste it into another stack the Menu Bar says "paste text"?

Not something I can replicate at the moment.

It only happend intermittently.

I would also like to know why on MacOS Sonoma, the engine is renaming the "Preferences" menuitem in the file menu to "Settings", and the "Quit" menuitem to "Exit".


There's interference from the engine on MacOS that I can't see where it's creeping in from.
I would love the menu code to be completely rewritten from the ground up for MacOS, but there's not much point when it won't compile. (I read on various 'other forums' [or rather, their 'lessons'] page) that Version 9.6.8 of the engine at release was only just made compatible with xCode 13. That makes me think I should be using xCode 11.3 with out 9.7.0-dp1 source - which xCode 11 is ideally suited for MacOS 10.14 (!) - perhaps MacOS 10.15...

I'll probably run MacOS 10.14 in a VM, but keep my mac on Sonoma. I need to keep it on Sonoma to test the menus (to see why they don't work properly and crash standalones). - But, ultimately, I think the entire menu implementation of the engine on MacOS needs ripping out and replacing with alternative code.

Over 'here' on MacOS 15.3 Sequoia 'Preferences' is renamed 'Settings', but 'Quit' stays 'Quit'.

Should that matter at all?

richmond62 wrote: ↑Fri Jan 24, 2025 11:46 am Over 'here' on MacOS 15.3 Sequoia 'Preferences' is renamed 'Settings', but 'Quit' stays 'Quit'.
Should that matter at all?

Until it stops working, but the question is why are things being renamed?

Presumably IF I click on 'Settings' : Ooooh, Yes; it opens the 'Preferences' stack.

I have a funny feeling that there are bigger things to think about than some Preferences/Settings, Quit/Exit cosmetic 'nothings'.

It does, but you can't say to someone "go to 'Preferences' and look in..." because it's no longer called "preferences" because something on the Mac is renaming it.

"go to 'Preferences'

But you can say "go to Preferences or Settings", and that should not fuss anyone.

But - the point is why is it messing with the menus?
If I'd called a menuitem "cheese" and it replaces it with "toast", you'd rightly wonder why. I'm wondering if this kind of interference is partly to do with why the menu code is broken in standalones without an ad-hoc patch.