upgrading to 8.1

[acarur01]

..has completely crashed our product :). The positioning for our layouts are completely off the grid (positioning in console is 0,-39999). Where do I begin to debug this? We are not (as far as I know) playing with positioning at all except for putting layout spacers to center child layouts. I also have layouts no longer draw (according to console they are not drawn)

15:50:41.550:WARN:HLayout:page$$menu$HorizontalLayout:ignoring bad or negative false: NaN [enable 'sizing' log for stack trace]
15:50:41.550:WARN:LayoutSpacer:page$$menu$$cwSpacer:ignoring bad or negative false: NaN [enable 'sizing' log for stack trace]
15:50:41.556:WARN:ImgSectionHeader:isc_ImgSectionHeader_1:ignoring bad or negative false: NaN [enable 'sizing' log for stack trace]
15:50:41.556:WARN:VLayout:page$content$$content$topSectionfinderHeader:ignoring bad or negative false: NaN [enable 'sizing' log for stack trace]
15:50:41.566:WARN:HLayout:page$content$$contentMenu$finderMenuLayout:ignoring bad or negative false: NaN [enable 'sizing' log for stack trace]
15:50:41.566:WARN:LayoutSpacer:page$$contentMenu$$cwSpacer:ignoring bad or negative false: NaN [enable 'sizing' log for stack trace]
15:50:41.569:WARN:HLayout:page$$bannerLayout:ignoring bad or negative false: NaN [enable 'sizing' log for stack trace]
15:50:41.569:WARN:HLayout:page$$mLayout:ignoring bad or negative false: NaN [enable 'sizing' log for stack trace]
15:50:41.570:WARN:VLayout:page$$context:ignoring bad or negative false: NaN [enable 'sizing' log for stack trace]
15:50:41.570:WARN:VLayout:page$$content:ignoring bad or negative false: NaN [enable 'sizing' log for stack trace]
15:50:41.570:WARN:VLayout:page$$contentMenu:ignoring bad or negative false: NaN [enable 'sizing' log for stack trace]
15:50:41.570:WARN:DynamicForm:page$$statusMessage$gridWrap:ignoring bad or negative false: NaN [enable 'sizing' log for stack trace]
15:50:41.571:WARN:HLayout:page$$bannerLayout:ignoring bad or negative false: NaN [enable 'sizing' log for stack trace]
15:50:41.571:WARN:HLayout:page$$mLayout:ignoring bad or negative false: NaN [enable 'sizing' log for stack trace]
15:50:41.571:WARN:VLayout:page$$context:ignoring bad or negative false: NaN [enable 'sizing' log for stack trace]
15:50:41.571:WARN:VLayout:page$$contentMenu:ignoring bad or negative false: NaN [enable 'sizing' log for stack trace]
15:50:41.573:WARN:VLayout:page$$menu:ignoring bad or negative false: NaN [enable 'sizing' log for stack trace]
15:50:41.573:WARN:HLayout:page$$menu$HorizontalLayout:ignoring bad or negative false: NaN [enable 'sizing' log for stack trace]
15:50:41.573:WARN:LayoutSpacer:page$$menu$$cwSpacer:ignoring bad or negative false: NaN [enable 'sizing' log for stack trace]
15:50:41.573:WARN:HLayout:page$$menu$HorizontalLayout:ignoring bad or negative false: NaN [enable 'sizing' log for stack trace]
15:50:41.574:WARN:HLayout:page$$menu$HorizontalLayoutForMenuItems:ignoring bad or negative false: NaN [enable 'sizing' log for stack trace]

[Isomorphic]

Not much we can do with this except to point out the NaN - this suggests that you be doing math on the left/top/width/height values you pass to SmartClient, and you are passing NaN, fractions, negative width/height or similar bad values.

[acarur01]

I also noticed that the Drawn Size column has some funky values like NaNwx871h or 100%1671w x 87h

[Isomorphic]

That last value is particularly telltale. "100%1671" is the kind of thing you'd see if your code added widths without checking that one was a percent.

If you think this might be something the framework is doing, please try narrowing it down to a test case, or at least something more specific - we can't do anything with what you've provided so far.

[acarur01]

I wish there was some sort of list on what behaviour has changed between version so it would be easier to figure out what we need to modify. I was literally just running this exact application 15-20 minutes ago with build from 06-17 and it worked fine.

[Isomorphic]

There's a giant changelog.html file in the release. But it does not have anything about coordinate handling changes or anything like that because there is no intentional change in this area. Once again, isolation is the first step.

And please remember - your code could well be flawed, but just in a way that hasn't been revealed until this release, because some behavior in the framework just happened to compensate for a bug in your code. So please don't automatically assume this is a bug - it may well be, but that's not a reasonable conclusion yet.

[acarur01]

Don't get me wrong. I am not assuming it is a bug AT ALL. We have a lot of workarounds in our product to get it the way we want using SmartClient. I'm trying to get a standalone testcase working as we speak.

[acarur01]

I don't know what has been changed between 8.1 release and and the 08-16 build but the screens that were broken when I first tested are now fixed.

[Isomorphic]

? we didn't fix anything even tangentially related to sizing. Probably some really obscure staleness issue in your IDE or deployment process. Well, it's a happy result regardless.