|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Warning Invalid BorderStyle value : 0
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Warning Invalid BorderStyle value : 0 - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
bikemike Member
|
I just replicated an entry in my project - where it is currently localised from the CSPROJ file, I now have an entry that localised the Release dll. All the forms look similar in both sources in Sisulizer, though with the binary scanned one some stuff appears to be aligned further to the top and left with a TableLayoutPanel on one form. Not sure if that's the cause of the warning. In both cases the TableLayoutPanel has location.x and y as 9. Is this warning a concern? I can't see any difference in the execution between the two localised dlls (I changed a string to be sure I was swapping them), though I may be missing it.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
When Sisulizer scans CSPROJ it reads extra information for .cs source code files. When Sisulizer scans EXE it reads the same information from IL data. These two logic are separate but are written to work in the same way. However there might be a difference. The extra information is ment for visual editor and this is why they might see different. However most likely this does not affect to the resource data itself. To check this I need EXE and the .resx/.cs file of the form having TableLayoutPanel. Can you upload them to me? Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
If your .NET assembly file requires some other assembly files (DLLs) they are not currently included into the exchange package. Only the assembly that is added to the SLP is included. I fixed this in 295. The new build also includes all custom DLLs that the assembly uses. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Thank you for the files. Can you also send me AboutBox1.Designer.cs? Also the zip file contain Spanish satellite assembly file xxx.resource.dll. Can you send the original EXE file that contains AboutBox1? Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
bikemike Member
|
Woops, done!
|
||||||||||||||||
| |||||||||||||||||
| Current time is 08:21 pm | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Warning Invalid BorderStyle value : 0 | |
Sisulizer software localization tool - Three simple steps to localize