Note that I've specified in both cases, even though that's the default for those properties, just to be super-clear that that isn't the problem. In both cases, the control remains unchanged visually. (Then update App.cs to set MainPage to the right example.)īoth examples have a very simple situation: a control with two-way binding to a view-model, and a button that updates the view-model property (to simulate "the data has been modified elsewhere" in the real app). Each example is independent of the other - you can try just one. The sample code below can be added directly a "File new project" MAUI app (with a name of "MauiPlayground" to use the same namespaces), or it's all available from my demo code repo. The sample code is all below, but the fundamental question is whether this a bug somewhere in my code (do I need to "tell" the controls to update themselves for some reason?) or possibly a bug in MAUI (in which case I should presumably report it)? Label and Checkbox) are visually updated, indicating that the view model notification is working fine and the UI itself is generally healthy.īuild environment: Visual Studio 2022 17.2.0 preview 2.1Īpp environment: Android, either emulator "Pixel 5 - API 30" or a real Pixel 6 ![]() The problem I'm facing is that changes to the view model are not visually propagated to the Switch.IsToggled and ListView.SelectedItem properties, even though the controls do raise events showing that they've "noticed" the property changes. I'm using 2-way data binding in my MAUI app: changes to the data can either come directly from the user, or from a background polling task that checks whether the canonical data has been changed elsewhere. ( CollectionView has similar issues, but other confounding factors that make it trickier to demonstrate.) It's entirely possible that they're different problems that just share some common symptoms though. I think it may be worth testing this on a Pi 3 to see just how much of a platform dependency there seems to be.This question is about two MAUI controls ( Switch and ListView) - I'm asking about them both in the same question as I'm expecting the root cause of the problem to be the same for both controls. ![]() ![]() This isn't completely consistent but the overall behavior and feel of the emulator is such that it's apparent that there are internal delays that simply shouldn't be there, and probably aren't in the same emulator on other platforms. it will display "REA", then delay a little, then display "DY". For instance, in Model 3 emulation (the md5 checksum of level3.rom is ecd0a5a83fca19ea860fe565fad4b061), in BASIC, it will often delay halfway in the display of "READY", e.g. There are delays in display of things to the screen that shouldn't be there at all. This is why I believe we're up against an SDL issue - because the same phenomenon is visible in multiple emulators that link against SDL2.Ī note about it working "fine": in reality it's not really "fine" as such. continuously changing output to the screen. It has everything to do with a blinking cursor, i.e. The issue has nothing to do with whether or not there's a disk image involved. That version does not blink the cursor and the end result is the same problem. Try it with Model 1 emulation and TRSDOS version 2.3. ![]() The input works "fine" if the cursor is blinking (see below).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |