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
Quality Assurance
Bugreports
Archive
ACTION_EJECTCD doesn't work
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="mm1352000" data-source="post: 1185166" data-attributes="member: 82144"><p>I think we're on the same page. <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>I agree with your sentiment, and had thought about the possibility of state tracking. Issues with that approach:</p><ol> <li data-xf-list-type="ol">Not all drives have a tray.</li> <li data-xf-list-type="ol">Some trays can't be closed by command from the PC (eg. many modern laptop trays - they can be ejected by the PC, but the person has to physically close the tray because it's not driven by a motor).</li> <li data-xf-list-type="ol">State tracking is hard if a person doesn't consistently use the MP commands to load/eject discs.</li> </ol><p>It just seems like a whole can of worms that I really don't want to dive into. There's every chance of making the behaviour/situation worse.</p><p></p><p></p><p>Great! I really didn't want to have to step through that code to figure out what was going on. <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></p><p>Once again, I generally agree with your perspective.</p><p></p><p>From the code, it looks like MP does try to do what you're suggesting. However it seems that function is based on the item name. Because disc insertion/ejection changes the name, the "tracking" fails. This would be independent of the skin.</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1185166, member: 82144"] I think we're on the same page. ;) I agree with your sentiment, and had thought about the possibility of state tracking. Issues with that approach: [LIST=1] [*]Not all drives have a tray. [*]Some trays can't be closed by command from the PC (eg. many modern laptop trays - they can be ejected by the PC, but the person has to physically close the tray because it's not driven by a motor). [*]State tracking is hard if a person doesn't consistently use the MP commands to load/eject discs. [/LIST] It just seems like a whole can of worms that I really don't want to dive into. There's every chance of making the behaviour/situation worse. Great! I really didn't want to have to step through that code to figure out what was going on. ;) Once again, I generally agree with your perspective. From the code, it looks like MP does try to do what you're suggesting. However it seems that function is based on the item name. Because disc insertion/ejection changes the name, the "tracking" fails. This would be independent of the skin. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Quality Assurance
Bugreports
Archive
ACTION_EJECTCD doesn't work
Contact us
RSS
Top
Bottom