I use a SettingsPane to manage application settings. I want the user to be able create any number of Account option. This is a parent option which have children options like name, server, port, user and password. Each of them has extended description. If I add a new option through a button, SettingsPane doesn't show new option in the list. My first approach was to try to recreate SettingsView but SettingsPane creates additional views named Group_View_[Option Caption]_0_1 and Extended_View_[Option Caption]_1_2 which must be removed before recreating the SettingsView otherwise it throws an error like 'View must be unique'.
Is it possible to reload a view once it is created or to add dynamic options to SettingsPane?
Related
I'm wondering if it is possible to create a kinda scheme that is a list of custom fields and apply this scheme to an issue type.
This would cause that issue type to have all custom fields in the list.
I know you have to first associate the field with a screen and also a field configuration. But its this last step 'project and issue type scope' that is confusing me.
The only way I could see how to do this is to go into EACH custom field, then go to the CONTEXTS for that field, then add a new context associating the field and the issue type.
Field configurations and field configuration schemes don't seem to do the trick. It still seems a necessary condition to have your custom field associated with an issue type, but you still need to do that step above, to create a new context for each custom field.
I'm wondering if there is a way to group all the fields in a scheme and associate that scheme once instead of having to do it for EACH FIELD.
Am I missing something? Or it's just not possible?
You're looking for Issue Type Screen Scheme.
First create a default screen with the fields for issue type X. You can also create screens for Create and Edit too if you want
Then define a Screen Scheme for issue type X which says which of those screens to use for that issue type.
Then create an Issue Type Screen Scheme (ITSS) that uses the Screen Scheme for issue type X
It is convoluted but does work. Don't use Field Configurations unless you need to make the field required, and even then it's better to use a Validator on a transition. The only time you need a custom field context is if you have select lists with different sets of options for different projects. If possible, avoid using issue types in custom field contexts.
I need to implement a wallet pass design that doesn't match any of (Boarding, Coupons, Event tickets, Store cards or Generic passes) is it possible to create new custom template?
for example I need to
1- add icons beside fields
2- make secondary or auxiliary fields in column instead of row (under each other)
3- use primary keys similar to Boarding pass ones, but use different icon than (PKTransitTypeAir, PKTransitTypeBoat, PKTransitTypeBus, PKTransitTypeGeneric,PKTransitTypeTrain)
4- add additional label under Boarding pass primary fields
5- decrease font size of Boarding pass primary fields
5- add highlight background to one of the fields
I had copied data from one form to another previously and it worked bt right now when I am trying to copy the detail of field 'PASSPORT' from login.form to from_to.form it shows an error.
here's the login.form
and here's the from_to.form with error
Controls are not properties of their forms, and moreover they are not (by default) public.
In other words, you access controls by using a global variable having the same name as the control, and only from inside the form, as that global variable is private.
As mentioned above the controls are private to each form and not visible to each other unless you make them public.
You are trying to access login.TextBox1 from another class.
To access login.TextBox1 from the from_to.class you must do one of the following...
In the IDE on the login form select TextBox1 and set it's Public property to True.
or..
Open the project properties and select the "Make all controls public" option. this makes all controls visible across all forms.
That is, after adding new columns and objects to a module and closing/saving these changes, I manually reopen the module and the columns are gone, although the objects remain in their appropriate places. can anybody tell me how to solve this issue...
You need to save the View, not just the Module.
The following Procedure is taken from IBM's Help Page
Procedure:
In the module window, click View > Save As.
On the General tab, type the name. To overwrite an existing view,
type the name of the view you want to overwrite. Note: View names
are case sensitive. To overwrite an existing view, you must type the
name exactly as it appears in the Views list.
Optional: Enter additional information about the view in the
Description box.
Optional: Select or clear the Remember Settings for options.
Optional: Select a Default option for the view. The default view is
the view that is displayed when the module is opened. If you do not make it a default view, it is listed in the views list and can be
selected when the module is open.
Use the Access to this view section to define whether the view is
private or public.
Optional: Set additional rules for the view on the Advanced tab.
I'm developing a Firefox extension. There is a menu X which I need to show in both Tools menu and Context menu. Tools menu item and Context menu item are defined in same file but menu X in another file.
As I'm reusing menu X by id only last use of it is effective. How can I reuse it multiple time in same file without redundancy?
It can be done using XBL.
I haven't found a good solution either. The approach is rather to define the menu in the overlay only once and then clone it in your "load" event handler. You can then insert the clone at the second location. You have to be careful because ID attributes have to stay unique - so if your menu uses ID attributes you will have to additionally rewrite them. Ugly, I know.
IDs are, per definitionem, unique. That means you can't share the menuitem but you can share the code that gets executed when the action is invoked. One way to achieve this is to use commands.