#52 Rework input for drag points

Open
opened 3 years ago by habeebweeb · 0 comments

The current system is absolutely terrible. Every single instance of a drag point is polling it's own input and reacting.

I think a single GameObject should handle input and send messages to EVERYTHING. I'm not smart enough to do something like this though. I'm also not smart enough to know if this is even a good idea to begin with 😖

An alternative I could do is have a couple of GameObjects associated with groups of drag points. Like one for every single prop, one for every single light etc. so that one object is polling input and then notifying all common objects of changes.


This is unrelated to issue #53 where this deals with moving input polling to one object and #53 deals with how inputs are detected. This issue most likely relies on the completion of #53 though.

The current system is absolutely terrible. Every single instance of a drag point is polling it's own input and reacting. I think a single `GameObject` should handle input and send messages to EVERYTHING. I'm not smart enough to do something like this though. I'm also not smart enough to know if this is even a good idea to begin with 😖 An alternative I could do is have a couple of `GameObject`s associated with groups of drag points. Like one for every single prop, one for every single light etc. so that one object is polling input and then notifying all common objects of changes. --- This is unrelated to issue #53 where this deals with moving input polling to one object and #53 deals with how inputs are detected. This issue most likely relies on the completion of #53 though.
Sign in to join this conversation.
No Milestone
No assignee
1 Participants
Loading...
Cancel
Save
There is no content yet.