- Thread starter
- Admin
- #21
@Brownard were you able to take a look on the mentioned points? I didn’t check, if you pushed or posted anything somewhere else, so apologies, if points are already clarifiedI also realized, but hesitated to "annoy" @Brownard with this As you also realized now, let's see, if he can easiliy fix it. It's nothing I can do in xaml.
that won't be possible or is very complicated, because it would mess up the complete focus handling of MP2. In media libraries you can scroll easily by just putting the mouse into the side margins of the targeted scroll direction. In EPG the cell where the mouse is positioned has focus. If we would place scroll buttons, the EPG grid would directly loose focus, when a scroll button get's focus. Accordingly MP2 would not know which EPG cell to focus and where to scroll.
I agree here also for media related settings. @henso can better make a statement here how feasible the change is.
They are existing. If you can not see them, MP2 can not detect the chapters. Please try with other DVD's and if you never can get them, but with other players you can rise a bug report.
Was discussed also in the past, but never integrated. Maybe somebody else knows better. I'm not recording anything.
I think there was an overlapping problem with some elements. Need to check that, but I'm 1 month off from today.
@Brownard can check this. I also lost settings sometimes due to wrong clicks, so I can confirm it happens.
Was requested several times, but I'm not sure why we couldn't/didn't implement. @morpheus_xx can answer this.
I think that is not really needed and would make it very complicated. Every HTPC software supports certain formats. Several tagging softwares support the MP2 naming scheme.
Agree here. There is often still a focus problem. I'll see what I can do on skin side to improve this. But I think it should be generally happening even without any "tweaks" on skin side. I'm not sure why MP2 is loosing the focus so often.
Others also reported, that settings are not saved correctly. @morpheus_xx or @Brownard can hopefully take a look and fix that.