-
-
Notifications
You must be signed in to change notification settings - Fork 19.2k
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 with LCD_PROGRESS_BAR & DogLCD defined together #1315
Comments
most recent.... is that the dev branch or stable? |
what branch did you use? |
I have managed to emulate the same errors with RepRap Discount Full Graphic Smart Controller & LCD_PROGRESS_BAR defined in the Development branch. |
Sorry I didn't clarify. It was the Dev Branch. I will try your suggestion MonkeyDave and report back Thanks |
I commented out the Line 301 in Configuration_adv.h as monkeydave suggested and the following error is what occurred. I am using the Dev branch of Marlin with Ramps 1.4 configured for a Prusa I3 with 2 extruders and heated bed. I also have a ReprapDiscountFullGraphics display. In file included from ultralcd.cpp:39: |
You've copied u8glib to program files > Arduino > libraries? |
I checked to see if the u8glib library was there and indeed it was. From https://bintray.com/olikraus/u8glib/Arduino I downloaded and copied the library again and now with the commented line as per monkeydave, it compiles properly. I don't know why it didn't the first time. Thanks again for your help. |
This should probably be left open and the title changed, there is a bug with LCD_PROGRESS_BAR & DogLCD defined together. |
RAMPS 1.4 Display stuck on Marlin startup screen with vertical bar in the middle |
@Grogyan which version are you using? Maybe you can try my version vis LogoLCD fixes: http://github.com/stv0g/Marlin/tree/LogoLCD |
@stv0g |
LCD_PROGRESS_BAR support still needs to be added to the DOGM implementation. So, don't enable it for that LCD yet. |
@Grogyan No, its in the LogoLCD branch of my fork, still testing... @thinkyhead Do you want to open a feature request for that? I would implement it in a few days (weeks). |
@stv0g I wrote the implementation for Hitachi, so I should probably finish the job. But I won't be able to get to it until tomorrow. Or, heck, why not now? I've been wanting to play with UECIDE more. |
#1343 is in the queue and ready for testing. |
Oh yeah, I didn't knew that about the Hitachi Implementation. Nice work! Unfortunately we've done some duplicated work with the cleanup of DOGM code, which I've in my queue.. |
Cleanup is always a risk, haha! Hmm, I've gotten pretty good at merging through git, but it sure takes a while. Since it's not a huge file, if I could grab your changes, I will add them onto my pull request. I have a pretty decent diff tool (ok, BBEdit) that speeds the process. I haven't gotten used to this new Collaborator tag yet, but will explore the higher git powers available there soon... Planning to stick to a policy of not pulling my own requests without peer review. (Be kind.) |
should be fixed with PR #1343 |
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. |
Hello,
With the most recent version of Marlin, I now receive the following errors:
ultralcd.cpp: In function 'void lcd_goto_menu(void (*)(), uint32_t, bool)':
ultralcd.cpp:199: error: 'lcd_set_custom_characters' was not declared in this scope
/dogm_lcd_implementation.h: In function 'void lcd_status_screen()':
dogm_lcd_implementation.h:88: error: too many arguments to function 'void lcd_implementation_init()'
ultralcd.cpp:271: error: at this point in file
/dogm_lcd_implementation.h: In function 'void lcd_update()':
dogm_lcd_implementation.h:88: error: too many arguments to function 'void lcd_implementation_init()'
ultralcd.cpp:1192: error: at this point in file
ultralcd.cpp: In function 'void lcd_finishstatus()':
ultralcd.cpp:1296: error: 'progressBarTick' was not declared in this scope
Can anyone tell me what I've done wrong?
Thanks
The text was updated successfully, but these errors were encountered: