Different Homing buttons and values in different browsers
-
I think you may have a problem with some of the browsers using a cached older version of the .js file.
-
Is it not a font size issue? DWC reduces informations if there is not enough space. And a larger font reduces space…
-
Just zoom in and out (ctrl-wheel or ctrl+, ctrl-) and you will see the layout change. Bootstrap (which I think is the framework being used) alters the layout depending on the window width and the scaling.
-
Ian I think the point he is making here is that in Safari it shows a Home All button (Normal for a delta but not Cartesian/CoreXY) but in Firefox and Chrome he gets the individual Axis Homeing buttons I guess this is an Issue with Safari and the very reason I use Chrome on My Mac Also the Z Hight is different in Safari for some reason.
Doug
Hi Doug,
Bit confused. I see home all button then the individual axes all stacked vertically in one layout but then the same buttons stacked left to right in the other layout - unless my old eyes are deceiving me
-
Ian I think the point he is making here is that in Safari it shows a Home All button (Normal for a delta but not Cartesian/CoreXY) but in Firefox and Chrome he gets the individual Axis Homeing buttons I guess this is an Issue with Safari and the very reason I use Chrome on My Mac Also the Z Hight is different in Safari for some reason.
Doug
Hi Doug,
Bit confused. I see home all button then the individual axes all stacked vertically in one layout but then the same buttons stacked left to right in the other layout - unless my old eyes are deceiving me
My Bad I hadn't spotted the vertical stacking very weird and that is how my Chrome looks as well will have to try Firefox I think and see what that does I do know Google has messed with quite a bit of stuff lately
-
You also have more moving boxes (+100/-100). I don't see any problems: it depends on the available space. Different browsers uses different font sizes, so manage space in different ways. DWC adjusts itself. As it adds a line, it regroups buttons on the same line.
-
Ian I think the point he is making here is that in Safari it shows a Home All button (Normal for a delta but not Cartesian/CoreXY) but in Firefox and Chrome he gets the individual Axis Homeing buttons I guess this is an Issue with Safari and the very reason I use Chrome on My Mac Also the Z Hight is different in Safari for some reason.
Doug
Hi Doug,
Bit confused. I see home all button then the individual axes all stacked vertically in one layout but then the same buttons stacked left to right in the other layout - unless my old eyes are deceiving me
I was wondering what they were talking about also. Same stuff, different layout.
-
Ian I think the point he is making here is that in Safari it shows a Home All button (Normal for a delta but not Cartesian/CoreXY) but in Firefox and Chrome he gets the individual Axis Homeing buttons I guess this is an Issue with Safari and the very reason I use Chrome on My Mac Also the Z Hight is different in Safari for some reason.
Doug
Hi Doug,
Bit confused. I see home all button then the individual axes all stacked vertically in one layout but then the same buttons stacked left to right in the other layout - unless my old eyes are deceiving me
My Bad I hadn't spotted the vertical stacking very weird and that is how my Chrome looks as well will have to try Firefox I think and see what that does I do know Google has messed with quite a bit of stuff lately
No worries mate. For info, I use Firefox and see the same layouts depending on how I resize the window.
-
Yeah I see that now if I narrow down my Chrome screen then they move at a certain width to be horizontal rather than vertical stacked
-
Sorry, I guess I buried the lead in that message:
The X, Y, and Z homing values are different. They actually command the amount of travel shown.
I now see that changing the window width shows the additonal buttons for each axis, but Firefox actually has different values for the Z axis than the other two browsers:
Chrome and Safari show:
Z-50 Z-5 Z-0.5 Z-0.05
While Firefox shows:
Z-100 Z-10 Z-1 Z-0.1
for those 4 or 8 movement buttons.
-
Settings -> Machine Control -> Half Z Movements
The state of this is probably stored in the browser, not the Duet.
-
Settings -> Machine Control -> Half Z Movements
The state of this is probably stored in the browser, not the Duet.
That was it! Thanks.
In this day and age when it is common (for me anyway) to interact with two to three web browsers on multiple devices (laptop, tablet, phone), even across the duration of a single print, I wonder if this information could be saved and loaded from the Duet itself. It feels like DWC was not designed with the multiple simultaneous browser environment in mind.
John
-
Settings -> Machine Control -> Half Z Movements
The state of this is probably stored in the browser, not the Duet.
That was it! Thanks.
In this day and age when it is common (for me anyway) to interact with two to three web browsers on multiple devices (laptop, tablet, phone), even across the duration of a single print, I wonder if this information could be saved and loaded from the Duet itself. It feels like DWC was not designed with the multiple simultaneous browser environment in mind.
John
Correct, it is only designed for 1 consecutive connection at a time. It’s so fast that it’s normally irrelevant, but it does raise questions like these.
If everything were set on Duet you wouldn’t be able to do custom things or client basis, so guess it’s a trade off as always ? -
Settings -> Machine Control -> Half Z Movements
The state of this is probably stored in the browser, not the Duet.
That was it! Thanks.
In this day and age when it is common (for me anyway) to interact with two to three web browsers on multiple devices (laptop, tablet, phone), even across the duration of a single print, I wonder if this information could be saved and loaded from the Duet itself. It feels like DWC was not designed with the multiple simultaneous browser environment in mind.
John
Correct, it is only designed for 1 consecutive connection at a time. It’s so fast that it’s normally irrelevant, but it does raise questions like these.
If everything were set on Duet you wouldn’t be able to do custom things or client basis, so guess it’s a trade off as always ?It would be possible by adding a username to the initial login.
Then the settings could be saved on a per user basis.
