Combo Box Indicator: mouse wheel bug or feature?

Both ring indicator and slide indicator works fine even when the mouse wheel property is enabled.
But user can change value of the Combo Box indicator at runtime.
Shouldn't it be disabled, by default, just like for the keyboard? After all, it's an indicator.
I know I can disable the mouse wheel feature. It should be disable by default.
Or is there any use of this feature?
George Zou
http://webspace.webring.com/people/og/gtoolbox
Attachments:
Mouse Wheel bug.vi ‏12 KB

I think what you are seeing is a minor bug introduced by the lack of a "Combo Box Indicator" on the palattes. You must drop a control then change direction and there appears to be no built in mouse support property written on direction change leaving you with the default mouse wheel support for a control. Since this is a "windows only" property there might not be an easy way to write the property on direction change without querying App.OS target. And then what do you do on targets that do not have support for the property? Change the behavior? THAT would confuse just about everyone who works with multiple OS's
The work arounds:
Use the key navigation page and pay attention to mouse wheel support for indicators
Add your own combo box indicator to the controls palatte with the right mouse wheel support
Write a VI Analizer test for "Indicator with mouse wheel support"
In Short; this seems like one more thing that can easily trip up a developer. A VI Analizer test for this could help save us from ourselves. Consider uploading yours to the VIA Enthusiasts group
Jeff

Similar Messages

Drop-down list box and Mouse wheel.

When a xft form doesn't fit in the web browser (using webaccess) because it's bigger, the drop-down list box control has a distinct behavior than other controls like select control in html or listbox in VB.
When I click in the field to drop the list and scroll down the mouse wheel, the position of the control remains static while the form in the background scrolls down, so the drop-down list box is at the top of the other controls of the form. In most of the forms I've used, the "normal" behavior, if I can say it this way, is to scroll down the list. It doesn't disturb me at all, but some users have complained this behavior. Is there a patch for this control?
I've using form designer 5.0 with AWS version 6.2.121.0
Any help is appreciated,

No patch that I am aware of. It could be related to a memory issue within the browser container. I have seen this behavour many times over when dealing with larger forms.

Get element in combo box indicator

a vi generates an array of strings, how can I select one element with a combo box and send it to another vi as if it is a control?
thanks

hope this helps:
Harold Timmis
[email protected]
Orlando,Fl
*Kudos always welcome
Attachments:
Untitled 6.vi ‏6 KB
Untitled 7.vi ‏8 KB

Ring or combo box control of date

Hi, I am developing a GUI with ring or combo box indicating possible date, i.e., month, day, and year. Or is there a way to create multiple items ran sequentially in a ring or combo box control.
the time stamp is alright, but can't get rid of the current time display in the set time and date dialogue . thanks alot.

Hi rookieprgmer,
You will have to format the date into a string to create a ring that contains all the data for the month, date and year. One method for separating the date from a timestamp is to use the Get Date/Time String. You could then take the date string and use it in the ring or combo box. Attached is an example of how to use that function.
What do you mean by running multiple items simultaneously in a ring or combo box?
Hopefully I covered what you were asking about.
Sappster
Attachments:
date.JPG ‏7 KB

Combo box selector

Hello,
Why doesn't the selector work on a combo box indicator? It works when fine when I make the combo box a control, but then the user can type into the combo box and modify values. I am using a combox box to allow the user to select from a list of strings that represent the last 8 unique commands that we sent to a piece of test equipment.
Regards,
Kaspar
Regards,
Kaspar

Hi Kaspar,
because an indicator is to show something and a control is to control something! You can use an event case to check the user input or you can simply uncheck the "allow undefined strings" property.
Mike
Message Edited by MikeS81 on 07-15-2008 08:52 PM

Enumeration binding for combo box - missing feature

