Cache current variable values in event conduits
Reported by Christopher Stawarz | November 20th, 2013 @ 10:37 AM
Scripts that use the client- and server-side event conduits often want on-demand access to the current value of selected variables. Rather than forcing every script to monitor and store variable values itself, we should provide some machinery to do it automatically. (Probably the easiest approach would be to add a variable-caching subclass of, e.g., IPCClientConduit.)
Comments and changes to this ticket
-
-
-
-
Christopher Stawarz June 20th, 2017 @ 10:04 AM
- Tag cleared.
-
Christopher Stawarz February 5th, 2021 @ 10:29 AM
- Tag set to “”
Assigned to Tender discussion #6102.
-
Christopher Stawarz February 5th, 2021 @ 10:30 AM
- Tag cleared.
-
Christopher Stawarz June 24th, 2021 @ 04:24 PM
- State changed from “open” to “resolved”
- Assigned user set to “Christopher Stawarz”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
The core framework and supporting libraries for the MWorks Suite
Christopher Stawarz