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 #50370 is a reply to message #50368] Thu, 04 October 2018 12:44 Go to previous message
mirek is currently offline  mirek
Messages: 14267
Registered: November 2005
Ultimate Member
mr_ped wrote on Thu, 04 October 2018 10:41
I think legacy SW should move to UTF8 finally, if-possible (development-time-budget wise)...

If it is not maintained any more, you can use old binaries for some time.

I'm not even sure how much dev effort it can take to migrate legacy code to UTF8, sounds to me like it should require just few text resources files conversion, setting UTF8 encoding for app environment, and finding string related code operating with byte = single letter assumption (if the legacy app was text editor, this may be problematic, otherwise you may have none such place in source = no work).

Sounds to me like for many apps this migration is 1-4h task + testing/bugfixing. Maybe 1-2 days in relaxed way.


...as long as it is just your code. Consider application connected to other subsystems, like SQL or perhaps some printing or OCR input or legacy 3rd party lib that you have no source code for (or maybe just not enough energy to fix and recompile) and things immediately become much more complicated.
 
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: Fri Aug 22 03:13:36 CEST 2025

Total time taken to generate the page: 0.00684 seconds