English > Scripts and Templates

Probable bug with text alignment in tabs of skins

<< < (2/3) > >>

goddert:
Strange ...
It doesn't seem to depend on the pvdconf.ini. Now although I start PVD without any pvdconf.ini and I change only the skin as preference, with the skin attached to this post I have the same problem with the wrong text wrapping. Rick could please do me a favour and test the attached skin and tell me whether you see the behaviour shown in the first two screenshots?

Thanks

[attachment deleted by admin]

rick.ca:

--- Quote ---Rick could please do me a favour and test the attached skin and tell me whether you see the behaviour shown in the first two screenshots?
--- End quote ---

It initially shows Description in a narrow column, but will the text intact (i.e., properly wrapped, not truncated). The Comment tab uses the full width available. Description does so only after the skin is reloaded (i.e., refreshing or changing movies does not).

It doesn't happen after all the rows above the tabbed section are deleted. Somehow, it seems to be picking up a column width from the previous section—in this case, that set for IMDb Rating. :-\

goddert:
Thank you.

It behaves sligthly different on my system. The description tab is never correct and always in form of the narrow column. Neither a restart nor refreshing etc. does help.

These were the good news.

On a XPSP3 32bit system the error doesn't occur with the skin above ...  :o

But ... I could reproduce the "narrow column" with another tab skin and one of my other skins (3. screenshot).

It occurs only with expandable sections and with every skin it behaves differently. In the end when I could reproduce the error with one skin it was sufficient to keep the MovieExpanded settings in the [UI] section of pvdconf.ini, delete the configuration file, copy the MovieExpanded settings to make appear the error again. Which means it depends on the combination of already expanded sections during the visualization of the skin. This would explain why deleting the pvdconf.ini initially resolved the problem for me.

But it doesn't explain the different behaviour on different systems and why the bug with my Windows 7 64bit system also without a pvdconf.ini produces the bug (except the initial setting MovieExpanded of virgin pvdconf.ini was provoking the bug there)

Edit: I forgot something. It is not the column width of the previous column it picks. The width doesn't correspond to any other column width in the skin. But ... the width seems to be the same through all the skins which produce the error. Maybe it is some default width it uses.

mgpw4me:
<guessing>

Assuming PVD (er, Delphi) uses the MSXML library for parsing, there are different versions available.  A quick look at your windows/system32 directory should tell you which versions you have loaded (3,4 and 6, being likely for 64 bit and 3,4 for 32 bit...and 6 on XP SP3 or later).  If these DLLs are the same on all systems, I'm out of ideas for the differences.

The narrow left column can't be reproduced on my system...Vista 32 bit (MSXML versions 3,4,6) and PVD 0.9.9.21.  It does make sense to me though...

The control tries to use the minimal amount of space because it's being autosized.  For a title, it would use the minimal width necessary to display the title.  For a multi-line display, it makes sense to look at the height of the page, then make the control's width whatever is necessary to fit the text into the display.  This would account for differences encountered with expandable fields. 

Rick's comment that a refresh resolves the issue also makes sense, if the parser invokes the renderer in real time...the renderer won't know about other tabs or columns that might occur later in the XML code.  Once the page has been parsed once, all the page elements are known, so the renderer can make a better decision.

</guessing>

The obvious fix would be to assign a width to the control or to one of it's parent containers (page control would be my preference).  If that works, it doesn't mean there isn't a problem, just that there's a work-around for it.

[attachment deleted by admin]

goddert:
@mgpw4me

Thanks for your answer. I'm not completely convinced by your guessing, for various reasons.

As far as I know PVD doesn't use the msxml* libraries and I'm not really sure whether it uses implicitly a xml library. It uses the mshtml.dll and therefore xmllite.dll. (btw I have on both systems only version 3 and 6 of the msxml* libraries - these are the ones that are necessary for parsing xml with windows (32 or 64) if you want to link them, 4 often is installed but not used).

But apart from this the control in question is not autosized. The poster control is autosized, the description and also all father objects aren't. (Autosize that is to say the poster fills all space available inside the 35% column/row) If you remove autosize from the poster the misalignment appears nevertheless. Or did you mean autosized by the PVD window? In this case it should occupy all the available horizontal space of the father column (obviously to the side of the poster) because there isn't defined a size for the column. Indeed the comments tab does it correctly (horizontally expanded til the border of the father column).


--- Quote ---For a multi-line display, it makes sense to look at the height of the page, then make the control's width whatever is necessary to fit the text into the display.
--- End quote ---
If this was the case you'd have a column with one word in every line if the text doesn't fit the height. It is not the way renderers work (at least in the occidental world :) Every browser is the proof.

Also putting a fixed width doesn't resolve the problem. In fact in the meanwhile I could reproduce the problem with both systems and various skins (see screenshot). As I said above, once discovered the guilty state of the values of MovieExpanded for a skin I can reproduce it.

I think the only answer can give us nostra when he will find a bit time to investigate the problem.

Thanks

VinT skin:

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version