You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having the corners, show_sel_box and the new vws_previews and vws_contours in the global state seems hacky, I think I need to come up with some way to have tool-level state, which is set at the time of tool switch.
So maybe each .rs file in events can define a thread-local state variable, containing a different type, and TOOL_DATA can become a reference to the current tool's data, or something.
Maybe tool data state variables should be a HashMap. Gotta think more about this.
The text was updated successfully, but these errors were encountered:
Or maybe it's not a problem to call thread_local! in each events/pan.rs, events/pen.rs etc., and each tool just knows which global variable is its own because it defined it. So pull that job out of state.rs and into the different events/ files. Thoughts?
Having the corners, show_sel_box and the new vws_previews and vws_contours in the global state seems hacky, I think I need to come up with some way to have tool-level state, which is set at the time of tool switch.
So maybe each
.rs
file inevents
can define a thread-local state variable, containing a different type, andTOOL_DATA
can become a reference to the current tool's data, or something.Maybe tool data state variables should be a
HashMap
. Gotta think more about this.The text was updated successfully, but these errors were encountered: