Suspect bug in 5.2.1 in MultiLine Portals

I can’t confirm it yet, but I took my production server to 5.2.1 on friday and I’ve had two bugs reported since then that are both in MultiLine Portals. Neither portal has been under development for months and months, so the bug reports make me suspicious. Both had to do with objects either sitting on top of other objects, or anchoring to sit on top of other objects, rendering the object underneath unuseable. One was a checkbox that wouldn’t check/uncheck until I went into form designer and moved an object that appeared to be on top of it. These checkboxes very definitely worked for months and months (years?) and I am the only developer. The other had a right anchor that didn’t make sense that was stretching it to be on top of the date field next to it that was absolutely in daily use for years, but was rendered unuseable by the object next to it overlapping suddenly.

If anyone else is seeing anything similar, say so. I see that multiLine portals were under development in 5.2.1…

ellen

So I’m not sure if this is a bug… but it’s really there and really has to do with the change made in 5.2.1 noted as

[fix] 306954 tabsequence in multi-line portals is default right to left

My simplest explanation is that objects foreground/background status is getting overridden by their proximity to the left of the portal. I have one of these portals where three objects sit on top of each other, 1 of which is intended to be behind the other 2. When I upgraded to 5.2.1 it now really likes being the first foreground object no matter what I tell it to do, unless I make sure its first pixel is to the right of the other 2 objects. Then it is willing to be behind them.

Hope that makes sense.

Please add a case in our support system with a sample.

This bug will be fixed in next release (Servoy 5.2.3). The form index information wasn’t taken into acount for a multiline portal. As far as I see this never worked well.