I greatly appreciate codemirror and the work that has gone into it. I know I’m being a little dense on this, but after studying the reference manual, I am still having problems understanding the whole process used for things such as resizing the editor.
I’ve written a soft-wrapper similar to Updates not synchronised with requestMeasure and ViewPlugin - #3 by bxff. It defines an update method that receives a ViewUpdate and checks geometryChanged. If geometryChanged=true, it does a requestMeasure, the write of which…does what? (to resize the editor)? Mine directly modifes viewState.contentDOMHeight and viewState.editorHeight. I can see my requestMeasure being called as the editor is first rendered.
What I can’t seem to do is resize from a user event (changing the size of the parent by dragging the border, in my case). I thought I could make this happen by direct calls to requestMeasure write which modifies the ViewState as above. These would use data about the parent passed in the user-initiated event. Is it enough to change the properties referred to above? Must I use a transaction to make those changes? I’m under the impression that changes to EditorState go through transactions, but not changes to ViewState.