Name menu MBSID 1.7

Testing/Troubleshooting
1

Hi,

I just finished my next MIOS project - a little brother for my “Der Brat” :slight_smile:

Here´s a little preview (more pics to follow):

Everything´s fine, with one exception: The baby has a 2x16 LCD, so DISPLAYED_ITEMS = 4. In the Patch Name menu, the buttons have erratic behaviour. I suppose the problem is that this menu has 5 key options (<,>,Ins,Del,Clr), and there´s a problem with only 4 buttons. Everytime I enter the menu, the buttons are mapped some other way. e.g. I press < and a space is inserted.

Is there any missed config change that can cause this or have I found a bug?

Thanks,

Seppoman

Brat50-6.JPG
Brat50-6.JPG850×605 145 KB

2

Hi Seppoman,

wasn’t there a recycle competition in one of the last c’t s? This would be a nice contribution :slight_smile:

To the buttons in the name menu: could it be that just the “<” key is missing, so that only “>,Ins,Del,Clr” are selectable? Then it would be an easy change (if so, I will do this with the next bugfix release)

Best Regards, Thorsten.

3

hmmm, this problem occoured twice so far on my MBSID 1.7.

but after a reboot everything was fine again :slight_smile:

so long,

julian

4

Hi Thorsten,

wasn’t there a recycle competition in one of the last c’t s? This would be a nice contribution :slight_smile:

Sadly, the awards are already given at the CeBit :wink:

To the buttons in the name menu: could it be that just the “<” key is missing, so that only “>,Ins,Del,Clr” are selectable? Then it would be an easy change (if so, I will do this with the next bugfix release)

No, I just checked it further. The functions depend on where the Nam Item is when selected from the upper menu layer:

  1. Clr,<,<,<

  2. Ins,Clr,<,<

  3. Del,Ins,Clr,<

  4. >,Del,Ins,Clr

so the items are rotated but in the right order. Rebooting doesnt change anything.

Any hints?

Seppoman

5

Hi Seppoman,

alright, this looks really like a bug - I will check this (together with the problem reported by Julian) once I find the time

Best Regards, Thorsten.

6

This bug is fixed in v1.7a

Best Regards, Thorsten.