- This topic has 9 replies, 3 voices, and was last updated 12 years, 11 months ago by
.
-
Posts
-
Child Dynamic form does not skin some components on creation. If I change the skin at runtime the child form components skin correctly.
I have posted a you tube video demonstrating the odd behavior. I cannot replicate this failure in another project. I believe it has something to do with the dfm file. How can I get programatically tell the new form to accomplish what I do by changing the skin manually from the mainform menu?
Windows Vista and most current release of AC and I did reload internal skins.
Have you placed a SkinProvider-component on the dynamically created form?
I guess nobody can help if it's not reproducable.
Last time I had such a case I copied the project and deleted and deleted and deleted until I found the circumstances that were needed (as a minimum) to show the problem.
Then the guys from AC were really quick in helping me.
Ralf
Ralf, thanks for taking the time to reply. Yes I have a skin provider on that form.
I understand that we would like to find the root cause but since a simple manual act of choosing another skin corrects the problem it would seem to me that on startup I should be able to initiate a method or procedure that would function the same as choosing another skin at run time.
Finding the error on a form this complex would be too time consuming. I believe that the problem was caused by one of the components not getting its parent property set correctly when added to the form. I may have to switch to another skinning product.
Ralf, thanks for taking the time to reply. Yes I have a skin provider on that form.
I understand that we would like to find the root cause but since a simple manual act of choosing another skin corrects the problem it would seem to me that on startup I should be able to initiate a method or procedure that would function the same as choosing another skin at run time.
Finding the error on a form this complex would be too time consuming. I believe that the problem was caused by one of the components not getting its parent property set correctly when added to the form. I may have to switch to another skinning product.
'Ralph' wrote:Finding the error on a form this complex would be too time consuming. I believe that the problem was caused by one of the components not getting its parent property set correctly when added to the form. I may have to switch to another skinning product.
I tried quite a lot of different skinning solutions before I found AC. I didn't find another one that was as good as this one.
Do you create the controls on that form at runtime?
And, regarding time-comsuming: My product is a humongous thing. Still thinning the app out to a skeleton that still shows the problem is just a matter of minutes. And then you suddenly delete something or change something and the sknning works again. That's were you can start to dig. Again, as I said, normally a matter of minutes, maybe one hour.
In your case you don't even need to let the “switch skin”-code survive. If you open a form the controls have to be skinned. If this is not the case this is enough to demonstrate the problem.
Just my 2cents.
Ralf
- You must be logged in to reply to this topic.