Hi - as per the title, I am seeing that whilst Cycles (ie. the Raytraced Viewport is selected) is rendering, the RhinoCommon Rhino.RhinoApp.Idle event is not firing until I pause the cycles render. Is this the intended functionality? It is quite an issue for plugins which rely on the idle event.
I think this may be due to the fact that the refresh mechanism provided by the realtime display integration mechanism posts events to handle the redraws. In this case it isn’t limited to Raytraced only, but to any render engine integrating though the mechanism. @andy, am I right in my assumption?
Back on the original subject - having the Rhino viewport suppress the Idle event is a total killer for a plugin that replies on the Idle event to process changes. Is this able to be fixed please?
The Rhino Idle event is called whenever the WM_KICKIDLE message is fired in Windows. The trouble is that when Cycles is running, it’s constantly drawing - so it never goes idle.
@andy perhaps the Cycles integration could fire off a WM_KICKIDLE event every second or so. Plugins the rely on the Rhino idle event are pretty much unusable whilst Cycles is rendering at the moment.
@dale this is something for the RDK to fix. Any integration will suffer from the same issue, not just Cycles. To make sure it doesn’t get lost I logged RH-58654