Note that there are some explanatory texts on larger screens.

plurals
  1. USCraig Graham
    primarykey
    data
    text
    plurals
    1. COThanks. Can see the logic, but the behaviour remains the same. It also remains the same if I shift the storyboard into one of the global resource files, use it from there in the dialog and explicitly load it with FindResource during program start, to try and force whatever precompilation/caching may be taking place. Even if I then apply the same trigger to the main UI window, the requestor still doesn't fade in the first time it's used.
      singulars
    2. COIt would be foul. List in itself has neither property change notification nor events, so if all you have is the List then you have to periodically iterate over all the elements in the List and all the elements in the OC and manually synchronise- complicated by the fact that while you're in the process of enumeration you can't delete any items and so have to make seperate buffer lists of records you want to get rid of and deal with them later. That has to be done seperately for each List<->OC relationship. If you have the model raising events for each item added then it gets easier. But why?
      singulars
    3. COAh well, it was a thought. I don't know a solution that keeps your extra elements in the StackPanel and avoids the DataGrid presenting its own scrollbar. The StackPanel's telling its children they have infinite height to use, so of course the DataGrid uses it. If it were me, next thing I'd try is having the DataGrid height constrained to the height of the StackPanel, hide both scrollbars, create a new scrollbar and bind that to something that controls the scroll positions of both the StackPanel and the DataGrid in a way that makes it look right. Complicated.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload