This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi |
|
|
|
|
I found a workaround to my problem: I implemented the popup control in a datatemplate in app.xaml instead putting the popup control inside a user control. Please let me know if you need more information regarding this issue - or if you are currently working to solve the problem. Kindly regards JohnR
|
|
|
|
|
Hi JohnR, Sorry for the delay in replying to this. This appears to be a WPF issue with the use of a button inside a popup inside a TreeView (which is what the property grid is implemented using). The TreeView internally detects the mouse down events and sets keyboard focus to the selected TreeViewitem. This fools the button into thinking it has not been clicked. You can reproduce the problem in your demo as follows: <TreeView> This results in the same symptoms as you report even though the property grid is not involved. The only workaround I have found so far is to style the TreeListViewItems that make up the PropertyGrid to have Focusable="False". However, this involves some fairly deep mucking around, and slightly affects the UI (it affects the highlighting of the selected property). To me it sounds like your data template workaround would be preferable. Unfortunately, because this is a WPF issue, I'm not sure there's anything more we can do to get around it. Sorry. |
|
|
|
