> This problem is easily (I hope) solved from within
> fdesign. You can specify the focus order by
> the order you raise(F3) the input field.
> (raising a object is no more than moving the object
> to the tail of the object list. By raising input fields
> one by one in the exact order you want the focus order
> to be, they will be added to the form in the order
> you raise them, thus the input focus order).
I think there is a problem with this when you are dealing with groups. Perhaps
someone out there can back me up (or shut me up telling me I'm wrong !!). I
have experienced strange behaviour when you have groups of object (xforms 086
on Linux-ELF).
In fdesign you have a group of objects (including buttons, input fields, frames
etc). You then raise or lower a single member of the group, say one of the
input fields. This sometimes appears to muck up the group membership (the
raised/lowered object leaves the group) and it certainly doesn't correct the
order of visitation with respect to input fields in other groups on the form,
or input fields not in a groupd on the form.
Also, slightly related, when adding items to a form dynamically (ie at
run-time, not using fdesign) - if they are added to an already established
group they "join" the group at the visual level of the previous group elements.
I have a mixer form (which depends on which audio channels linux has available
to it) to which I add mute radio buttons which must all be in the same group
for the "radio" to work. So my rough (psuedo) code is :-
for (i=0; i<max_channels; i++)
{
if (channel is available)
{
add a nice grey box on which the mute button sits
add to group "mutebuttongroup"
add the mute button (radio)
end adding to group
}
}
When I now display this form, all the mute buttons except the first mute button
are in fact hidden (lying underneath the "nice grey boxes") until I move the
mouse over the top of them at which point they "magically" reappear. My current
hack is when I do an fl_show_form I also iterate over the mute buttons calling
fl_show_object on each button.
I can supply code to demonstrate the above behaviour if you want.
Has anyone else noticed either of these odd behaviours or is it just my mind
playing tricks on me !!
Cheers for now,
TicH
------------------------------------------------------------------------
| Name - Richard Kent |
| EMail - kent@hydra.dra.hmg.gb |
| Plan - All work and no play.....hi ho, hi ho |
------------------------------------------------------------------------
_________________________________________________
To unsubscribe, send the message "unsubscribe" to
xforms-request@bob.usuf2.usuhs.mil or see
http://bob.usuf2.usuhs.mil/mailserv/xforms.html
Xforms Home Page: http://bragg.phys.uwm.edu/xforms
List Archive: http://bob.usuf2.usuhs.mil/mailserv/list-archives/