If you have worked on installscript of InstallShield. You might also came across to this condition when you have a 'Feature View' and all in the list are selected by default. How can we deselect them?
Thanks.
Look at the FeatureSetData() and FeatureSelectItem() functions:
FeatureSetData ( szFeatureSource, szFeature, nInfo, nData, szData );
The FeatureSetData function sets properties and data for the specified feature. Most of the settings correspond to the properties in the Features view.
FeatureSelectItem ( szFeatureSource, szFeature, bSelect );
The FeatureSelectItem function sets a feature's selection status to either selected or not selected. You can use FeatureSelectItem to change selection status before displaying features in feature dialogs, and you can use it to change or override selections afterward, depending on your setup's requirements.
Related
I have a process that involves extending the "Files" menu that is located on (most) acumatica pages (next to notes and activities in the top right)
I would like to add two columns to the table that appears in the smartpanel.
I have been looking for the source code/data behind this smart panel and I cant seem to find it, is it tied into SM202520 (search in files)? Can it be extended?
Am I better off just adding a PXAction button to the 3 or 4 pages I want my extended "files" menu to be?
Thanks
There's no DataView bound to that dialog, you can verify that by using inspect element shortcut key CTL+ALT+CLICK on a grid column header:
In order to be customized the grid needs to be bound to a DataView which inspect element reveals it is not. The lack of DataView binding is by design and therefore that dialog can't be customized.
A grid that can be customized will show the View Name property:
I created a DAC extension mapped to an extension table off of SOShipment. I have two custom fields in the extension table that I'd like to add to the Sales Orders entry form, specifically the grid in the Shipments tab. When I go to the layout editor for this form and select the Grid: ShipmentList under the Shipments tab, there are no fields in the Add Data Fields tab on the right. Also, I see a yellow circle with this error in several places:
The "ShipmentList" view is not found. Try to publish the customization project.
I published the customization project, but the error persists. To my knowledge, we haven't done any customization that would've touched the ShipmentList view. What is the issue here and how do I resolve it?
Since you are trying to add those Custom fields to the Grid: ShipmentList(which primary DAC is SOOrderShipment), make sure you add the Custom Fields to the Correct DAC extension, the correct DAC extension should be for SOOrderShipment.
(You have to rename the DataView because in base code, this Dataview is named shipmentList. However, the editor Tool when generating Customization Script for that screen is assigning ShipmentList(Capital S) to Datamember instead of correct Dataview name. )
So, then Go to Section Screen, Select SO301000 screen, select the Grid(ShipmentList) under the Shipments Tab, select Action->Edit ASPX, then locate on DataMember="ShipmentList" (with Capital S) and replace it for DataMember="shipmentList" (lowercase s). Then click on "Generate Customization Script" and publish your Customization.
After publishing, go to SO30100 Screen, select correct Grid and you will be able to see new Custom Fields and the warning message gone.
In my Android project I've already created a custom dialog: A class named SelectColorDialog, extending Dialog, that allows the user to view a large matrix of color cells in order to select a particular color. The dialog returns the selected color value (as Integer) to the dialog initiator – typically an Activity – via a callback function.
I've a similar custom dialog, SelectTypefaceDialog, to allow easy font selection. A list of available typefaces are shown, as ListView rows, each identified by name and with an associated short sample text rendered in that typeface. The available typefaces include usual droid fonts, such as NORMAL, MONOSPACE, etc. as well as any externally sourced TTF font files that the user cares to load into a particular subdirectory on the SDCard.
These custom dialogs were not initially designed to be used directly in conjunction with SharedPreferences, preferences definition XML files or with any PreferenceActivity. Instead of, each dialog can be popped up from any activity, via the user pressing a button or via a menu item. The activity classes that create these dialogs also have internal callback classes, selection event listeners, to detect when the user selects a color or font.
These two dialogs do not have OK and Cancel buttons. Instead, the user just clicks on an item - a view of some kind - in the dialog to select the corresponding color or typeface value (implicit OK) or else presses the device’s back button to dismiss the dialog with no action taken (implicit Cancel).
I would now like to go further and incorporate these two custom dialogs into the shared preferences framework via a preferences.XML and an associated PreferenceActivity.
I would prefer to base two DialogPreference subclasses directly on these existing dialogs if possible, but I cannot see how to do so. I suspect that I cannot, and that I'll need to start all over again, and copy or adapt all the java code that is presently in the custom dialog classes – for color or font display and selection – directly into the custom DialogPreference classes instead, perhaps by overriding onCreateDialogView() and/or other methods?
This question may be a bit old, but I hope to help those, looking at the same problem in future: just extend Preference instead of DialogPreference. DialogPreference is designed badly and expected "official" way to use custom Dialog - overriding protected showDialog method does not work, because this single method contains half of class logic.
If you select multiple entries by using the CTRL button you can select multiple view entries. I need to find a way to prevent this to happen. How can I turn off this feature?
Because the listview is a custom dijit control, the properties are adjustable in CSJS.
This is the solution:
dijit.byId('#{id:listView1}').bAllowMultipleSelection = false;
dijit.byId('#{id:listView1}').initVirtualList();
In my program I want the user to be able to choose between some options so I was using wxChoice component. Unfortunately after user interaction (clicking a button) I have to show custom text (not from my predefined list). Everything works fine if I use wxCombobox control but the drawback of this approach is that each time user selects an element from a list, selected text is highlited. It is annoying. I want the component to be read-only like. How to achieve this ?
Some code to visualize my question:
wxComboBox* viewAngle = wxDynamicCast( owner->FindWindow
( ID_CHOICE_3D_VIEWANGLE ), wxComboBox );
viewAngle->SetSelection( wxNOT_FOUND );
viewAngle->SetValue(_("Custom View"));
EDIT:
This control is used to set camera view in 3D object viewer application. Possible options are like: top, left, right, etc. It is also possible that the user moves 3D object using mouse. In that case I want my combobox to display "custom view" string. However "custom view" should not be a part of combobox list because selecting this option does nothing.
wxWidgets default implementation alwasy marks selected text. Which might be misleading for the user because he might think that he is expected to input any text.
IMHO, the custom text should be added to the wxComboBox control, the program could just ignore it when user selects that option.
Also, the wxComboBox's wxCB_READONLY style could be used to avoid the highlighting thing.