Hi,
I am using the .isl file as embedded resource and loading it on startup. It works fine for all other themes but office2013 theme looks like the attached screenshot. Also it happens on both 15.1 and 15.2 versions.
Can someone assist with this issue.
Thanks,
Nivid Dholakia
Hi Nivid,
Thank you for posting in our forums.
Please provide me with more details about your issue. What controls are you using? How many forms are you creating in your MDI container? How are you loading them? Are you using an UltraTabbedMDIManager? What are the steps to reproduce the issue?
Also it would be extremely helpful if you are able to provide me with a small isolated sample that reproduces the issue. This will ensure that I will be able to determine what exactly is causing the issue and how to reproduce it.
Thank you for your collaboration.
I am looking forward to hearing from you.
All I changed is the using style. If I am using Office 2010/2007 styles generated from AppStylist, It does not have any issues.
I have generated Office2013.isl from AppStylist. I did not change any stlyle of the controls. AppStylist>File>Create New> Start form Theme> Office 2013 Light Gray and saved it.
protected override void OnLoad(EventArgs e) { Stream s = Assembly.GetExecutingAssembly().GetManifestResourceStream(GetType(), "Office2013.isl"); if (s != null) { StyleManager.Load(s); } else { Debug.WriteLine("Unable to locate the " + appStylistFileName + " app style file."); } base.OnLoad(e); }
Problem is when there are more then 2 child windows open and one is closed. The Form that was previously opened looses its styles and it will be like a normal MDI child window. If we drag that window inside the MDI container it starts painting the window all around. Sorry I am caught up with other things so I could not make a sample application. I Hope this will help you guys.
Adding on this post the form should be maximized and then closed using code not by close button.
Thank you for the reply.
Unfortunately, I am unable to reproduce this issue. I tried following the provided steps and everything works fine for me. Without any additional details it is difficult to say what exactly is causing this issue. What other controls do you have in the application? Is the issue reproducible without them – i.e. using a forms without any controls, just an MDI parent and an empty parent form, does the issue happen again? Again a sample that demonstrates this issue will be preferable, since with it I will be able to find what exactly is causing this issue.