#25 language pack crashes#65
Conversation
|
Thanks - tested, working. However, if we could request a minor change; after discussing with Rich, we think that assertions would probably be more appropriate than message boxes after all (i.e, just |
|
The reason why I chose a warning is interference with other REAPER extensions. If these add menus too, an assertion would prohibit compatibility, while a warning on every startup could at least be acceptable. But in this case both of course is not optimal. Edit: Since assertions only show up in Debug build, compatibility with other extensions is still ensured. Hence, I changed the warnings to assertions. |
…to menu positions. Extent menu.cpp by function to get a menu by position.
…s if the previous fails.
…rrectness and show warning if they don't match.
…ck position check warnings by this lambda function.
8a6f4e2 to
acad80d
Compare
…load menu.h/.cpp functions to handle utf-16 formatted strings.
…ching for menus and convert utf-16 to utf-8 in that case.
|
replaced by #91 |
As suggested by @firthm01 to fix #25, the extension first trys to insert the menus by searching for the corresponding labels. If this fails it will fall back to the hard-coded fallback positions.
After sucessfully inserting the menus by using the labels, the fallback positions are checked for correctness. However, this could also fail if other extensions are manipulating the reaper menus. So instead of causing an exception, a warning will be displayed if this check fails.