I have ContantPage for adding new object to database. And one part of this page can be two sets of controls depending on state of ToggleButton.
How to implement such thing with Xamarin.Forms keeping in mind that I need to access values of this optional part from ContantPage?
Have two Layout views (e.g. StackLayout) one with the toggle off controls and the other with the toggle on controls.
Then bind the IsVisible property of the StackLayouts to the toggled property of the switch (one bound to be visible when toggled on, the other when toggled off).
Related
I use the create command in livecode to dynamically create several objects (graphic, field, button) depending of some conditions. I use "lock screen" and set up all properties: width, height, textSize and many many more... Then "unlock screen".
Here is the problem:
The syntax create btn "Rider1" creates a standard button, but I need an ption menu button. In the project browser, there is also an option menu "Button: Rider2Number", but trying to modify the button that was created by script fails: there is no option menu or popup menu in the list of button types. There are opaque and standard and some variations. It seems like the standard button and the option menu are two different objects. Which prefix (like btn) I should use to create an option menu by script?
You have to first the the style of the button, then set its menuMode:
set the style of last button to "menu"
set the menuMode of last button to "comboBox"
There are two ways to fully set the required properties:
1- If you already have an option button (call it "XYZ"), you can:
create button
set the properties of last button to the properties of btn "XYZ"
You then will need to modify things, like its name and contents.
2- You can set the properties of the "templateButton" as required, perhaps, again, to the properties of btn "XYZ". Then all new buttons will start off that way. You will still have to modify a bit as in the above case.
This is all so that you need not set the many properties that distinguish one type from another; that is tedious. Look up the "templateButton" in the dictionary. This property can be set on the fly, to any number of different types of buttons. Do you see? If you had a suite of button styles, you set the properties of the templateButton to any of those on the fly, and then any newly created button will be of that type.
There is only one button object class. The difference between the many types you are interested in is the "menuMode". Check this out in the dictionary.
We have are getting a strange behavior with the radio groups in our templates. Each of the radio groups is required, however, when a radio button from a group is selected, the next radio button (not the next group) gets focus. This will confuse our users as they will think they have to click each radio. Moreover, it would be helpful if an entire group could have focus as opposed to individual radios.
Is there a way to give the group focus as opposed to the individual radio?
The manner in which Radio Buttons (or any other type of input element) get focus in the Signing Session UI is not configurable via the API, nor is it configurable via the DocuSign web console.
we can change this option from Docusign settings.
Preferences->Account Administration->Features->signing auto-navigation rule-> Navigate Blank Required Fields
This will move focus to next field when a radio button is selected from Radio group.
I have a TextArea in my application that actually takes no interactions from the user.
Is there a way to either
Remove the scrollbar entirely and let me handle what happens when the scrollbar would appear?
Use a different object to display text to the screen? I need to be able to append text, but I don't need it to be highlight-able or take any user input.
According to your needs, you need to use label.
If you need TextArea, to remove scrollBars, you can do the next :
Use lookupAll(java.lang.String selector) method to find scrollBars, and
call scrollBar.setOpacity(0.0) for each found scrollBar.
2a. Don't call setVisible(false), as visible property (I believe) is used to TextArea to control scrollBar visibility.
My question is about focus management for web accessibility. When we launch a popup/dialog, does focus always need to go to the first focusable element for accessibility reasons or is it acceptable to set focus on an element that we think the user is more likely to want to work with?
For example, if a dialog starts with an input field and a cancel link followed by a dropdown and we think the user would most likely want to work with the dropdown when the dialog loads, is it ok to set focus on the dropdown element? In this case, how would the user know about the previous focusable elements existing on the dialog? But, if the dropdown is where 80% of the users will want to be when the dialog is launched, it doesn't make much sense placing focus on the initial input field...
thoughts?
Based on my research and what public opinion is: http://webaim.org/discussion/mail_thread?thread=5435 it seems like where the focus goes for a modal dialog/popup would depend on the usecase. For example, it makes sense to set focus on the search input field for www.google.com although there are preceding elements that the user can interact with -- this maximizes usability for screen reader and keyboard only users. But, in general the focus needs to go to the first element the user can interact with -- depends on the scenario.
I would caution against setting focus to anything other than the first form element or headings/content that introduce the form. See WCAG 2.0 Focus Order:
If a Web page can be navigated sequentially and the navigation
sequences affect meaning or operation, focusable components receive
focus in an order that preserves meaning and operability. (Level A)
While the case you present is I think an edge case, I think the focus order rules still apply. If you think that most users will want to interact with the select why not put it first in the form rather than set focus to an element in the middle of the form?
I've added a segmented control as the right bar button item of my navigation bar. The control has two segments and I'm attempting to use the control as bar button items. So I was wondering haw can I deselect a selected segment once the user preses it. I've already tried setting the selectedSegmentIndex property to -1 when the action method is called but that is preventing the segment from even being highlighted. Any idea on how can can get the segments to behave like bar button item?
do segmentedControl.momentary = YES; during setup or if using IB, select the Momentary checkbox in the Attributes Inspector.