-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Drag Selection #1603
Drag Selection #1603
Conversation
54be1c7
to
0e4c55a
Compare
c635ac5
to
8f1662e
Compare
8f1662e
to
52865b7
Compare
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.
wooh!
a5a59b3
to
f649e8a
Compare
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.
if we don't move the selection to hud layer now, it's likely still doable later. advantage of simulating it: we easily capture it in recordings. (although tracing the camera pos in presenter has to be done anyway)
has merge conflicts :) |
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.
ok, let's do it like this for now.
f649e8a
to
a51d2c3
Compare
merge conflicts are fixed :) |
Also relevant for the input layer since the selection queue for the controller resides there. This back propagation of the unit state is a bit hard to do across thread boundaries. We can probably manage that via another interface to the presenter though. |
Depends on #1550
Adds drag selection to the possible inputs.
Selectable
ability