Interface button interactions??

Discontinued Software Weather Watcher - Skins
1

On two similar skins the meeting of the left side and right side buttons reacts differently. In one the right hand button overlays the left hand button, on the other the opposite is the case.

What governs which button is on top when they overlap?

Case 1 - right button (Options) overlays left button (Maps)[code][Skin]
BackColor=255,255,255

FontSize=6
FontBold=False
FontColor=0,0,0

ButtonExitX=-27
ButtonExitY=5
ButtonCurrentX=15
ButtonCurrentY=-20
ButtonHourlyX=70
ButtonHourlyY=-20
ButtonDailyX=118
ButtonDailyY=-20
ButtonDetailedX=158
ButtonDetailedY=-20
ButtonMapsX=229
ButtonMapsY=-20
ButtonOptionsX=-62
ButtonOptionsY=-20
ButtonRetrieveX=-80
ButtonRetrieveY=5
ButtonAlertsX=-128
ButtonAlertsY=5

TitleX=15
TitleY=6
TitleText=Weather Watcher
TitleFont=Verdana
TitleFontBold=true
TitleFontItalic=False
TitleFontSize=8
TitleColor=181,208,217

ResizeHeight=10
ResizeWidth=12

DragHeight=14
DragWidth=7

StatusBackColor=255,255,255

StatusFont=Verdana
StatusFontBold=False
StatusFontItalic=False
StatusFontSize=8
StatusFontColor=0,0,0

StatusX=20
StatusY=1
StatusBarX=20
StatusBarY=1

StatusHeight=20
StatusWidth=303

StatusBarHeight=14
StatusBarWidth=264

StatusBarEmptyColor=255,0,255
StatusBarFullColor=42,94,162

[Info]
Author=Hunz - updated by Ed P.
SkinDesc=Mini Tronnix
[/code]

Case 2 - left button (Maps) overlays right button (Update)[code][Skin]
BackColor=255,255,255

FontSize=6
FontBold=False
FontColor=0,0,0
ButtonExitX=-27
ButtonExitY=5
ButtonCurrentX=15
ButtonCurrentY=-20
ButtonHourlyX=70
ButtonHourlyY=-20
ButtonDailyX=118
ButtonDailyY=-20
ButtonDetailedX=158
ButtonDetailedY=-20
ButtonMapsX=229
ButtonMapsY=-20
ButtonOptionsX=-80
ButtonOptionsY=5
ButtonRetrieveX=-59
ButtonRetrieveY=-20
ButtonAlertsX=-128
ButtonAlertsY=5

TitleX=15
TitleY=6
TitleText=Weather Watcher
TitleFont=Verdana
TitleFontBold=true
TitleFontItalic=False
TitleFontSize=8
TitleColor=181,208,217

ResizeHeight=10
ResizeWidth=12

DragHeight=14
DragWidth=7

StatusBackColor=255,255,255

StatusFont=Verdana
StatusFontBold=False
StatusFontItalic=False
StatusFontSize=8
StatusFontColor=0,0,0

StatusX=20
StatusY=1
StatusBarX=20
StatusBarY=1

StatusHeight=20
StatusWidth=303

StatusBarHeight=14
StatusBarWidth=264

StatusBarEmptyColor=255,0,255
StatusBarFullColor=42,94,162

[Info]
Author=Hunz - updated by Ed P.
SkinDesc=Mini Tronnix II
[/code]
I’ve tried various arrangements of the button parm’s sequence to no avail. So what’s the key?

2

EdP, why would you want the buttons to overlap in the first place?

3

Hey Mike.

Smaller forecast window for smaller screens using the same skin.

Not a problem with the desktop and it’s 19" monitor but very useful with the nb’s smaller screen. Multiple versions of a skin work but is more work to maintain, one skin for both is a better option.

So what’s the key to consistent button overlap behavior?

4

EdP, there is no consistency because the buttons were not designed to be used like you’re trying to use them. How would you expect them to overlap?

5

Consistently!! And logically!! :evil:

If I have the option to choose a senario I would like the buttons positioned relative to the right border to overlay buttons positioned relative to the left border. Like my Mini Tronnix interface does.

6

Calm down there, tiger. I promise not to ask you any more serious questions :neutral:

7

:sign5:

8

I just realized something, while I’m concerned about the visual appearance of button overlaps there is also the underlying code to support the button’s function. And it is that that is probably the cause of my visual problems.

That revelation doesn’t solve my problem but does help me to think of how to address it differently. Maps is the button that is causing me the problems so it’s probably coded after the Retrieve button’s code and before the Options buttom code since its on top when the Options button is squeezed in but below when the Update/Retrieve button is squeezed in. Yes? Am I close? :icon_smile:

9

Please e-mail me your skin so I can try it out.