AJAX single click doesn't work

[#1]

Clicking on a single item in a chart has no effect in AJAX (QV10). User must drag on a portion of the chart object to select a single item.

Is this intentional? It causes confusion.

For example, if I have a pie chart on click on one slice of the pie, nothing happens.

[#2]

Anyone??? Is this intentional behavior or a bug?

[#3]

Presumably a bug as the IE Plugin allows selection of seperate pieces of pie!

[#4]

I agree.

The other problem that occurs (perhaps as a result / perhaps not???), is we cannot shift-click or CTRL-click. Ajax simply takes the first item you click and ignores the fact that you are using shift or CTRL.

[Miguel_Angel_Baeyens]

Hello,

It's working for me fine in both verion 9 and 10 IR. What I do is first open the drop down list, then hold CTRL pressed before selecting anything, and then select several values. If the list is long and I need to scroll down, I keep holding CTRL and use the mouse to scroll down, selected values are still there.

If you instead just click and then press CTRL, once the mouse button is release, the selection is send to the server.

Hope this helps.

[#6]

Yes, it works correctly on list boxes but not chart objects.

With the plug-in, you can CTRL-click bars or pie slices on a chart or single-click a single pie slice or bar to select. That is what is not working for us.

Can you try this on a chart and see if it works for you?

[#7]

P.S., I am using QV10 / Ajax ZFP client / Internet Explorer 8.

[Miguel_Angel_Baeyens]

Ok, I see my fault. I assumed you were talking about listboxes/multiboxes.

Yep, I've tried and just clicking doesn't work. For single values, shift clicking and moving the mouse a few dots will work. If bars or pie slices are consecutive, you can drag the mouse over them to select them. If they are non-consecutive, CTRL doesn't work.

EDIT: Checked with QVS 9 and 10, Chrome 8 and IE 8. If it's a bug, it comes from v9.

[#9]

I don't think the Ajax client was much used / developed heavily prior to v9. I wonder if perhaps this was never tested? I am going to report it as a bug thru support and see if anything happens.

Given the way the product is intended to be used, this seems a serious limitation.

Thank you for checking with your version!

[#10 · Accepted solution]

This is fixed in SR1.