Thanks, committed rBe413b39a936181cc954dfbf054b0a19794d8902c

Existing logic works now, rBa7cf7b114f82625aa5d81e91e26e67cbe7a842bc, however this is preferred, will commit w/ PyEval_GetBuiltins call instead of access from modules.

Confirmed, checking...

I know this is not the right place to ask questions, but now that I have the attention of knowledgeable people on the rather obscure and new matter of custom gizmos: How do I make a 2D gizmo pan and scale with the area? It seems like in the node editor as well as the sequencer preview the gizmo is always drawn relative to the area frame and not to the content of the area.
I made a stackexchange question as well, but I have a feeling it will go unanswered: https://blender.stackexchange.com/questions/155528/python-how-to-pan-and-scale-gizmogroup-with-background

Well, I guess this should work for the other region_types as well...

Thank you so much! Using gizmos in the preview region is probably a more common use, but I didn't know about it. So I think you can also treat this as a matter of incomplete documentation.

This actually works for the preview area if you set

• bl_space_type = 'SEQUENCE_EDITOR'
• bl_region_type = 'PREVIEW'

The crashes are now fixed. The rest is to be addressed in the .blend file itself.

Add missing semicolons.

Short story: neither of update or tagging should happen from set() functions.

ID.update_tag(...) doesn't refresh on the viewport while scrolling in the timeline. Going to edit mode refreshes the mesh in the viewport.

Fairly sure calling view_layer.update() within a set function isn't supported.

A different diff ended up being committed.

Fixed rB8096190d11d6caf5facfc266791a08985179688a

I see, thanks but why doesn't this happen when baking for example smoke in the same way?

https://developer.blender.org/D5952

The cache is empty when I open the file afterwards

Right, all properties should use the character index not the byte offset.

In D5881#136734, @Campbell Barton (campbellbarton) wrote:

This patch has the issue that indices can be between unicode characters.
See comments for D1613: Add set selection function to text api

This patch has the issue that indices can be between unicode characters.

Can confirm.
This was always crashing, not really designed for usage outside of the FileBrowser itself...

This patch deals with set selection: D5881

so now it would be possible to get back selection to what it was before the last undo using this