Hi,
In our application, combo boxes are usually employed for similar purpose as radio button groups: provide the end-user with an exclusive, static list of choices.
Unfortunately, JUComboBoxBinding.createEnumerationBinding method does not seem to follow the same paradigm as JUButtonGroupBinding.createEnumerationBinding.
In fact, for JUButtonGroupBinding, one parameter is "AbstractButton[] buttons", which is used for display purposes (end-user descriptions of the choices), and another is "Object[] valueList", which is the list of values for the corresponding attribute (usually, the valid values in the database for the column).
Meanwhile, JUComboBoxBinding is only receiving one array parameter, "Object[] values", which is used both for display purposes and for database values... This approach is very restrictive, as long as we expect to display in the combo box a descriptive text for the coded value in the database (and localizable, as well!).
Is this a known bug, or am I the first one to have noticed it? Is there any schedule for making this feature available?
Thanks,
Adrian

I'm not sure where my last reply went, so another try.
Unfortunately, I have the same feeling as usual, that my posted messages are not carefully read...
The main issue was the comparison between JUComboBoxBinding and JUButtonGroupBinding, and my question was about the possible future availability of a feature. Nothing about this in the answer...
Could I have an aswer to my original message, please?JUButtonGroupBinding is a custom control provided by JClient and has an api to let a user 'provide' custom Button objects instead of the default 'RadioButton's that would get created if none is passed in. The fact that you could use that to perform LOV kind of indirection of displaying a value other than what's set is 'a side-effect' of the original intention.
FYI, we already implemented an extension to JUComboBoxBinding which is just doing what I was asking for. It is not complex at all:( I was only thinking that it might be useful also in standard...The 'standard' way of getting this behavior you're asking for is to create a programmatic VO as suggested above, with both display/update attribute values and bind it to the ComboBox as an LOV Binding. And yes you can certainly create custom controls extending Swing and use the existing bindings or 'extend' them as per an application need.
Regards,
Adrian

Auto-Suggest feature in Combo-box LOV is not displaying non-unique values

Hi,
I have an auto-suggest feature implementation on a combo-box lov that displays the name and email-id of a list of people. There are non-unique names in the back-end, for example :
Abraham Mason [email protected]
Abraham Mason [email protected]
But when I use the auto-suggest feature and type in, say 'Ab', instead of showing both the Abraham Masons the auto-suggest displays only one of the values.
As in the example above the email-ids of the two Abraham Masons are different and unique.
If I use the conventional drop down menu of the combo-box then both the values are visible.
Is the auto-suggest feature implemented in a manner so as to display only unique values?
This is the implementation of the auto-suggest feature that I have done -
<af:column headerText="#{bindings.RqmtAtLevel1.hints.Owner.label}"
id="c23" sortable="true" filterable="true"
sortProperty="Owner"
filterFeatures="caseInsensitive">
<af:inputComboboxListOfValues id="ownerId"
popupTitle="#{ResourcesGenBundle['Header.SearchandSelect.Searchandselectanobjectusingad']}: #{bindings.RqmtAtLevel1.hints.Owner.label}"
value="#{row.bindings.Owner.inputValue}"
model="#{row.bindings.Owner.listOfValuesModel}"
required="#{bindings.RqmtAtLevel1.hints.Owner.mandatory}"
columns="#{bindings.RqmtAtLevel1.hints.Owner.displayWidth}"
shortDesc="#{bindings.RqmtAtLevel1.hints.Owner.tooltip}"
autoSubmit="true">
<f:validator binding="#{row.bindings.Owner.validator}"/>
<af:autoSuggestBehavior suggestedItems="#{row.bindings.Owner.suggestedItems}"/>
</af:inputComboboxListOfValues>
</af:column>
Thanks,
Anirudh Acharya

Hi,
don't find a bug entry about this, so if this indeed is a defect then this has not been filed. Do you have a test case ? If you have please zip it up and send it in a mail to me. My mail address is in my OTN profile (just click on my name until you get to the profile). Pleas rename the "zip" extension to "unzip" and mention the JDeveloper release you work with. The test case should work against the Oracle HR schema.
If you need to track the issue, I suggest to file a service request with customer support yourself
Frank

Silver Combo Box Display Style Bug

[LV2011, Windows XP]
There appears to be a small bug with the Silver-style Combo Box control when you right-click and select Visible Items->Display Style. For the string control a glyph appears properly, but for the combo box the glyph appears in the wrong place, and the colours are wrong. In fact, the glyph only appears properly if you click on it, or do something else to force a redraw of the control.
This combo box is a bit confusing, since it has no "Radix Shadow" part like the string control does, and in fact only the Silver-style combo box lets you display the "Display Type" glyph. The other styles of combo box have no "Display Type" feature in the "Visible Items" menu, but the "Display Style Visible" checkbox does appear on the "Appearance" tab of the Properties dialog box (though checking it has no effect, and it appears unchecked if you re-launch the dialog box".
I've attached a new version of the control which is close to fixing the bug, but the glyph region is 1 pixel skinnier than the string version. Copy this to your "..\vi.lib\silver_ctls\String" folder if you want it to replace the version in the palettes.
Jaegen
Solved!
Go to Solution.
Attachments:
Combo Box NI_Silver.ctl ‏6 KB

Jaegen:
Good catch, there is now a Corrective Action Request filed for this issue. It is correct that this property is
not supported by the Combo Box found in the Modern Palette. However, this should at least be documented in the
"Display Style Visible" property documentation if this is case, which it is not.
Thanks for alerting us to this error and if you would like to follow the CAR, look for CAR# 312717 listed in
bug fix reports for later releases of LabVIEW.
Please let me know if you have any questions or need any more help with this issue.
Tori W.
National Instruments

Response to mouse click by combo box list and underlying clickable label

Hello,
we developed a label responding to a mouse click by opening and thereby displaying an associated help text. The label extends a project specific hierarchy of labels and thus implements MouseListener, of course. Now we encountered a strange problem: It occurs when a combo box is placed above such a label in a panel. By clicking the combo box a selective list drops down and covers the label. As soon as a mouse click is performed on a list item directly covering (i.e., right in front of) the clickable label not only this item is selected but the help screen associated with the underlying label is displayed, too. So the mouse click is processed twice: as proposed by the combo box and unwantedly by the label. This behaviour could not be reproduced on other components being placed below a combobox. So the label itself seems to be the cause but we cannot imagine what could exactly be the reason for this double reaction. Perhaps anyone heard of something like that?
We are currently working with IBM Visual Age for Java 2.0 (Java version 1.1.8 with the according Swing version). The clickable label reflectively calls methods of a model to determine whether help is available and if so later on to open this help text.
Any help is appreciated!
Danilo

Thank you for your response. I tried both to check the focus and to consume the event. But I had to learn that labels are not able to catch the focus. I also was not able to consume an appropriate event of the combobox. So I finally solved the problem by extending JButton and implementing ActionListener. Thus my labels are actually buttons but I changed their appearance and behaviour so one cannot distinguish them from labels.

Question about using the Combo Box feature!

I have a form that I am trying to create for our company that will allow our field nurses to select what they need and print it more effieciently. The problem is that some of the selections are too long and I can't get the Combo box feature to allow them to be printed on multiple lines:
I have spoken to my supervisor about redoing the form to look like this:
But in order for us to meet state guidelines it has to be formated like the first because that is the state form given to us. I want to be able to either:
A) have the combo box multi-line auto text sized so it will get all the information into each box
OR
B) create text boxes at the end of the form that auto enteries the selected data from the second picture into boxes that look like the first picture.
Is there any way to do either of these?

