Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » Developing U++ » Mac OS » Problem with menu accelerators
Re: Problem with menu accelerators [message #50365 is a reply to message #50363] Wed, 03 October 2018 20:22 Go to previous messageGo to previous message
mirek is currently offline  mirek
Messages: 13984
Registered: November 2005
Ultimate Member
Novo wrote on Wed, 03 October 2018 19:48
mirek wrote on Wed, 03 October 2018 11:42

That would be hard to integrate ("shouldn't rely" part).

I think we should just deprecate SetDefaultCharset.

I somewhat doubt that deprecating of SetDefaultCharset is easier.
What will you do with functions taking CHARSET_DEFAULT as an argument?
CHARSET_DEFAULT should disappear in such case ...
IMHO, it is easier to fix places which explicitly require UTF8 ...


Well, the place is "Ctrl::GetKeyDesc". I am really not sure how reasonably fix it, except maybe reverting to text names ("Ctrl"...) if charset is not UTF8 (but even that will some people report as bug).

I understand the need for maintaining charsets for old apps - in windows. But I do not think that spending much effort to make U++/cocoa compatible with legacy encodings is worth it...
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: GridCtrl is currently broken
Next Topic: The last roadbloack... workaround for NSMenu issue
Goto Forum:
  


Current Time: Mon Jun 10 08:41:58 CEST 2024

Total time taken to generate the page: 0.01516 seconds