Tim (or anyone who's seen this)

I have quite a complex project that uses Autosizing all over the place for labels and other assorted stuff. Sometimes, I notice that these labels have not autosized correctly (they retain a default design size) but it seems that reloading the app (not recompiling) can often fix the problem. It seems random TBH despite spending a lot of time trying to analyse the issue. My uneducated case is that it's some form of timing issue during startup when properties are being set?

Any ideas?

Mark

Mark,

<< I have quite a complex project that uses Autosizing all over the place for labels and other assorted stuff. Sometimes, I notice that these labels have not autosized correctly (they retain a default design size) but it seems that reloading the app (not recompiling) can often fix the problem. It seems random TBH despite spending a lot of time trying to analyse the issue. My uneducated case is that it's some form of timing issue during startup when properties are being set? >>

It can't really be a timing issue because JavaScript is single-threaded.  It could be a sequence of operations issue, but I couldn't say for sure without seeing your application.  My first guess is no, however.  The EWB layout primitives are pretty well battle-tested and are used in every aspect of EWB down to the scrollbars and design-time, and I haven't seen any issues with them since their initial release in the spring.  It doesn't mean that there couldn't be a bug, of course. But, it's a pretty obscure one, if it is.

Send me over something via email and I'll take a look.  Even a URL for a test system is fine, just make sure that you've turned off the compression during compilation.

Tim Young
Elevate Software
www.elevatesoft.com

Thanks Tim - will do in next few min - Mark

Mark,

<< Thanks Tim - will do in next few min >>

Got your stuff, will look at it today or tomorrow.

Tim Young
Elevate Software
www.elevatesoft.com