You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The display in Octoprint-Webclient (everything below the print-pause-cancel line) twitches every time you change layers because the skipto line is deleted and re-inserted. This is very annoying with small but tall objects.
The text was updated successfully, but these errors were encountered:
Thoughts on ditching this feature in favour of allowing users to use other plugins like "display" or do you think this is important specifo to this plugin?
Other wise, we'll need to improve how this is update/rendered to fix this
The frame of your plugin is briefly deleted when layer changes (the display area below is pushed up). Then your frame is 1 or 2 lines tall. (The display area below is pushed down by 1-2 lines). This causes the displayed area below "your" frame to fidgeting.
Why don't you use a fixed size for the frame?
a) because fixed size is bad in general as it wont flow well on small screens etc... (not a deal breaker)
b) I ask because there are several plugins for "show me layer and z height" and I wonder if "do one thing well" is a better motto for this plugin - so removing this saves us from trying to figure it out...
c) it uses the ocotprint api correctly, so the updates all (we think) come from the framework, so we dont think WE are deleting and recreating it... perhaps its as the layer height grows the flickering happens becuase the 'box' is blown out to two lines...
see 0.1.6 to see if this fixes it (made shorter text)... however bigger machines might still suffer when z and layer count gets higher...
if you know more about the dev side let us know.
The display in Octoprint-Webclient (everything below the print-pause-cancel line) twitches every time you change layers because the skipto line is deleted and re-inserted. This is very annoying with small but tall objects.
The text was updated successfully, but these errors were encountered: