home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Development
General Development (no feature request here!)
Time for me to try to help. Volume OSD.
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="joboehl" data-source="post: 77621" data-attributes="member: 23490"><p>Hi, </p><p></p><p>I've being playing around with the MP for the last couple of months and really like the project and hope it will evolve a lot. </p><p></p><p>I don't really have C# experience and don't code for a long time, but decided to give it a shot. Probably my code is not nearly as optimized as it can be, and maybe not what the team whant in terms of design, and theres where I need help. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p>After thinking about different ways to implement a SystemWide Volume OSD, and dealing with difficulties to call GUI elements from Core components, I decided to change the approach. I developed a ProcessPlugIn that listens for a particular message. This message is send my the VolumeHandler core component. </p><p></p><p>In the process plug-in was easier to call any kind of GUI element. I decided to create a modified Dialog just to handle the Volume display, that obbeys a new skin file (DialogVolume.xml). I've tried other alternatives and had some prototypes using a mechanism similar to the WaitCursor. Altough doable, I lack the skill to make it look good like this one. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p>I'am attaching some screenshots of the OSD in Action. Still lot of things to do (like managing to get it over the Music Visualization. Any Idea?), but it's pretty much usable right now. And can be disabled by disabling the plug-in. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /></p><p></p><p>Well, if the developers don't have any objections about the way it was done (using a process plug-in), I can try to create a patch and submit to sourceforge. Please let me know. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p>Julio</p></blockquote><p></p>
[QUOTE="joboehl, post: 77621, member: 23490"] Hi, I've being playing around with the MP for the last couple of months and really like the project and hope it will evolve a lot. I don't really have C# experience and don't code for a long time, but decided to give it a shot. Probably my code is not nearly as optimized as it can be, and maybe not what the team whant in terms of design, and theres where I need help. :) After thinking about different ways to implement a SystemWide Volume OSD, and dealing with difficulties to call GUI elements from Core components, I decided to change the approach. I developed a ProcessPlugIn that listens for a particular message. This message is send my the VolumeHandler core component. In the process plug-in was easier to call any kind of GUI element. I decided to create a modified Dialog just to handle the Volume display, that obbeys a new skin file (DialogVolume.xml). I've tried other alternatives and had some prototypes using a mechanism similar to the WaitCursor. Altough doable, I lack the skill to make it look good like this one. :) I'am attaching some screenshots of the OSD in Action. Still lot of things to do (like managing to get it over the Music Visualization. Any Idea?), but it's pretty much usable right now. And can be disabled by disabling the plug-in. ;) Well, if the developers don't have any objections about the way it was done (using a process plug-in), I can try to create a patch and submit to sourceforge. Please let me know. :) Julio [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
Time for me to try to help. Volume OSD.
Contact us
RSS
Top
Bottom
