Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.clipper.visual-objects > #10483
| From | "Karl-Heinz" <invalid@invalid.invalid> |
|---|---|
| Newsgroups | comp.lang.clipper.visual-objects |
| Subject | Re: ListViewItemChanged fires if items is not changed |
| Date | 2017-04-21 13:46 +0200 |
| Message-ID | <elu9p5F5jhgU1@mid.individual.net> (permalink) |
| References | <2ougfcdbp7qdqerosulp1sp0neavltpgo5@4ax.com> <elrqs1Fldi9U1@mid.individual.net> <kthjfc14ku3e4g0v9il8coifdv79kjv84k@4ax.com> |
Hi Dick,
> Seems like a good trick, thanks. Still strange that this method is
> called almost every time while I'd expect it to be called when
> something is acually changed, as the name suggests.
IMO ListViewItemChanged() works correctly. It´s up to us to ignore any
unwanted state notifications. BTW: Self:IsVisible() helps not if you add,
after the window is visible, e.g. another Item. In such situations it´s IMO
better to check for the keys a user must press to toggle a item checkbox.
METHOD ListViewItemChanged(oEvent) CLASS <YouWindow>
LOCAL pNMLV AS _winNM_LISTVIEW
//LOCAL symListView AS SYMBOL
SUPER:ListViewItemChanged(oEvent)
// IF SELF:isvisible()
IF IsKeyPressed ( VK_LBUTTON ) .OR. IsKeyPressed ( VK_SPACE ) // <---
User action
...
...
ENDIF
RETURN NIL
regards
Karl-Heinz
Back to comp.lang.clipper.visual-objects | Previous | Next — Previous in thread | Find similar | Unroll thread
ListViewItemChanged fires if items is not changed D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2017-04-20 11:21 +0200
Re: ListViewItemChanged fires if items is not changed "Karl-Heinz" <invalid@invalid.invalid> - 2017-04-20 15:17 +0200
Re: ListViewItemChanged fires if items is not changed D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2017-04-21 10:50 +0200
Re: ListViewItemChanged fires if items is not changed "Karl-Heinz" <invalid@invalid.invalid> - 2017-04-21 13:46 +0200
csiph-web