I ran into another glitch in testing the Notes 8.5 client. When opening a couple views in a custom DB, I get the warning "Cannot execute the specified command." The LotusScript debugger wasn't able to help with the diagnosis (no LotusScript firing before the error appears). I then manually tried to follow the sequence of events and found the @Command ViewExpandAll in the PostOpen event of the views. I commented out the formula and that stopped the error.
Google isn't returning any hits to provide insight surrounding the problem. Having the view automatically expand isn't critical and we could live without it, but I'm curious if there's a workaround. Should I be reporting these problems to Lotus?
Thursday, June 11, 2009
Subscribe to:
Post Comments (Atom)
1 comments:
I remember similar issues with a few designs I had .... From what I could figure, the problem lies in the fact that in the new eclipse interface, in certain events you can no longer assume the view has been drawn or has focus in the UI when the time comes to execute any given line of code because the UI on eclipse is drawn by a separate thread (from what I've gathered). Since @Command([ViewExpandAll]) is a UI command dependent on executing in a view with focus, when that code hits in PostOpen, I couldn't guarantee the view was "there" yet ... Seems to me it was also "random" ... some views were fine and would be drawn and focused by the time PostOpen ran, some other not (maybe due to the size or complexity of the views) ... but like i said, this is to the best of my "recollection", so I may also be full of poo...
Post a Comment