- User Since
- Jan 25 2019, 2:31 AM (46 w, 1 d)
Fri, Nov 22
There appear to be only a couple built-in add-ons using save_pre (blenderkit and measureit), and they both seem to be using it to clean data. I haven't looked very closely at blenderkit, but measureit appears to be manipulating scene data in the handler. However, I'm not very familiar with it, so I'm not sure how critical it would be skip over the code during the recovery file save. If it is only cleaning unused data, I'm assuming it would not be very noticeable - just accumulated garbage memory/scene-data.
I'm personally using the callback to move global property data from the add-on preferences group to scene data, so such data will be saved inside the *.blend file.
I'm very new to Python and Blender development, so I'm probably not the best person to throw one together. But it should be simple to do so for someone who knows what they're doing. It would be even easier to modify a copy of an existing add-on, which would only involve moving some preferences properties from the primary preferences structure to a child property group derived class. If needed, I can try to throw something together, or make a slight modification to one of the built-in add-ons.
Fri, Nov 15
Nov 12 2019
Aug 22 2019
You have to check the "extend" checkbox to make deselect useful (which may be a bug in itself)
Jan 26 2019
Jan 25 2019
I can confirm this bug. I'm having the same problem. I seem to notice it has something to do with the mouse position. It almost acts as if the UV editor work space is losing the mouse focus, as if the code thinks the mouse is hovering a tool window or such. As far as I can tell, it effects panning and zooming. I'm using an MX Master 2S Logitech mouse.