After all the threads, i see that a menu lib is difficult to handle (also i think it has a simple concept). I did my best to add tutorial pages to the wiki, but i also see that there is still a lot of discussion required. I am not sure how to improve this. Let me know if something is missing... and do not hestitate to ask directly...

After all the threads, i see that a menu lib is difficult to handle (also i think it has a simple concept). I did my best to add tutorial pages to the wiki, but i also see that there is still a lot of discussion required. I am not sure how to improve this. Let me know if something is missing... and do not hestitate to ask directly...

Oliver

Hi, I've only tried menubackend and menu that came with the IDE I don't like the submenus on menu, menubackend I got a working menu with submenus but most of the functions don't work. What I'm after is a char LCD scrolling top to bottom menu with submenus (like your PWM pin example) But I couldn't use .....getBefore().getName() etc they don't compile so I had no way to work out what to display as the before and after items. I'm hoping your structure does what it says, it's much better documented example wise despite what you said above. There is only one example for menubackend, most of it's feature are not used or exampled.

Many thanks for the offer of assistance, It's great you release the library in the first place! I'll try myself and post if I need to

dannix, I had the same problem, built a huge menu, couldnt get it to work, and now turning to this option. Seems like it has much more functionality just trying to learn how to use its features

Well, working functions is a start! reading this thread I noticed the GLCD support in m2tklib. I don't need it now, but I will sometime later ;-)

I'm glad it wasn't just me. I'm newish to this arduino and I normally program in Perl so not having dynamic memory etc I thought it could be me using menubackend wrong but there is to many posts I've seen with similar issues when it comes to anything beyond a basic list of menu items.

The problem is, that LiquidCrystal_SR is the same type as LiquidCrystal. The warning is correct and it will not work.M2tklib currently only supports output to LiquidCrystal. Howver, other libs could be added also, but M2tklib needs another graphics output handler. The existing LCD output code might serve as a template: http://code.google.com/p/m2tklib/source/browse/dev/LiquidCrystal/m2ghlc.cpp

Quote

Question. I have 3 buttons up, down & select , which you have no handler for, I thought no problem I can use SetKey() in my ISR? this is ok I assume?

It is no problem to have only three buttons. And yes, you probably can use setKey within an ISR (it has not been fully tested by me).

The problem is, that LiquidCrystal_SR is the same type as LiquidCrystal. The warning is correct and it will not work.M2tklib currently only supports output to LiquidCrystal. Howver, other libs could be added also, but M2tklib needs another graphics output handler. The existing LCD output code might serve as a template: http://code.google.com/p/m2tklib/source/browse/dev/LiquidCrystal/m2ghlc.cpp

Quote

Question. I have 3 buttons up, down & select , which you have no handler for, I thought no problem I can use SetKey() in my ISR? this is ok I assume?

It is no problem to have only three buttons. And yes, you probably can use setKey within an ISR (it has not been fully tested by me).

Oliver

I tired renaming LiquidCrystal to LiquidCrystal_SR http://code.google.com/p/m2tklib/source/browse/dev/LiquidCrystal/m2ghlc.cpp renaming it as m2ghlc_sr but it hit another strange error "error: __c causes a section type conflict" it was flagged against my Serial.print messages that had flash strings in them like

I had a look at MENWIZ which also supports LiquidCrystal, but all variations of ie shift register, I2C etc maybe there is some confusion over the names LiquidCrystal vs this "new" LiquidCrystal that I'm using?