Just got word from MS that this was a docmented bug that was resolved in =
the current (most recent? ) build -- though curiously the bug site =
didn't list it and I didn't know it's status until I reported it....
[quoted text, click to view] "Tim Brooks" <usna91@msn.com> wrote in message =
news:ev8sxO1uFHA.3628@TK2MSFTNGP10.phx.gbl...
Ok....one last word on this. Got it to work but makes no sense. =
Tried changing everything single property, building, running.....
Try this if you're interested....
a.. Create a new LinkLabel anywhere....=20
b.. Change the textalign property to topcenter. Event doesn't fire =
- on my build anyway...
c.. Change back to topleft and recompile - fires; OnClick base =
method must be hittesting or something in the wrong area. Or else =
drawing outside the control area -- which stays on the left.
I can live with this but what a pain....I wish I could have the time =
it took to figure this out back....
Several hours over this stupid bug!!!!!
tb
Alex Yakhnin [MVP] wrote:=20
I've just tested the LinkLabel in the simple test app and it fires Click =
event all the time.=20
--
Alex Yakhnin, .NET CF MVP
www.intelliprog.com |
www.opennetcf.org [quoted text, click to view] "Tim Brooks" wrote:
Peter Foot [MVP] wrote:
LinkLabel contains both the Click (inherited from Control) and =
LinkClicked=20
event, make sure you are handling the LinkClicked event.
Peter
=20
Peter,
Thanks. I hate to disagree to someone with such clear knowledge of the=20
topic (i've seen your posts all over the web).....But the LinkLabel=20
control in my build of CF2.0 (VS2005 Beta 2) doesn't expose a=20
LinkClicked event. It only exposes the following events:
- Clicked
- EnabledChanged
- ParentChanged
- TextChanged
- CollectionChanging
- CollectionChanged
As for protected methods to potentially override, it only exposes those=20
of the parent UserControl -- most of which, like the click event -- seem =
to be inert. This control seems to be about as useful as teats on bull, =
as the expression goes. I'll just write my own.=20
I understand the design constraints, but man, CF seems to require me to=20
write half my own controls -- but just think of all that I'm =
learning.....
Experimented with override some of the parent on_methods.....hmmmm
- GotFocus -- works but not a good solution as it throws repeatedly=20
without user intervention
- Actually....weird.....just created a test harness for linklabel=20
control and threw in all the obvious overrides....it's throwing Click=20
and MouseDown (using overrides)....but EXTREMELY random. I have to=20
click all around the link and sometimes it fires...sometimes doesn't. =20
Also, seems to work better clicking on the outer edge of the link test=20
rather than directly in the middle of it. Whoever wrote the hit testing =
on this one must have been high on RedBull or something....I think my=20
users will think i'm playing a joke on them if I use this....
Oh well, Bill giveth and he taketh away....
Pace
tim