(fixed 3.6.2) Button size changes after editing the command

[DnGermany]

When editing button cmds, normally the position of the button is shown with the four numbered positions. Sometimes the button position box is blank, and after I edit the button cmd and press ok, the button changes size. I'm using DRM 3.5.3

[mr.zebra]

I think the button editor defaults to "all" mode. The only time i've ever seen the button position info blank is when it is different in WS and FS versions. I suspect that may be what you are experiencing here.

[DnGermany]

Yeah that's the problem with the blank boxes. Does that mean I have to edit the cmds twice, or is it a bug with the button size changing?

[mr.zebra]

No, you can edit the button command in the "all" mode just fine. The only thing that wont change is the button size/position.Which it sounds like you didnt want to change anyhow.

[Oldeman]

There is an bug/error in the handling of the button position parameter that under certain conditions causes the size to change when editing buttons. I have only seen it happen when a menu button has BOTH 4x3 and 16x9 screen format attributes AND EITHER the top or left side postions are the SAME for both screen formats. Seems to work ok if more than one button location is the same in both screen format modes. For example, when editing a button in the "all" mode three of the buttons locations are blank and the TOP location contains the number "345". If you edit the button action or command, when you finish the top position changes from "345" to zero for both button modes. The button size now extents to the top of the menu. Only way to correct it is to actually type the number "345" in again in BOTH 4x3 and 16x9 button edit modes, won't work changing it in "all" mode. This size error seems to happen when: 1. The Left/or Top button location is the default cursor location when you enter button edit mode. 2. Only the top OR left side of the button have the same location (number). In the button "All" edit mode, only the top or left side of the button actually shows a number. 3. You edit the button trying to change its attributes/action. I'm usually trying to change the button action when this happens. 4. BOTH pan&scan and wide screen are checked/selected for the VTS containing the edited menu. May not be necessary(?). This happens rarely, but has happened enough that I have tried to track down some of the conditions.

[DimadSoft]

Do you have a small sample vob which exposes the problem?

[susanalic]

I've experienced same issue in my last edited dvd. No problem in version 3.4.1. only which I've compared with. dvd with hide all except menus. http://download.yousendit.com/EBDD2A1D0A082D17 PGC 3 zona menu VTS 1

[Oldeman]

Take a button that has both a wide and a Pan/Scan mode. In the "all" mode Make the sides >>>> left=100, Top=200, Right=300 and Bottom=400. 1) edit the button, make the bottom wide setting 399. exit button edit. 2) edit the button in "all" mode it should show the 100,200, 300 and a greyed out bottom setting. 3) edit the button action command and then exit the button edit mode. 4) the Top setting goes to zero on my system. This error is strange as it only goes to zero in the left and up directions depending on the values in the right and bottom locations. It has something to do with initial focus (cursor location) when entering button edit mode. see attached example:

[manfy]

same thing happens in DRMP361

toaddub,
if dimad still needs sample vob, then latest download from julius 'strange movie'-thread can be used:
http://www.cdr-zone.com/forum/viewtopic.php?t=9243
symptoms can easily be reproduced with all buttons in VTS6 PGC31.

symptoms summary (from my old post):
* button edit window contains 3 tabs: wide, P/S, all modes
* all modes tab: top/bottom position is usually displayed (since they contain same values in wide & P/S), left/right position usually not.
ok so far!
* now, if you go to wide or P/S tab and accidentally (or intentionally) set e.g. left position to the same value for both modes and press OK/enter then everything seems ok on the outside, but i think DRMP sets those values internally to 0! (which results in prolonged button upon export)

proof:
open button edit window again for a.m. button -> it will display correct value for left pos in 'all modes tab' BUT when you press OK again, the left pos will be 'officially' set to 0, and you can easily recognize now since button frame is redrawn accordingly!

rgds.m

[CDR-Zone.COM]