|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Sisulizer not parsing our derived controls
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Sisulizer not parsing our derived controls - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
lachmayr Member
|
I have a TestPage.xaml file that uses our AppPage and TabbedViewController framework controls that were derived like this:
and this:
Here's the beginning of the TestPage.xaml file:
Now, Sisulizer is telling me it can't 'map' the fwrk:TabbedViewController (during scan process) and I assume this is also the reason Sisulizer cannot build the TestPage.es-ES.xaml. Is there a way around this? any tips on how to get Sisulizer to recognize our framework controls? Why does Sisulizer not complain about the fwrk:AppPage reference? Your help is most appreciated. Without figuring this out, we are not able to move forward with Sisulizer! -Stephen
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello Stephen, Lately you sent to us your Sisulizer project with EXE file for this thread: http://www.sisulizer.net/view_topic.php?id=1352&forum_id=4&jump_to=7929#p7929 I found in this project testpage.xaml, and fwrk:TabbedViewController component mentioned in your post, but I can’t to test scan/build/component remapping without your source files (Visual Studio project files). Could you send to us these files via “Private Upload” button? BTW: testpage.xaml contains also ResourceDictionary resource. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
lachmayr Member
|
Thanks for the response. I've uploaded all the project files. You should be able to unzip it and run the UnitTests solution, which includes the ViewControllerDriver project I am having problems with. -Stephen
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
lachmayr Member
|
Did you get the files? Any insight yet into this issue? -Stephen
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, Yes, I’ve got files and I’ve reproduced it. Issue was forwarded yesterday to our developers. Of course, we let you know about investigation results. Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 06:01 pm | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Sisulizer not parsing our derived controls | |
Sisulizer software localization tool - Three simple steps to localize