en-us Latest posts to this formQuestions about the Multi-Language Add-In for Visual Studio .NET https://www.jollans.de/tiki/img/tiki/Tiki_WCG.png https://www.jollans.de/tiki/ Sun, 05 Apr 2026 17:52:22 +0000 Laminas_Feed_Writer 2 (https://getlaminas.org) https://www.jollans.de/tiki/ {CODE} That is all that is required to hide the texts in this XAML node. This is a big simplification. Previously Multi-Language added the x:Uid attribute to identify the XAML node. It then stored the fact that a property was hidden in the project database. In the new version, Multi-Language does not add x:Uid or x:Name to a node either when you hide it, or when you select it for translation. In addition, Multi-Language stores nothing related to the node in the project database. The attached property m:Hide.Option is defined in the file MlExtension.cs/.vb along with the markup extension used to fetch translated texts. The definition is extremely minimal. {CODE(caption="C#" wrap="0" theme="default")} public enum HideOption { node, tree, none } public static class Hide { public static HideOption GetOption ( Object obj ) { return HideOption.node ; } public static void SetOption ( Object obj, HideOption value ) { } } {CODE} ===The property value is not stored at all.=== In particular, it is not a dependency property, and it may be applied to objects which are not dependency objects. As a result, the property can be applied almost anywhere. For example on a setter {CODE(caption="XAML" wrap="0" theme="default")} yle x:Key="TBStyle" TargetType="TextBlock"> {CODE} !!!!Alternativ usage m:Hide.Option="tree" In the previous example, it would be more convenient to hide the properties at a higher level, for the whole style. This is possible using the alternative value __m:Hide.Option="tree"__. {CODE(caption="XAML" wrap="0" theme="default")} yle x:Key="TBStyle" TargetType="TextBlock" m:Hide.Option="tree"> {CODE} This option would effectively mark the style node ===and all its child nodes as hidden===. __Note:__%%%Multi-Language recognizes this option, but there is no GUI support for inserting it. If you want to use this option, you must add it by hand. You cannot apply the option directly to a Resources node, but if you place your resources within a resource dictionary, you can apply it to the resource dictionary. So you could effectively hide all strings in your resources in the following way. {CODE(caption="XAML" wrap="0" theme="default")} {CODE} Finally, if you wanted to revert the __m:Hide.Option="tree"__ at a lower level in the tree structure, this is possible with __m:Hide.Option="none"__.]]> Sun, 26 Apr 2020 17:20:30 +0000 https://www.jollans.de/tiki/tiki-view_forum_thread.php?comments_parentId=1163 https://www.jollans.de/tiki/tiki-view_forum_thread.php?comments_parentId=1163 0 Tue, 21 Apr 2020 21:12:08 +0000 https://www.jollans.de/tiki/tiki-view_forum_thread.php?comments_parentId=1162 https://www.jollans.de/tiki/tiki-view_forum_thread.php?comments_parentId=1162 0 Thu, 15 Aug 2019 22:55:26 +0000 https://www.jollans.de/tiki/tiki-view_forum_thread.php?comments_parentId=1161 https://www.jollans.de/tiki/tiki-view_forum_thread.php?comments_parentId=1161 0 lns:m="clr-namespace:MultiLanguageMarkup" {CODE} Texts are now localized using the new markup extension, for example: %%% {CODE(caption="XAML Localization with m:Lang" wrap="0" theme="default")} Content="{m:Lang Apply}" {CODE} This instantiates the markup extension __LangExtension__ and passes the name of the resource as a parameter to its constructor. ===Switching the language at run time is handled in the markup extension===. The markup extension maintains a list of all the places where it is used. In most cases this list will contain one item, but if the markup extension is used in a DataTemplate, then it will contain one item for each time the template is used. The markup extension is added to your project as a source file, so you can read how it works if it interests you. I have tried to keep it as simple as possible, while doing the necessary work, and provided plenty of comments. Because language switching is now handled in the markup extension, the function __ml_UpdateControls__ is not necessary, and is no longer generated for XAML files. When you add support for switching language at run time, Multi-Language adds the project MLRuntime (as before) and makes a minor change to file containing the markup extension. It simple replaces the conditional compilation statement #if false with #if true, to activate the code which attaches to the language changed event handler. (If language switching does not work, you might start by checking that this change was actually made. (:biggrin:)) --- When you use Multi-Language version 6.03 it will automatically: *update the previous localization to use __m:Lang__ style *remove the function __ml_UpdateControls__ The previous method is no longer supported. Finally, this change also applies to Silverlight projects, but I have not tested it at all.%%% If anybody is actually using Multi-Language with Silverlight and has problems, please let me know. Phil]]> Sun, 07 Apr 2019 08:09:18 +0000 https://www.jollans.de/tiki/tiki-view_forum_thread.php?comments_parentId=1160 https://www.jollans.de/tiki/tiki-view_forum_thread.php?comments_parentId=1160 0 Tue, 24 Jul 2018 21:15:34 +0000 https://www.jollans.de/tiki/tiki-view_forum_thread.php?comments_parentId=1159 https://www.jollans.de/tiki/tiki-view_forum_thread.php?comments_parentId=1159 0 Tue, 13 Jun 2017 11:16:39 +0000 https://www.jollans.de/tiki/tiki-view_forum_thread.php?comments_parentId=1139 https://www.jollans.de/tiki/tiki-view_forum_thread.php?comments_parentId=1139 0 Tue, 30 May 2017 09:03:40 +0000 https://www.jollans.de/tiki/tiki-view_forum_thread.php?comments_parentId=1133 https://www.jollans.de/tiki/tiki-view_forum_thread.php?comments_parentId=1133 0 Wed, 17 May 2017 12:55:11 +0000 https://www.jollans.de/tiki/tiki-view_forum_thread.php?comments_parentId=1129 https://www.jollans.de/tiki/tiki-view_forum_thread.php?comments_parentId=1129 0 Fri, 05 May 2017 20:21:28 +0000 https://www.jollans.de/tiki/tiki-view_forum_thread.php?comments_parentId=1127 https://www.jollans.de/tiki/tiki-view_forum_thread.php?comments_parentId=1127 0 Tue, 04 Apr 2017 15:01:36 +0000 https://www.jollans.de/tiki/tiki-view_forum_thread.php?comments_parentId=1126 https://www.jollans.de/tiki/tiki-view_forum_thread.php?comments_parentId=1126 0