<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; "><div>Hello,</div><div><br></div><div>Hopefully this can be answered quickly by someone in the know…</div><div><br></div><div>I am tracking down a restore state bug in my reader, and I have nailed it down to the following situation:</div><div><br></div><div>When restoring state, ParaView is using my setArrayStatus() function before I have finished initializing my array list within RequestInformation().</div><div><br></div><div>This causes the on/off status of the arrays in the state being restored to be ignored, as I clobber them when I initialize the list.</div><div><br></div><div>My question is this: where should I be populating my list of available arrays if not in RequestInformation()? The way I have it set up now works fine for when I load data from scratch, but when restoring from a state, as I said, ParaView is trying to set the on/off state of the arrays before I am done populating the available arrays…</div><div><br></div><div><br></div><div>I hope someone can give me a quick answer… again the question boils down to this: where, and at what point, should I be populating my available array list so that it will be initialized already when ParaView attempts to change the status during a state restore?</div><div><br></div><div>Thanks,</div><div>Josh</div><div> </div></body></html>