-
Notifications
You must be signed in to change notification settings - Fork 235
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
Firestate Hotkey Instant Response #6586
base: develop
Are you sure you want to change the base?
Firestate Hotkey Instant Response #6586
Conversation
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.
- Fixes the minor aggravation of the delay in the display on the order button when changing firestate via hotkey.
It's nice to see the fire state not delay, but it doesn't reflect what the Sim does, so I'm not sure it's the best, since you can no longer exactly tell what the game is trying to do. Maybe there could be like a progress bar showing the changing process? I think the worst part is actually that the popup menu closes when the fire state updates on the UI side, so you open the menu to change the state, do it wrong for whatever reason, open it again to fix it, but it auto closes due to the 0.5 delay. The delay itself is not a significant issue, after some experience it's expected due to how the game handles every single command.
- Prevents unnecessary calls to SetAvailableOrders when new selection is same as the old selection (discovered because
SetFirestate
triggersOnSelection
, for whatever reason).
- This breaks the updating of orders due to enhancements finishing, like TML or teleporter, which are simply using
Unit.AddCommandCap
. - This also breaks the updating of the question mark that appears for mixed fire states after setting all the fire states using the popup. The question mark should disappear after you do that since the fire states are no longer mixed.
|
Yeah I agree now, I think I was being a bit too harsh on my expectations of the UI showing the network delay. It would be nice to show the delay but it's not required, so instant UI changes despite the delay is preferred over delayed UI changes.
I don't think the call itself needs to be refined, I think the function itself should verify if the orders of the selection changed before refreshing the UI elements. Maybe ideally an element doesn't get refreshed unless that element's order state was changed in the selection. |
SetFirestate
triggersOnSelection
, for whatever reason).