-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move flexiMenu functions to CfgFunctions #1054
Conversation
Could delete these: https://github.com/CBATeam/CBA_A3/blob/master/addons/ui/script_component.hpp#L83-L86 However, before the functions are named |
Might be right yeah. But then we previously had both I guess I'll just move them to PREP then? |
master: PR: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see comment
Can we also delete these silly |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
allVariables missionNamespace
Before minus new (functions lost by this PR):
["cba_ui_fnc_setobjectmenusource"]
New minus old (functions added by this PR):
["cba_fnc_fleximenu_highlightcaretkey","cba_fnc_fleximenu_keydown","cba_fnc_fleximenu_keyup","cba_fnc_fleximenu_list","cba_fnc_fleximenu_mousebuttondown","cba_fnc_fleximenu_getmenudef","cba_fnc_fleximenu_menu","cba_fnc_fleximenu_getmenuoption","cba_fnc_fleximenu_execute","cba_fnc_fleximenu_menushortcut"]
- Should we add all these new functions?
cba_ui_fnc_setobjectmenusource
has to be kept.
wat? should |
idk, dude, it's the flexi menu dude |
What about not doing the = stuff and instead to make use of CfgFunctions with a different tag? |
We need some of them twice anyway as they were defined in CfgFunctions and as a PREP with different names. |
What I don't want is to introduce new (duplicate) globals with this PR if it can be avoided. |
This triggers me.