Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] LCD Positioning error in Z menu, for menu_motion.cpp #16566

Closed
andylh opened this issue Jan 14, 2020 · 7 comments
Closed

[BUG] LCD Positioning error in Z menu, for menu_motion.cpp #16566

andylh opened this issue Jan 14, 2020 · 7 comments

Comments

@andylh
Copy link

andylh commented Jan 14, 2020

The position of the menu item for the Z menu when doing an 0.025mm correction is incorrect being too far to the left. The change lines up the menu item with those above.

Needs the following change in line 252 of "menu_motion.cpp" (Change the start position from 0 to 1)

MENU_ITEM_ADDON_START(1);

@boelle boelle changed the title LCD Positioning error in Z menu, for menu_motion.cpp [FR] LCD Positioning error in Z menu, for menu_motion.cpp Jan 14, 2020
@boelle boelle added the T: Feature Request Features requested by users. label Jan 14, 2020
@boelle
Copy link
Contributor

boelle commented Jan 14, 2020

changed the title since you want something specific changed

@borland1
Copy link
Contributor

borland1 commented Jan 16, 2020

I don't see that offset on my 12864 graphic display. But I see a problem that is inconsistent with other menus. Namely, the solid lines above and below the heading "Move Z".
Menu looks like this, but with solid lines above and below the 'Move Z' header, plus above and below menu selection..

Move Z
Move Axis -^
Move 10mm ->
Move 1mm ->
Move 0.1mm ->
Move 0.025mm ->

Big problem is when 'Move 10mm' is selected, as there are then four solid lines on the screen, making it difficult to tell what menu item is currently selected.

Suggest removing the header "Move Z" and re-label each menu selection like this:

Move Axes -^
Move Z 10mm ->
Move Z 1mm ->
Move Z 0.1mm ->
Move Z 0.025mm ->

That could apply to other Axis menus as well.

@ellensp
Copy link
Contributor

ellensp commented Feb 2, 2020

This does seem to be a bug.

On a 20x4 char display:
The menu "Move Z|Move 0.025m" is one character left of where it should be, interfering with the ">" cursor on that line.
If you apply the patch "MENU_ITEM_ADDON_START(1);" then this does correct the display.

BUT

On a 12864 GLCD display:
All the menus are left justified as there is no need for a ">" cursor, its uses boxes.
The menu "Move Z|Move 0.025m" is in the correct location on this display.
If you apply the patch "MENU_ITEM_ADDON_START(1);" then this menu is one character to the right of where it should display.

What does this mean?

There does look to a bug, but its is not as simple as changing the start position.

@boelle boelle removed the T: Feature Request Features requested by users. label Feb 2, 2020
@boelle boelle changed the title [FR] LCD Positioning error in Z menu, for menu_motion.cpp [BUG] LCD Positioning error in Z menu, for menu_motion.cpp Feb 2, 2020
@ellensp
Copy link
Contributor

ellensp commented Feb 3, 2020

After much digging in circles I have found the issue (but not solved it, yet)
https://github.com/MarlinFirmware/Marlin/blob/bugfix-2.0.x/Marlin/src/lcd/menu/menu_motion.cpp#L250
This routine adds a blank menu item, then comes back and updates the lcd line with the custom text using lcd_put_u8str(tmp). The issue is that displaying the menu is LCD dependent. This is handled differently if your on a 20x4 or a 12864. But lcd_put_u8str is common across screens.

@ellensp
Copy link
Contributor

ellensp commented Feb 3, 2020

Looked at several ways to fix this, went for the simplest.
Which is to set MENU_ITEM_ADDON_START(1); only on character displays.

@ellensp
Copy link
Contributor

ellensp commented Feb 4, 2020

This fix is now part of marlin bugfix 2.0.x.

@github-actions
Copy link

github-actions bot commented Jul 3, 2020

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked and limited conversation to collaborators Jul 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants