Ok,
So I worked out what I was doing wrong.
As my custom component was not in fact based on the original Panel
class, but a custom panel (lets call it myPanel, in the name space
'lion'), the custom component being started like this:
?xml version=1.0 encoding=utf-8?
lion:myPanel
I got temporarily burned by something similar to this. I had a public
property in a custom component which really should have been private.
But when I changed it to private, I got a run-time error when the
custom component was constructed. It turned out to be an issue with
the SetProperty
2 matches
Mail list logo
