Thank you, tbp1 for responding. Unfortunately, if I understand you, you totally misunderstood me. If you understood me, I totally misunderstood you. Perhaps we each misunderstood the other.
I've resolved my problem which was not what I thought it was. Two things were happening: 1) Bit rot in my code caused by no longer allowing cmder.setChanged() to have one argument. Consequently, some of my code that had been working for years was no longer able to set the selected position as observed by the operator after my code executed. This was because I was calling cmdr.setPosition() right after calling cmdr.setChanged(). Since now cmdr.setChanged() was causing an exception (which was never shown to the operator, so I didn't know there was an error), the cmdr.setPosition() was no longer called. 2) In another case, I was intentionally raising an exception after calling cmdr.setPosition(). While it is surprising to me that raising an exception in some sense "undoes" the cmdr.setPosition(), I have no objections to this. Thanks. So far as I'm concerned this thread is finished. SegundoBob -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/1a3aa6bd-9d55-455a-8016-8fc4365d81cfn%40googlegroups.com.
