|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius | Page:   1 2 |
|
|||||||||||||||
| .NET WPF Styles not working - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello,I have just tried build 287. The WPF Styles test application crashes when run. Sorry for confusion. Our R&D planned implementation of better binary XAML/BAML scanning to build 287, but today release wasn’t planned. It is result of accidentally turning on this new XAML/BAML binary scan method to build 286, while it is not finished yet, and for this reason R&D decided release today new, not planned build with disabled this new scan method. New (finished) binary scan of XAML will be implemented to next build. Have a nice weekend, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Thomas, In the moment it seems we do not have a solution for that. I just got information from our our CTO and we found it is not fair to give some time frame to our customers. We all (incl. R&D) hoped that R&D could finish the new WPF parser in the last build - but that was way to optimistic. We are always open and honest to our customers and so we have to apologize in this case. We all really believed that our R&D could make the needed changes for some of special occasions in WPF that we found after release of that platform much faster. As of the post of Janusz that situation was not clear to the support team. So his expectation that the new parser makes it to the new build was still based on the old status we got from R&D before the holiday season. The only thing that it is clear at the moment is, that project localization for WPF will be finished before binary localization. Sorry for not having better news at this moment. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
The sample your sent us now works (build 288) if you use project localization (e.g. either add .snl or .csproj into Sisulizer project). However you use binary localization (added .exe). There the bug still exist and we have not managed to solve it. You can either switch to project localization or wait until we fix the binary localization. The Sisulizer version you have neither of above works. You need 288 in order to use project localization. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
tbratt Member
|
Hi, Is it possible to find out what the roadmap is for releasing 288 and also the future date for a build that allows binary localisation? Best regards, Thomas
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, This issue has highest priority and our R&D currently works on this, but as Jaakko wrote in his post, this problem is still not managed to fixing, and for this reason we can’t determine fixing date. Of course, we let you about fixing this issue, when it will be solved. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 06:01 pm | Page: 1 2 |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > .NET WPF Styles not working | |
Sisulizer software localization tool - Three simple steps to localize
