Replies: 5 comments
-
Hello, 'GSonofNun! Thanks for submitting a new feature request. I've automatically added a vote 👍 reaction to help get things started. Other community members can vote to help us prioritize this feature in the future! |
Beta Was this translation helpful? Give feedback.
-
@GSonofNun Did you try creating some attached properties for this? This seems like the easiest solution |
Beta Was this translation helpful? Give feedback.
-
@GSonofNun ⬆️ |
Beta Was this translation helpful? Give feedback.
-
Yes, attached properties seem to work. It does make it harder to implement a two-way binding on the IsMuted property. And it doesn't change the fact that I think these properties should be available via XAML without developers all having to make their own attached properties. |
Beta Was this translation helpful? Give feedback.
-
Moving feature to next milestone out of hotfix release. |
Beta Was this translation helpful? Give feedback.
-
Describe the problem this feature would solve
When using a MediaPlayerElement in XAML, there were a couple properties on MediaPlayerElement's MediaPlayer instance I wanted to set/bind in XAML.
The properties I needed to set were IsLoopingEnabled and IsMuted.
<MediaPlayerElement IsMuted="True" IsLoopingEnabled="True"/>
However, these properties aren't available on MediaPlayerElement.
Describe the solution
The solution I ended up creating was using behaviors to set the properties on the MediaPlayer. Using them in XAML would look like this:
And something similar can be done for the IsMuted property
Describe alternatives you've considered
Ideally it would be great if there was a built-in solution to access these properties, but I don't know of any alternatives at this time.
Beta Was this translation helpful? Give feedback.
All reactions