Open equilet opened 6 years ago
this is not quite as straightforward of a change as you might think since the queuesize is used to allocate a block of memory. So if we want to let users change this on the fly it will involve some careful coding, locking, resizing and initializing the schedule heap etc...
I'm not sure that having these exposed with the Max UI is worth the danger of changing the inner functioning at this time.
Hopefully people who are interested in osc-schedule will soon be using o.schedule!
Yeah, that’s a message that should probably not be an attribute
On Jan 1, 2018, at 6:25 AM, rama gottfried notifications@github.com wrote:
this is not quite as straightforward of a change as you might think since the queuesize is used to allocate a block of memory. So if we want to let users change this on the fly it will involve some careful coding, locking, resizing and initializing the schedule heap etc...
I'm not sure that having these exposed with the Max UI is worth the danger of changing the inner functioning at this time.
Hopefully people who are interested in osc-schedule will soon be using o.schedule!
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/CNMAT/CNMAT-Externs/issues/75#issuecomment-354655885, or mute the thread https://github.com/notifications/unsubscribe-auth/ABjjdYUqSnpciQdD5PwYeCUi2qgcXXDKks5tGOrXgaJpZM4Qxvf4.
osc-schedule's attributes are not exposed to the Max system to the point of being viewable in the [view that user sees when they right click]. This should be a straightforward fix.