PUO 17 - Button select & activate

[blutach]

I have a question about this PUO. I know it can only be used in the PGCs. According to my reading of Taylor and LaBarge, it seems that when this PUO is activated, you can not move to another button, nor indeed select a button, which is either selected by default, by a Set HL_BTN command or via a force select (although Taylor says that button select and activate (=force select and force action) for a button is not mandatory in the player).

Just wondering if this is correct? And if there is a more definitive and precise view on the restrictions this PUO does from the likes of mpucoder and/or bigotti5.

Thanks in advance.

Regards

[blutach]

Sorry to bump, but does ayone have any info on this?

Regards

[setarip_old]

Hi!According to my reading of Taylor and LaBarge, it seems that when this PUO is activated, you can not move to another button, nor indeed select a button, which is either selected by default, by a Set HL_BTN command or via a force select... Just wondering if this is correct?Not that I have any understanding of the function(s) you've described but, couldn't you simply create a DVD with this specific PUO activated and see if it behaves as you've anticipated?

[blutach]

Yes, I could actually, but of course, not all players ahere to spec and some of this is "optional". So, I am hoping some extra info might emerge.

Thanks for the suggestion.

Regards

[Sir Didymus]

Hi blutach!

I hesitated a lot to provide some feedbacks until now, in order to give priority, of course, to the masters you have named...

But now, if you bump your thread, opening it to anybody...

:-)

Well, I always assumed (with a more or less simplicistic approach) that the role of the POUs, in general, is to prevent user operations to be performed. Straight and easy.

In the specific case of the PUO17, the flag indicates that the operations of button selection and activation are prohibited for all of the buttons in the given PGC.

Force selection and force activation have nothing to do with the PUOs: these define default actions to take (e.g. which button to automatically select and/or to automatically activate) when the button select end time expires.


although Taylor says that button select and activate (=force select and force action) for a button is not mandatory in the player


???

If you refere to the this table:

http://img299.imageshack.us/img299/4122/image1so0.th.gif (http://img299.imageshack.us/my.php?image=image1so0.gif)

on page 287 of the second edition, my interpretation is different: IMHO this table is not wrong; it just say that the function of symultaneously "selecting and activating a button" is something you can have or not in the remote control of your player. So, it is "optional".

But this has no impact on the compliance to the PUO17: in the standard player, the proper handling of the PUO17 is mandatory, AFAIK.
This means that all the players should react in the same manner when the PUO17 is set in the PGC: they should disregard the users commands of button selection (for instance up, down, left right moves) and action.

Cheers,
SD

[bigotti5]

You must not mix up UOP and PUO
UOP means "user operation" - what can the user do with his settop/remote using one or more buttons
e.g
angle change

resume


upper button selection


these three example-UOPs are mandatory for players (every player must offer these possibilities)

subpicture menu call


time play


button select and activate

are examples of UOPs that are not mandatory for players (not mandatory for players to offer these possibilities)

PUOs are flags to prohibit UOPs
So set PUO_17 prohibits:

upper_button_select
lower_button_select
left_button_select
right_button_select
button_activate
button_select_and_activate (can only be prohibited on players offering this possibility)

[blutach]

Hi bigotti5 and SD and thanks for the info.

So, would a correct interpretation be that if PUO17 is set, then despite the fact that there may be buttons in the cell, they can not be selected, moved to or activated and that you must just wait for the cell to play and then execute cell and post commands?

Regards