Re: Important change in MaskBox control

[Claus Dietrich <claus.dietrich@xxxxxxxxxx>]

Am 16.04.26 um 22:22 schrieb Benoît Minisini:
> Le 16/04/2026 à 15:39, Benoît Minisini a écrit :
> > Le 16/04/2026 à 15:17, Florian Brunke a écrit :
> > > Hi,
> > > okay I will clarify this by something you can all test:
> > > 1- Use the following mask definition in a MaskBox: "!00:00"
> > > 2- now enter "12:34" into the MaskBox; you will see, every position 
> > > will be OVERWRITTEN
> > > 3- next, put the cursor to the most leftposition again and try 
> > > typing in new digits; you will see nothing happens, because the 
> > > positions are not overwritten again.
> > > 4- now delete the whole MaskBox and insert: "11:05"
> > > 5- put the cursor just right of the ":" separator
> > > 6- type "12"; you see that theyou can insert the "1" by OVERWRITING 
> > > but not the "2" (confronted by anything but "0", overwriting is 
> > > blocked)
> > > 7- the same happens, resp. again nothing happens, if you put the 
> > > cursor in the most left position
> > > 8- finally something special to demonstrate: delete the MaskBox 
> > > contents again and insert "10:20"
> > > 9- now you will see that you can insert and OVERWRITE the segments 
> > > before and after the ":" separator. So, apparently, if the right 
> > > position of the segment is a "0", overwriting works.
> > > In this kind of mask I think digits should generally be overwritten 
> > > in any position.
> > > Best regards,
> > > Florian
> >
> > My bad, it was just a bug that prevented any insertion in a full slot 
> > between two separators. It does make sense only in insertion mode.
> >
> > It's fixed in master.
>
> Don't forget to tell me when everything is ok for both of you.
>
> I don't these changes will be backported to the stable version, 
> because they are too intrusive.
>
> Regards,
Hi Benoît, Hi Florian

I posted a message to the ML today (~17:20) as response to above 
description of Florian. The message didn't show up in the ML - no idea 
why. It is not the first time that this happened. As I never receive a 
bounce back from my email provider in these cases I have no idea what is 
causing this.

In my response I rated Florians observation as a bug, which you 
confirmed and fixed already. So there was no need for resending my message.

I couldn't test your latest MaskBox fix yet because it didn't arrive in 
the OBS-master yet, but I am sure that it will be OK.

So lets hope that this message arrives ...

Best regards

Claus