Support forum of the software localization tool Sisulizer


.NET, Delphi, ... - Sisulizer Localization Tool Support 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 

 Moderated by: Sisusupport, Renate.Reinartz, Markus.Kreisel, Ilkka.Salmenius
New Topic Reply Printer Friendly
Error scanning .Net forms with DevExpress LookUpColumnInfo components. - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Wed Nov 8th, 2017 11:56 am
PM Private Upload Quote Reply
jbueno25
Member
 

Joined: Thu Feb 12th, 2009
Location:  
Posts: 40
Status: 
Offline
We are testing Sisulizer 4 in order to upgrade from version 2. Our applications uses DevExpress controls suite (version 10.2.5).

We found an error scanning several forms:

Warning    Could not scan the code of ScanError.XtraForm1 item. Form may show incorrectly on visual editor.

This error appears in forms with a LookUpEdit control in a grid (class RepositoryItemLookUpEdit) when it has columns added to Columns property. I attach a zip file with two VS projects and two Sisulizer projects: ScanOk project has grid and a RepositoryItemLookUpEdit without columns, and it works; ScanError is identical project but the RepositoryItemLookUpEdit has two columns, and it fails. If you compare both designer files, you will find only one difference, the Columns property  serialized:

//
// repositoryItemLookUpEdit1
//
...
this.repositoryItemLookUpEdit1.Columns.AddRange(new DevExpress.XtraEditors.Controls.LookUpColumnInfo[] {
new DevExpress.XtraEditors.Controls.LookUpColumnInfo(resources.GetString("repositoryItemLookUpEdit1.Columns"), resources.GetString("repositoryItemLookUpEdit1.Columns1")),
new DevExpress.XtraEditors.Controls.LookUpColumnInfo(resources.GetString("repositoryItemLookUpEdit1.Columns2"), resources.GetString("repositoryItemLookUpEdit1.Columns3"))});
...

I analysed the dissemsambled file generated by ISDASM.EXE when Sisulizer scans this form. It seems correct.


In our application we have inherited RepositoryItemLookUpEdit for make Columns property no localizable. It's very dificult to localize because the name scheme for resources ("repositoryItemLookUpEdit1.ColumnsXX"). The fieldname of a column is localizable too (I read in your forums that is corrected in Sisulizer). Our code in designer file is:

this.repositoryItemLookUpEdit1.Columns.AddRange(new DevExpress.XtraEditors.Controls.LookUpColumnInfo[] {
new DevExpress.XtraEditors.Controls.LookUpColumnInfo("Key", "IdUsuario"),
new DevExpress.XtraEditors.Controls.LookUpColumnInfo("Value", "Nombre del usuario")});

We use other LookUpColumnInfo constructors.


Please, could you support this case too?

Thanks in advanced.
Juancho.

Back To Top PM Private Upload Quote Reply

 Posted: Sun Nov 12th, 2017 11:44 pm
PM Private Upload Quote Reply
Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 1979
Status: 
Offline
Thank you for reporting this. I fixed it. The fix will be in the next build (370) that will be released in few weeks.

In the meantime you can use our internal build. I will send instuctions.

Ilkka



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

Current time is 04:26 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Error scanning .Net forms with DevExpress LookUpColumnInfo components.



WowUltra modified by Sisulizer Copyright © 2007-09 by Jim Hale - Based on WowBB Copyright © 2003-2006 Aycan Gulez

Sisulizer software localization tool - Three simple steps to localize