Re: BETA: NoesisGUI v2.1.0b10 (Unity, C++)
Thanks for the update. Just tried beta10, noticed an issue: DynamicResource-s no longer resolve:
Setup in ApplicationResources:
Then in MainPage.xaml:
This used to work in Beta4 -> I'd get the "Roboto" font on screen. In beta10, I get the default Noesis font.
Note that using StaticResource works, however that's not a good workaround for us since we load non-English fonts (or different fonts in general) dynamically based on UI language during startup.
Is this a known issue or should I open a bug?
Setup in ApplicationResources:
Code: Select all
<FontFamily x:Key="PhoneFontFamilyNormal">Fonts/#Roboto Regular</FontFamily>
<Style x:Key="appBarTextStyle" TargetType="TextBlock">
<Setter Property="FontFamily" Value="{DynamicResource PhoneFontFamilyNormal}"/>
</Style>
Code: Select all
<Button>
<TextBlock Text="test" Style="{StaticResource appBarTextStyle}" />
</Button>
Is this a known issue or should I open a bug?
Re: BETA: NoesisGUI v2.1.0b10 (Unity, C++)
Hi,
In the new Unity beta I get the error "Unable to convert '0' to 'CV.UI.UserControls.PlacementPosition' enum value".
Is this a noesis bug or something in the api has changed?
In the new Unity beta I get the error "Unable to convert '0' to 'CV.UI.UserControls.PlacementPosition' enum value".
Is this a noesis bug or something in the api has changed?
-
sfernandez
Site Admin
- Posts: 2984
- Joined:
Re: BETA: NoesisGUI v2.1.0b10 (Unity, C++)
Thanks for bringing this up, DynamicResource was not searching in the new Application Resources dictionary, we fixed it for the next release.DynamicResource-s no longer resolve
This is probably coming from a Binding.Converter incorrect type returned. In previous versions that error was failing silently, we added a message so users can fix the return type.In the new Unity beta I get the error "Unable to convert '0' to 'CV.UI.UserControls.PlacementPosition' enum value".
Is this a noesis bug or something in the api has changed?
Could you verify this is the problem you are seeing?
-
sfernandez
Site Admin
- Posts: 2984
- Joined:
Re: BETA: NoesisGUI v2.1.0b10 (Unity, C++)
@ivan:
About the enums problem I found it is a bug in our code.
We are fixing it and will be solved for the next beta we are going to release very soon.
About the enums problem I found it is a bug in our code.
We are fixing it and will be solved for the next beta we are going to release very soon.
Re: BETA: NoesisGUI v2.1.0b12 (Unity, C++)
Beta 12 released!
Re: BETA: NoesisGUI v2.1.0b12 (Unity, C++)
Hi,
I have noticed two problems with noesis.
In Unity , beta 04 I have a problem on the iPad 2. When a UserControl is created and after it is not used anymore the memory is still allocated so the memory usage gets very high.
In the previous version of noesis we didn't have this problem.
I haven't noticed that problem on the windows version.
On windows, when creating an image with a TextureSource, then enabeling a camera in front of the camera that Noesis is using and then switching back,
after that when I try to close the application it freezes. The problem is when I add a TextureSource to an Image.
Is this a known issue and do you need more detail about that?
I have noticed two problems with noesis.
In Unity , beta 04 I have a problem on the iPad 2. When a UserControl is created and after it is not used anymore the memory is still allocated so the memory usage gets very high.
In the previous version of noesis we didn't have this problem.
I haven't noticed that problem on the windows version.
On windows, when creating an image with a TextureSource, then enabeling a camera in front of the camera that Noesis is using and then switching back,
after that when I try to close the application it freezes. The problem is when I add a TextureSource to an Image.
Is this a known issue and do you need more detail about that?
-
sfernandez
Site Admin
- Posts: 2984
- Joined:
Re: BETA: NoesisGUI v2.1.0b12 (Unity, C++)
Is this also happening with beta 12?Hi,
I have noticed two problems with noesis.
In Unity , beta 04 I have a problem on the iPad 2. When a UserControl is created and after it is not used anymore the memory is still allocated so the memory usage gets very high.
In the previous version of noesis we didn't have this problem.
I haven't noticed that problem on the windows version.
If this is this something you can reproduce easily with a small example, could you please create a ticket in our bugtracker and we will investigate it?On windows, when creating an image with a TextureSource, then enabeling a camera in front of the camera that Noesis is using and then switching back,
after that when I try to close the application it freezes. The problem is when I add a TextureSource to an Image.
Is this a known issue and do you need more detail about that?
Re: BETA: NoesisGUI v2.1.0b12
We have released the C# SDK, this is the first version including the application framework. Please give it a try.
Re: BETA: NoesisGUI v2.1.0b12
Just tried Beta12 - thanks for updating it so quickly! Unfortunately there's an even earlier failure now that also blocks my test for DynamicResource-s.
For this XAML:
This code throws exception because the SolidColorBrush is likely frozen:
Used to work fine on beta10 and before. Since our code is sprinkled with color, opacity changes in a lot of places unfortunately this issue is a blocker.
For this XAML:
Code: Select all
...
<Grid x:Name="LayoutRoot" Background="Black">
...
</Grid>
...
Code: Select all
// ... code to load xaml here ...
Grid LayoutRoot = (Grid) FindName("LayoutRoot");
LayoutRoot.Background.Opacity = 0; <-- ERROR HERE: "Cannot set 'Opacity' property on object 'SolidColorBrush' because it is in a read-only state"
-
sfernandez
Site Admin
- Posts: 2984
- Joined:
Re: BETA: NoesisGUI v2.1.0b12
Resources coming from Application.Resources, Style.Setters, Trigger.Setters, named Brushes (like "Black"), are all Frozen.
I verified that the same occurs in WPF. In our previous versions we incorrectly allowed to modify properties of frozen objects.
If you need to modify them in code, then you have to Clone the resource before:
Or use a non-named resource:
Or you can use animations, as they automatically create clones of frozen objects.
I verified that the same occurs in WPF. In our previous versions we incorrectly allowed to modify properties of frozen objects.
If you need to modify them in code, then you have to Clone the resource before:
Code: Select all
Grid LayoutRoot = (Grid) FindName("LayoutRoot");
LayoutRoot.Background = LayoutRoot.Background.Clone(); // <- Create a modifiable copy here
LayoutRoot.Background.Opacity = 0;
Code: Select all
...
<Grid x:Name="LayoutRoot" Background="#000">
...
</Grid>
...
Who is online
Users browsing this forum: No registered users and 15 guests