| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002099 | NoesisGUI | Unity | public | 2021-08-31 21:34 | 2022-05-20 20:33 |
| Reporter | stonstad | Assigned To | jsantos | ||
| Priority | normal | Severity | major | ||
| Status | resolved | Resolution | fixed | ||
| Product Version | 3.1.0 | ||||
| Target Version | 3.1.1 | Fixed in Version | 3.1.1 | ||
| Summary | 0002099: 3.1.x Upgrade Can't Find XAML | ||||
| Description | Despite my best efforts I can't seem to get 3.1.x Noesis to find certain XAML files that worked previously in 3.0.x and that appear to have the correct file path. My installation workflow entailed deleting all previous NoesisGUI files, and then unzipping Noesis into Assets/Plugins/NoesisGUI. My user interfaces exist in /Assets/User Interface. I am also seeing Unity errors warning me that unique hashes are not generating correctly for Noesis created .asset files. I confirmed correct file paths and dependency references in XAML. For some reason I had to keep reimporting fonts to get them to be finally found. In some instances the issue appears to be static references in OnInitialized. I disabled preview -- but it looks like this Noesis 3.1 may? be calling OnInitialized in my non-variant code which has external dependencies. | ||||
| Steps To Reproduce | No reproduction project yet. I can't run yet. | ||||
| Platform | Any | ||||
 |
OK, the cause was a user control that had variant code in InitializeComponent. InitializeComponent was failing within Noesis code which in turn caused the XAML to not be found error to appear. The error message shown was incorrect. The new behavior would be fine if the error message was not misleading. |
 |
There are many things wrong in 3.1 if you are upgrading from 3.0, we are solving all of them with the idea of having a 3.1.1 soon. But just a few comments regarding your installation:
After that, our script should do a reimport all to make sure the importer for each XAML is 'XamlImporter' and for each font is NoesisFontImporter. This step is missing in 3.1.0 and must done manually, xaml by xaml and font by font. Yeah, far from ideal. Rigth now, if you do a Unity reimport all, fonts are properly fixed, but XAML won't be changed. @sfernandez I know you have been doing tests importing projects from 3.0, am I missing something here? |
|
|
Understood. I am reading the tutorial and release notes. |
|
|
I deleted the unzipped folder in Unity. I deleted all .asset files. I installed via the documented package installation process. I'm seeing lots of quirks with UI and purple backgrounds in sprites. I seem to recall this was an issue I encountered before with an undefined style. It is possible that I had customizations in theme files. But the major issue I am seeing is a licensing error. I think I need to take a break from this release to stay productive.
License Error.PNG (131,834 bytes) |
 |
I've just sent you an email with your updated license information, required for NoesisGUI 3.1. |
|
|
Thanks, Sergio. Much appreciated. |
|
|
This was all largely user error. Please feel free to close -- thank you for the help. |
|
|
We'll keep it open because we should detect if user unzips the plugin inside Assets and avoid throwing a NullReferenceException in that case. |
|
|
"1. You shouldn't unzip the package inside /Assets. It must be extracted somewhere else, and then imported from the package manager. The steps are described in the Installation section, but I will review them to make this clearer." Unity references the package files indefinitely from the external directory location. So although I do not store the package files in Unity I have to place them in SCM with the project. Do you put the files in a folder that is a peer to \assets? |
|
|
Yeah, we are doing something similar to that. |
|
|
I think we solved everything here. I am closing this. Thanks again for your feedback! |
