Yup, I definitely didn't pick that up from your original post! On Monday, February 28, 2022 at 4:14:44 PM UTC-5 SegundoBob wrote:
> 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/6a0b77e4-f6d6-4c9e-9118-cd94a38f78b7n%40googlegroups.com.
