The current implementation recommends that users specify a "dummy" lambda function that returns the desired static content. Although this works, it results in unnecessary processing on the rendering side of things since it causes the window to redraw the same static content over and over. If you want to get granular about this, there is also an extremely small unnoticeable cost each time the callback is executed and returns the same python equivalent of a data pointer to the render call.
Anyways, users should be able to pass an extra argument to the display panes that permanently renders them as static after the first draw sequence is completed.
The current implementation recommends that users specify a "dummy" lambda function that returns the desired static content. Although this works, it results in unnecessary processing on the rendering side of things since it causes the window to redraw the same static content over and over. If you want to get granular about this, there is also an extremely small unnoticeable cost each time the callback is executed and returns the same python equivalent of a data pointer to the render call.
Anyways, users should be able to pass an extra argument to the display panes that permanently renders them as static after the first draw sequence is completed.