I've tested this more carefully. The node starts to work correctly after removing it and recreating it again. It means that it calls something in its init function. In particular it calls this.

Lines 79 to 85 in 2d9e313

    
               def update_gl_scale_info(self, origin=None): 
        
                   """ 
        
                   the nodeview scale and dpi differs between users and must be queried to get correct nodeview 
        
                   x,y and dpi scale info. 
        
                   this is instead of calling `get_dpi_factor` on every redraw. 
        
                   """

I'm not sure why get_dpi_factor can't be called on each redraw. From my point of view it's just a constant and reading it can't be too expensive especially comparatively to what already is happening in the draw functions.

So the fix should be to include reading ui_scale on each redraw. Probably also some proves, that it does not have significant impact on execution duration, can be added.

P.S. This behavior is related to how it's implemented in Sverchok and is irrelevant to API changes in Blender (though API changes still can have an effect but it might have different symptones).

	def update_gl_scale_info(self, origin=None):
	"""
	the nodeview scale and dpi differs between users and must be queried to get correct nodeview
	x,y and dpi scale info.

	this is instead of calling `get_dpi_factor` on every redraw.
	"""

UI scale - Blender 3.4 #4709

Description

Problem statement

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions