Ok, having looked at this more, it has something to do with the fact that I'm dismissing the overlays with a Command, and the touch event isn't being "handled" and is therefore going through to the underlying UI element. If I handle the Touch Down event separately from the Command I don't ...

In our UI, we have several tooltips. These are generally for the WebGL build for users who have mouse, but we've left them in the Android build and you seem to be able to activate them with a "press and hold" on the UI element, which is sometimes useful for our users. I'm seeing one proble...

Thanks, I may try this. In the meantime, setting the Unity target framerate to 30 fps seems to have alleviated the performance and battery issues, so I think we'll run with that for now.

Our game is 100% 2D using Noesis. We don't have any 3D objects. I think the increased efficiency of Noesis 3 may have been the issue. I was seeing it driving 80 FPS on my desktop. I think the attempt to maximize framerate was causing our WebGL customers problems. They were complaining of their lapto...

Our app is rendering Noesis via Camera Overlay render mode in Unity. Is there a way to turn off continuous rendering for this mode? The tooltip says the "Continuous Rendering" flag is ignored for Camera Overlay mode, and I don't fully understand the NoesisView.NeedsRendering flag. When we ...

Cool, I will try these suggestions. Thanks!

Running under Unity, I've set my Noesis default fontsize to 15px. This works good for our WebAssembly builds, but for tablets we'd like the default fontsize to be bigger. Maybe a better way to do this would be to just create different styles for tablet/mobile, but I was wondering if there was some w...

Hey, sorry to post another problem. Our product has been released under 2.2.6 now for 5 months now (WebAssembly) and we have had almost no problems. I don't think I've seen a single crash. Locally, after upgrading to 3.0, while running our app in the editor, I'm getting random crashes where the Unit...

That does help. I believe the answer is to stop trying to do what I'm doing. :) We won't die without the hover event in the listview. You can get to the same data by tapping anyway. WIth the mouse it is much easier to scan though multiple pieces of data with the hover, but we can just have the touch...

Hmm, yeah, I think I want to leave panning support in. If I pulled that, it would remove touch scrolling right? Our Webassembly version has tooltips that appear if the user hovers over a ListViewItem. Obviously that doesn't work in a touch enviornment. I'm trying to replace that behavior on Android/...