Benoît Minisini ha scritto:
>> Benoît Minisini a écrit :
>>
Fabien Bodard a écrit :
> it seem that the click event is send after the .value setting... but
> the MouseUp before.
>
> why did you not use the click event ?
>
I don't use it bec
Benoît Minisini a écrit :
>> Benoît Minisini a écrit :
>> ...
>>
>>> If you really have to make a difference between a change coming from the
>>> application and a change coming from the user, then use a boolean flag,
>>> like "bIgnoreClickEvent", that you set explicitely when needed.
>> May be tha
> Benoît Minisini a écrit :
> ...
>
> > If you really have to make a difference between a change coming from the
> > application and a change coming from the user, then use a boolean flag,
> > like "bIgnoreClickEvent", that you set explicitely when needed.
>
> May be that's a solution.
> Now I know
Fabien Bodard a écrit :
> Public Sub CheckBox1_MouseUp()
>
> If not Last.Value and ItIsNotGood then Stop Event
I didn't knew it was possible to stop an event
> End
>
> You need to take in mind that the value is changed after the mouseup event ...
Yeah, but as there no explanation nor map abo
Benoît Minisini a écrit :
...
>
> If you really have to make a difference between a change coming from the
> application and a change coming from the user, then use a boolean flag, like
> "bIgnoreClickEvent", that you set explicitely when needed.
May be that's a solution.
Now I know which order
> Benoît Minisini a écrit :
> >> Fabien Bodard a écrit :
> >>> it seem that the click event is send after the .value setting... but
> >>> the MouseUp before.
> >>>
> >>> why did you not use the click event ?
> >>
> >> I don't use it because it is raised after the .Value has changed and I
> >> need
Benoît Minisini a écrit :
>> Fabien Bodard a écrit :
>>> it seem that the click event is send after the .value setting... but
>>> the MouseUp before.
>>>
>>> why did you not use the click event ?
>> I don't use it because it is raised after the .Value has changed and I
>> need to be able to forbid
> Fabien Bodard a écrit :
> > it seem that the click event is send after the .value setting... but
> > the MouseUp before.
> >
> > why did you not use the click event ?
>
> I don't use it because it is raised after the .Value has changed and I
> need to be able to forbid any change in some conditio
Public Sub CheckBox1_MouseUp()
If not Last.Value and ItIsNotGood then Stop Event
End
You need to take in mind that the value is changed after the mouseup event ...
2009/8/23 Jean-Yves F. Barbier <12u...@gmail.com>:
> Fabien Bodard a écrit :
>> it seem that the click event is send after the
Fabien Bodard a écrit :
> it seem that the click event is send after the .value setting... but
> the MouseUp before.
>
> why did you not use the click event ?
I don't use it because it is raised after the .Value has changed and I
need to be able to forbid any change in some conditions.
--
---
it seem that the click event is send after the .value setting... but
the MouseUp before.
why did you not use the click event ?
2009/8/23 Jean-Yves F. Barbier <12u...@gmail.com>:
> Jean-Yves F. Barbier a écrit :
>> Hi list,
>>
>> In my application I use CheckBoxes to display&set|unset individual
Jean-Yves F. Barbier a écrit :
> Hi list,
>
> In my application I use CheckBoxes to display&set|unset individual rights from
> a database.
>
> When I check|uncheck one, the corresponding xxx_MouseUp() is directly issuing
> an SQL
> request to GRANT|REVOKE the corresponding right.
> However, for
Jean-Yves F. Barbier a écrit :
> Hi list,
>
> In my application I use CheckBoxes to display&set|unset individual rights from
> a database.
>
> When I check|uncheck one, the corresponding xxx_MouseUp() is directly issuing
> an SQL
> request to GRANT|REVOKE the corresponding right.
> However, for
Hi list,
In my application I use CheckBoxes to display&set|unset individual rights from
a database.
When I check|uncheck one, the corresponding xxx_MouseUp() is directly issuing
an SQL
request to GRANT|REVOKE the corresponding right.
However, for some CheckBoxes I must *reverse* the check as it
14 matches
Mail list logo