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
Reproduction - change the "grid major spacing" to a lower value, attempt to delete the old value and replace with a new one. Because its applied instantly you will trash laserweb with a config that runs out of memory when loading the grid.
It's a combination of 2 bugs. I want to reduce the grid size from 50mm to 10mm. When changing this value laserweb instantly applies it.
Second part of the bug is that it does not display properly in the UI so the user can't easily see the value when making changes.
The 'grid minor spacing' requires a restart but the 'grid major spacing' goes on instantly. Chrome crashes with a out of memory issue from there on out and laserweb is fully unresponsive, the only fix is to remove the laserweb profile.
Screen resolution is 3200x1800
The text was updated successfully, but these errors were encountered:
Thanks for the hint!
Nobody reported that until now, so I guess not many people are trying to change these values (or they use the up/down buttons for it).
Windows 10 using laserweb 4.0.998-136 64bit.
Reproduction - change the "grid major spacing" to a lower value, attempt to delete the old value and replace with a new one. Because its applied instantly you will trash laserweb with a config that runs out of memory when loading the grid.
It's a combination of 2 bugs. I want to reduce the grid size from 50mm to 10mm. When changing this value laserweb instantly applies it.
Second part of the bug is that it does not display properly in the UI so the user can't easily see the value when making changes.
The 'grid minor spacing' requires a restart but the 'grid major spacing' goes on instantly. Chrome crashes with a out of memory issue from there on out and laserweb is fully unresponsive, the only fix is to remove the laserweb profile.
Screen resolution is 3200x1800
The text was updated successfully, but these errors were encountered: