DUI Parser Error
Parse error on opening particular window.
Sunday, June 17, 2007 by rookieinfotech | Discussion: SkinStudio
Hello,
On opening the control panel window after applying the WindowBlinds skin made by me,this error message comes:
DUI Parser Message
parse error '<' at line 1.
How to solve this problem? Someone please help me.
On opening the control panel window after applying the WindowBlinds skin made by me,this error message comes:
DUI Parser Message
parse error '<' at line 1.
How to solve this problem? Someone please help me.
rookieinfotech
Reply #2 Thursday, August 30, 2007 6:44 AM
Reply #2 Thursday, August 30, 2007 6:44 AM
I compared the whole UI files with that of another WB skin.I couldn't find any error.
The DUI Parser error comes when I apply my WB skin when no other WB skin is active.
Recently I found that if I apply the skin made by me when another WB skin is active,I don't get the DUI Parser error.Everything works fine.But after a reboot,if my skin is active,on opening Control Panel,the error comes. So what can be the problem??
The DUI Parser error comes when I apply my WB skin when no other WB skin is active.
Recently I found that if I apply the skin made by me when another WB skin is active,I don't get the DUI Parser error.Everything works fine.But after a reboot,if my skin is active,on opening Control Panel,the error comes. So what can be the problem??
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!
Reply #1 Sunday, June 17, 2007 3:40 PM
The problem is a codeing error in either shellstyle1.uifile or shellstyle2.uifile used for the Windowblind you have loaded.
Open either file in Notepad and track down and correct any error
(good luck, it can be anywhere....)