Omnis refusing to change $top of a field
Hi Bas,
Since it’s only the 1st time when the behavior occurs it makes me wonder if there’s something special about the entry field’s $event handling that may somehow interfere with the normal processing?
Brian O’Sullivan
brian.os@verizon.net
—–Original Message—–
From: Bastiaan Olij <bastiaan@basenlily.me>
To: omnisdev-en <omnisdev-en@lists.omnis-dev.com>
Sent: Tue, Jun 6, 2017 7:31 am
Subject: Re: Omnis refusing to change $top of a field
Hey Phil,
Yeah close enough as an explanation 🙂
No I’m pretty sure the values are correct. The code that fails is this:
Calculate $cinst.$bobjs.1234.$top as lvTop+2
Calculate $cinst.$objs.ivEntry.$top as lvTop+5
The background object moves exactly where it needs to go.
The entry field fails but not always.
If the values were wrong I would expect it to consistently fail and for
both to fail
It’s really weird, it’s like Omnis does not accept the change…
Cheers,
Bas
On 6/6/17 6:46 pm, Phil (OmnisList) wrote:
> Bas,
>
> So, to be clear, after entering a code, the entry box moves down the
> height of the sub window, lets say 30 points, so you just add 30 each
> time to the $top figure, and then the previous $top figure is used for
> the subwindow $top?
>
> So, on a refresh, you set $top to 0, or 1… and that is what fails?
> Or something else?
>
> Maybe the code that is calculating $top is wrong when the effective
> list is empty?
> Maybe it doesn’t think the list is empty at that point.
> Hard to guess without seeing any code…
>
> regards
> Phil Potter
> Based in Chester in the UK.
_____________________________________________________________
Manage your list subscriptions at lists.omnis-dev.com
_____________________________________________________________
Manage your list subscriptions at lists.omnis-dev.com