From: BillT on
I have just discovered when running a program generated from VO2.8,
that a button click is not activated unless the button is fully
showing in the window.

The same (well, the original from which the new program evolved)
program generated by 2.5 behaves differently. If the button is only
partially visible then the screen scrolls until the button is fully
exposed and then calls the button's method.

Is this a bug or a deliberate change or....?

Thanks,
Bill
From: Karl Faller on
Bill,
just tried with 2 of my apps, even if the button is just clickable at
all, it behaves like you described for 2.5. So i'd suspect some other
problem in your app...

Karl

>I have just discovered when running a program generated from VO2.8,
>that a button click is not activated unless the button is fully
>showing in the window.
>
>The same (well, the original from which the new program evolved)
>program generated by 2.5 behaves differently. If the button is only
>partially visible then the screen scrolls until the button is fully
>exposed and then calls the button's method.
>
>Is this a bug or a deliberate change or....?
>
>Thanks,
>Bill
From: Geoff Schaller on
Bill.

I'm with Karl here. I just squished a window until I got a scrollbar and
half a button hidden. It clicks.

Geoff



"BillT" <wtillick(a)hotmail.com> wrote in message
news:303dfda7-f1e1-4417-b123-d89a063add6a(a)y32g2000prc.googlegroups.com:

> I have just discovered when running a program generated from VO2.8,
> that a button click is not activated unless the button is fully
> showing in the window.
>
> The same (well, the original from which the new program evolved)
> program generated by 2.5 behaves differently. If the button is only
> partially visible then the screen scrolls until the button is fully
> exposed and then calls the button's method.
>
> Is this a bug or a deliberate change or....?
>
> Thanks,
> Bill

From: BillT on
Karl, ,Geoff,
Thanks - so it's not 2.8 per se.

I do have a bBrowser on the window, but I don't think that's the
problem. I looked at that possibility first as the only significant
difference between my main window and this one is the presence of bB
on this one.

Just tried with a test window + bBrowser in this program and that
worked as 2.5 does (i.e. the window jumps sideways until the button
shows fully and then the button action occurs.)

Just tried a few things with my troublesome window, and the results
are:-
1. Button fully exposed when window is shown = OK when clicked
2. Button fully exposed by dragging horizontal scroll bar to fully
expose the button = OK when clicked
3. My button is on the right, and it seems that if there is room to
move the window left sideways without hiding any controls on the left
then it will jump sideways to the edge of the leftmost control.. If
this causes the button to then be exposed, then OK when clicked.
If the button is still not fully exposed then the only solution seems
to be to drag the horizontal scroll bar sufficient to expose the
button. Then OK.

Not something I recall ever striking previously. This window has quite
a wide bB on it which means there is only a couple of mm space on left
edge. The program 'remembers' it's last size and position so once
sorted on a particular PC the wide window should position itself OK.

Thanks and regards,
Bill
From: BillT on
Correction to point 3 above - the window will jump left as far as it
needs to expose the button EXCEPT that it will not push the bBrowser
off the screen. Other controls on the left may be pushed off the
screen.

Cheers,
Bill