I opened it up in Unity 6 Beta and everything was working as intended so I’m just gonna assume it was some version related issue.
I agree, I think it’s a good thing. Might be worth adding to the documentation, though.
I opened it up in Unity 6 Beta and everything was working as intended so I’m just gonna assume it was some version related issue.
I agree, I think it’s a good thing. Might be worth adding to the documentation, though.
I love this package! Its integration with MVVM and Redux is exciting.
I really want to apply it to the project, but I am worried that it has fatal problems that will be encountered in the middle or late development, could the official provide some more information about this package for reference.
Please tell us what are the main risks of using it now, I really love this design, but I couldn’t help worrying~
Thank you for your blessing, and if you can give some reference suggestions, it would be better~~~
What does [dt] mean in the package name, Developer Tools?
Did anyone get the worldspace ui document script working in XR?
I’m using the example scene included with XR Interaction package but it doesn’t work out of the box.
Have you solved this problem? I have a solution that uses XRITK to make UIToolkit run in XR to interact normally. However, there is a problem that the scroll related processing does not work.
You can read the code below to understand how it works
9785478–1403883–UIDocument3D.cs (5.5 KB)
Edit- PixelBlastGames’ post covered this before I posted
If you’re trying to build app-ui components in the UI Builder and they look broken, like zero size, check which Theme the builder is using in the top right. If its the Built In default runtime theme, try switching to one of the App UI themes
Edit: To use the App-UI thtmes in an editor window, use the tss named App UI, not one of the subsequent ones like App UI - Dark - Medium
Has anyone managed to use this with an Editor Window?
I’m trying to apply themeing, but I don’t know where to set the .tss. Theres no PanelSettings (that I know of) since its an Editor Window. Applying the StyleSheet to the root doesn’t seem to be enough.
You can load a stylesheet through c# rootvisualelement.stylesheets.add(stylesheet), which worked for me
Did anyone already use the grid view in App Ui?
https://docs.unity3d.com/Packages/com.unity.dt.app-ui@1.1/api/Unity.AppUI.UI.GridView.html
Can it be used like the ListView with binding to a list of elements from uxml side? Or only from code?
Otherwise I hope that I have time at the weekend to test it myself.
Regards Stefan
@StefanDu I think it is just from code.
It would be so nice to be able to contribute to this package to improve it (such as the UXML support for binding a list of elements in this case).
Its funny, I tried to get the List View to act as a Grid View, but since I do not have the full source, I could not set the height line and the lazy item loading mechansim accordingly. Thus I found ppl here talking about that Grid View inside the App UI. Will try to get it working, but not sure if those Controls work in Custom Inspectors, but they should, or ?
It’s very strange to see FOR INTERNAL UNITY USE ONLY on this package.
Аfter all, this is what working with the UI should look like. And now I have to write my own implementation of mvvm, navigation, etc.
@TomTrottel App UI components would work in custom inspector for sure. As soon as you use UITK in your inspector you can use App UI ones from what I have observed (all Muse tools are custom Editor windows and they use App UI stuff)
yeah I got it working two days ago. problem was that you have to register the makeitem and binditem delegates with the underlying listview of the ui app gridview. (which is clearly stated in the docs, but I oversaw it).
@highcore I think the disclaimer is a bit confusing too, it seems Unity doesn’t want to accept external feedbacks nor being responsible of any bug encountered by external users. I would not say “Internal Usage only” but just “Use at your own risks” at this point.
Can somebody explain to me what this package do exactly because i do not undestrand it
Its an internal unsupported project, its got a few ideas from React in there and allows Unity to be used for mobile app development - mainly for managing the UI side of app dev
It’s unsupported in the sense it’s internal and you will get no support if you have issues.
That said, they are fixing bugs faster than I can report them. I was just making a bug report for localization issue on some elements, and bam just as I complete it new version (pre.11) released with it already fixed. Release notes aren’t even up on the website at time for me posting this.