Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index

Sorry, forgot the screenshot:

Am 16.05.2015 um 15:51 schrieb X Roemer:
Hi Regina,

thanks for your reply also.

The TabIndex you're writing about sounds pretty much like what I'm looking for - but I can't find it. I use python / pyuno and I can't find a property called TabIndex or something similar.

In this folder are two screenshots with all the properties of a RadioButton:

Or is it the case, that TabIndex means the index in the parent container?

Well, I tried to add all mixed elements from a list (RadioButtons were directly after each other) and it didn't work.
When I add the RadioButtons in a separate loop, they work.

Sometimes it would be handy to have more control, as you might have more elements inbetween the RadioButtons. So the designing gets more complicated. Like here in the middle row, where the checkboxes are working like radiobuttons. The advantage of a radiobutton is to see immediately what kind of choices are possible.


Am 16.05.2015 um 15:04 schrieb Regina Henschel:
Hi Xaver,

X Roemer schrieb:

I use always the same mechanism to add radio buttons by code. Usually I
add one after one, directly after each other, and they get grouped
automatically. But this time I can choose more than one and the others
don't get disabled. (See screenshot)

I know, it's better to show some code, but it would be a bit too much,
as the creation of widgets is splitted into several steps.

My questions are:
- Is there a mechanism to group radio buttons by code instead of adding
them one directly after the other?
- Can someone guess, what else can go wrong?


There the last paragraph in section 'Option Buttons'
"To combine several option buttons in a group, you must position them one after another in the activation sequence without any gaps (Model.TabIndex property, described as Order in the dialog editor). If the activation sequence is interrupted by another control element, then automatically starts with a new control element group that can be activated regardless of the first group of control elements."

So this is different from option buttons in forms, where grouping is done by the name property.

I have tested, that you really get a grouping, when the TabIndex is consecutive. That happens automatically, when you insert them in that order.

You can change the property 'Tab index' after you have inserted a control, but that will change the other tab indexes too. You might want to have a list of the wanted tab order when designing the dialog and start changing at tab index 0.

You can set and change the property TabIndex as well inside your program before executing the dialog. But unless you insert option buttons newly (instead of setting visible) when running your program, I think, that generating the dialog controls in the correct order while designing the dialog is much easier.

Kind regards

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.