Timeline for C/C++ Flexible yet fast way of linking UI elements to functions
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 16, 2017 at 10:54 | comment | added | Ian Young | It's not just about ease of use. It's also about re-usability and flexibility. Also, the performance cost of clicking a button in a UI is negligible. Calling a wrapped function pointer via a virtual function will still happen faster than you can click the button, unless the button click triggers something cpu intensive, in which case, that is what should be optimised, not the button. | |
| Aug 16, 2017 at 10:44 | comment | added | simulate | I think it's a good idea to treat the behaviour as something separate from a button, this way I can relink behaviours to different buttons. Though i still really dislike the idea of virtual functions and derived classes. I am not sure why but I think it's because it takes away from the transparency of things and i feel like it is a trade off of performance for easy usuage | |
| Aug 16, 2017 at 10:09 | history | answered | Ian Young | CC BY-SA 3.0 |