A) No.
B) Yes. Create a text box with the following code as the custom calculation
script (assuming the name of the combo is "Combo Box1"):
event.value = this.getField("Combo Box1").value;
That way, when the user makes a selection in the combo-box, the value will
also appear in the text box. Just make sure to make the text box read-only
and set the combo-box to apply the selection immediately.

Firefox bug when clicking "open link in new tab" or mouse wheel

I am starting to get this bug for a last few days.
When I am trying to click "Open link in new tab" or, as usual using mouse wheel click, inside a Firefox window I got this for a couple of seconds before page shows up.
https://lh3.googleusercontent.com/-tbYPFx7jBn4/VIBxWfNBp8I/AAAAAAAABPM/yxArZ9Zbw88/s1000/bug.jpg
As you can see it's a mix of previous pages I was viewing for a last few days....
All those pages was not open at the this moment, it's just like a flash back :O)
Any idea what may cause it?

hello Bubunya, maybe that's an issue with hardware acceleration - please try [[Upgrade your graphics drivers to use hardware acceleration and WebGL|updating your graphics driver]], or in case this doesn't solve the issue or there is no new version available at the moment, disable hardware acceleration in the firefox ''menu ≡ > options > advanced > general'' (that setting will take a restart of the browser to take effect).

Bugging Array by using COMBO BOX component !!!

