+1 As OP mentioned this feature is much nicer with multiple list boxes you'd
like to keep in sync
> On Feb 9, 2017, at 10:29 AM, Cannon Smith
> wrote:
>
> I love this feature. [snip]
>
>
>> On Feb 9, 2017, at 11:09 AM, Chip Scheide
Tim
That sounds like a bug that 4D have introduced-have you reported it to them?
There used to be a nasty killer if you put a trace in a form resize event
-probably from a similar way of handling the call to how they are now handling
the on column resize-it should only really actually be an on
Thank you all for your suggestions, the flag came to mind, too. That's a
feasible way to go.
Our current solution was to not act until form unload which is in our use case
OK as we just store the status of the listbox.
Still I'm not really happy about this change because one way or another you
Yeh what we used to do was to set a boolean to false and then when code runs
set to true. Only run code if boolean is false. We had the same type of
problems in really old versions of ALP
Regards
Chuck
Couldn't you write the code so that it runs only if a flag is not set, then set
the flag upon starting the operation and clear it when done, then the
subsequent calls would see that the flag is already set so they don’t do
anything...?
-Tim
on timer?
set a timer event (10 ticks?) when the On Column resize occurs
WHen the timer 'times out' apply the actions you want as you can
conceder the resize event to be complete.
Alternatively - an event handler turned on when resize fires first time
to track mouse down, and then on mouse up
6 matches
Mail list logo