
Signature
Regards,
Lloyd Dupont
NovaMind Software
Mind Mapping at its best
www.nova-mind.com
Hi,
> I dont see the difference between your syntax and my syntax (except that
> you permutted the order of ElementName and Path, and I tried, just in
> case, but it didn't work)
I just made things explicit, while you left the "Path" implicit. I was
not sure if it could be the problem, apparently not. OK, let's try
something else ;-)
You can debug your bindings like this:
http://geekswithblogs.net/lbugnion/archive/2007/04/02/110622.aspx
(see the chapter "How to find binding errors?")
If that still doesn't help, zip your project and send it to me, I'll
take a look. My email address is genuine.
> Anyway, I know it's one shoot, I don't care for now, I would like it to
> work, at least!
> (And yes the value are initialize before the call to
> InitializeComponent(), so that allright)
HTH,
Laurent

Signature
Laurent Bugnion [MVP ASP.NET]
Software engineering, Blog: http://www.galasoft.ch
PhotoAlbum: http://www.galasoft.ch/pictures
Support children in Calcutta: http://www.calcutta-espoir.ch
Laurent Bugnion, MVP - 15 Jun 2007 14:43 GMT
Hi,
After asking Microsoft, the "problem" is in fact that you're not
supposed to subclass controls this way, and the symptom in that case was
actually a scope problem.
The problem is related to this post by Microsoft's Kevin Moore:
http://work.j832.com/2007/06/don-subclass-panel-unless-you-making.html
If you intend to subclass a control (in your case, it was a Slider),
then you need to subclass it properly in code behind, and create a XAML
template for it (usually by adding it to generic.xaml). In other cases,
use a UserControl.
HTH,
Laurent
> Hi,
>
[quoted text clipped - 21 lines]
> HTH,
> Laurent

Signature
Laurent Bugnion [MVP ASP.NET]
Software engineering, Blog: http://www.galasoft.ch
PhotoAlbum: http://www.galasoft.ch/pictures
Support children in Calcutta: http://www.calcutta-espoir.ch