Hi,
Today, I create a flash with Array. I did use prototype
method to add one more fantastic function to sort the array
randomly. But when I include one combo box component with static
value in to the parent file, I have a big trouble. The flash file
stop running & give the alert of endless looping. Ah ha, what a
funny thing is happened out there?
If you want to produce this bug, please follow me.
Step1: Create 1 flash movie & name it "test.fla". Copy
the code below into the first frame.
Array.prototype.randomSort = function():Array {
var arr1:Array = this;
var arr2:Array = new Array();
var rand:Number;
while (arr1.length>0) {
trace(arr1.length);
rand = Math.floor(Math.random()*arr1.length);
if (rand == 1 && arr1.length == 1) {
rand = 0;
arr2.push(arr1[rand]);
arr1.splice(rand, 1);
return arr2;
Step2: Export the movie by Ctrl+Enter -> we will have
test.swf huh?
Step3: Create another flash & name it "main.fla".
Step4: In main.fla, create an empty movieclip symbol &
name it loader_mc. Drag it to the stage & five the instance
name "XXXloader_mc" for example.
Step5: In main.fla, Drag one combo box component to the stage
& add some data to the combo
Step6: In the first frame of main.fla, load the test movie
into XXXloader_mc. Try this
XXXloader_mc.loadMovie("test.swf");
Step7: Export main.fla. Ctrl+Enter again.
Congratulation, you are in the problem.

both together caused the problem and i don't see a problem
with your randomSort() method although destroying the original
array seems like a bad idea and is one of the 2 reasons for your
problem:
one, the combobox is executing your method (and every other
array prototype method that exists) every time it's clicked. that
looks like a bug in the combobox component.
and two, your prototype is causing a problem because it
destroys the arrays that call your method.

Bug? Mouse wheel doesn't work on Firefox and Chrome when added an application skin

I added a customized skin to make the background of Flex to transparent. The skin is created by the "new file wizard" and only changed the "backgroundRect" 's alpha to "0".
It works with no problem in IE8.0.6001 and Opera11.6 but doesn't respond to any mouse wheel event in FireFox 11.0 and Google Chrome 17.0.963.79.
Is it a BUG?
The flash player's versions are: IE:11.1.102.55; FireFox:11.1.102.55; Chrome:11.1.102.63; Opera:11.1.102.55

I opened a new Flex project and then tried again. I finally found that it's not a problem of flash but div rendering.
It seems Firefox and Chorme don't pass mouse wheel event automatically if div layout is set to "absolute".
Although this is not a Flex issue, any idea of passing that event to flash will be appriciated. I haven't find a way to do it so far :-(
What I'm doing is editing the "index.tamplate.html" to test. I added a div to contain the div of "flashContent" and set it's style to:
    position: absolute;
    top: 150px; left: 150px;
    height: 250px; width: 250px;
    z-index: 10;
Another div's z-index is set to 1 to test the overlay effect.
The reason why I added a div to contain the original div of flash, is I cannot figure out a way to effectively edit the CSS of the "flashContent" div.
Any help will be thankful!!

Combo box bug

When I make a selection in my combo box component the opened
selection box closes however the border of the selection box
remains visible.
How can I resolve this?

After troubleshooting I noticed that this only happens when I
have deselected the "export in first frame" checkbox in the
combobox linkage identifier. (had to uncheck this box to set up my
preloader)
It would be fantastic if someone could tell me whats going on

2.1 bug: navigation snapback using mouse wheel in Library

Running 2.1 under WinXP, I get this behavior intermittently:
When using the mouse wheel to advance from one image to the next in the Library module, the focus will snap backwards from the currently selected image to some previous image. It will not snap back to the immediately previous image, but to an image 2 or 3 positions earlier.
When this behavior appears, it persists, even after closing and restarting LR ... and most recently even after rebooting WinXP.

Could be a mouse driver thing, a LR thing, an OS thing.
For more direct control that doesn't slip, use arrow keys.

Combo Box Indicator: mouse wheel bug or feature?

Similar Messages

Maybe you are looking for