Support forum of the software localization tool Sisulizer


Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... Home

Get in contact with the makers of Sisulizer.
Our forum is open for all questions around Sisulizer from customers and prospects.
Don't hesitate to register and ask. The Sisulizer team will answer ASAP.
Search     Help Home Sisulizer Website Download
Search by username
Not logged in - Login | Register 
Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > WPF GridSplitter Error

 Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius
New Topic Reply Printer Friendly
WPF GridSplitter Error - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ...
AuthorPost
 Posted: Fri Sep 5th, 2008 08:17 pm
PM Quote Reply
jlars
Member
 

Joined: Fri Sep 5th, 2008
Location:  
Posts: 18
Status: 
Offline
 When I include a GridSplitter in a WPF window, Sisulizer builds a resource DLL that crashes. Error info:

System.Windows.Markup.XamlParseException occurred  Message="Cannot convert string '' in attribute 'Row' to object of type 'System.Int32'.  is not a valid value for Int32. 


This happens when Sisulizer builds against a compiled exe BUT NOT when Sisulizer builds against the vcproj file.

Is this a bug in Sisulizer?
Back To Top PM Quote Reply

 Posted: Fri Sep 5th, 2008 08:32 pm
PM Quote Reply
Renate.Reinartz
Administrator


Joined: Sat Apr 8th, 2006
Location: Bedburg, Germany
Posts: 43
Status: 
Offline
 Can you please send the EXE causing the problem plus you .SLP with a short description how to produce the problem to support (at) sisulizer.fi.

We will try to reproduce and fix it if needed. In the meantime please use your vcproj.

Renate



____________________
http://www.sisulizer.de - Three simple steps to localize
Back To Top PM Quote Reply

 Posted: Fri Sep 5th, 2008 10:23 pm
PM Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Bedburg, Germany
Posts: 831
Status: 
Offline
 Hi,

your problem was forwarded to R&D for analysis.

Best

Markus



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Quote Reply

 Posted: Sun Sep 7th, 2008 10:17 am
PM Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Tokyo, Japan
Posts: 1641
Status: 
Offline
 I fixed this in 271. The new build will come out in a week.

System.Windows.Controls.GridSplitter was not mapped to a ny control so I mapped it to splitter control.

Jaakko



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Quote Reply

 Posted: Tue Sep 9th, 2008 02:55 pm
PM Quote Reply
jlars
Member
 

Joined: Fri Sep 5th, 2008
Location:  
Posts: 18
Status: 
Offline
 Thanks - I will try 271 when it comes out. -Joe
Back To Top PM Quote Reply

 Posted: Tue Sep 16th, 2008 06:27 pm
PM Quote Reply
jlars
Member
 

Joined: Fri Sep 5th, 2008
Location:  
Posts: 18
Status: 
Offline
 Just got 271 and confirmed the fix. Thanks! -Joe
Back To Top PM Quote Reply

Current time is 03:30 pm  
Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > WPF GridSplitter Error



WowUltra 1.11 Copyright © 2007 by Jim Hale - Based on WowBB Copyright © 2003-2006 Aycan Gulez

Sisulizer software localization tool - Three simple steps to localize