[quote=435141:@jim mckay]That would make sense then that Xojo isn’t anticipating being asked for touchbar items and releases the input context on deactivate (pure speculation of course). Apple assumes that everyone wants to provide items for the touch bar.
Does the IDE use TextInputCanvas? That has an override to return nil for inputContext if the view is not editable.
That would make a lot of sense if Apple isn’t getting the context into a local variable and operating on that, but rather using a function call result for each new call, and assuming it’s never going to be nil.
So essentially once deactivate is called, the next call goes to a nil object and boom… That is, if the IDE uses TextInputCanvas.[/quote]
According to Apples docs, this property is nil when the object doesnt conform to the NSTextInputClient protocol. Returning Nil when the editor is read-only seems like the right thing to do in that case.
That said, this is one of those bugs where we have been searching for reproducible steps. Ive personally seen this on and off since early December, but havent been able to reliably reproduce it yet.