Search Issue Tracker
By Design
Votes
0
Found in
2018.4.0f1
2019.2.0a1
2019.2.3f1
2019.3.0a1
2020.1.0a1
Issue ID
1190542
Regression
No
[UWP] ContentDialog box doesn't disables apps interactivity
Steps to reproduce:
1. Download 1190542_repro.zip and open "SampleScene" scene
2. Build a UWP app
3. Click on ContentDialog button
4. Click on a different button
5. Hover over cubes
Expected results: App isn't interactive apart from the Content Dialog box
Actual results: The app is still interactive.
Reproduced with: 2020.1.0a8, 2019.3.0b7, 2019.2.9f1, 2018.4.11f1
-
lorrhill
Oct 14, 2019 05:55
Nice to see this post here. Thanks for that. https://yipcreations.com/chatroulette-alternatives/
-
zemayk
Oct 12, 2019 11:22
United Parcel Service (UPS) is the largest parcel/package delivery company. UPS is one of the leading global providers of supply chain management solutions and logistics services.
-
SHAREit1
Oct 11, 2019 10:19
Thank you so much for the information. Very good post
https://apkmoto.com/
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [UWP] Solution is created with "Data\Resources" directory which should not exist
- Audio clips on scene end while switching scenes when one scene has Timeline audio playing
- [Hub] Can trigger multiple concurrent Hub installations of the same editor version via Hub link
- [GI - Lightmapper] Invalid texels are not treated the same way in CPU and GPU lightmapper
- Canvas rect returning incorrect size when switching aspect ratios in the Game view
Resolution Note (fix version 2020.1):
When using XAML in a UWP app, change the Input Source under Player Settings -> Publisher Settings -> Misc to either "Independent Input Source" or "Swap Chain Panel" in order for Unity to better interact with XAML controls.
Using either one of these settings will consume mouse and touch events preventing them from triggering UI or GameObject interactions. For details on these settings (and which to use) reference: https://docs.unity3d.com/ScriptReference/PlayerSettings.WSAInputSource.html. Note that Keyboard input is not handled in this way and is always generated from CoreWindow; it may still trigger "OnKey" interactions in Unity.
Alternatively, you can call AppCallbacks::UnitySetInput from your native XAML code (e.g. MainPage.cpp) to enable/disable input from reaching Unity, depending on your XAML use-cases. For more information on AppCallbacks class, see: https://docs.unity3d.com/2019.2/Documentation/Manual/windowsstore-appcallbacks.html