ListGrid header tool tips do not appear when column is sort enabled

SmartClient Version: v8.3p_2012-11-26/LGPL Development Only (built 2012-11-26)

Brower Version: IE 9

I have a ListGrid where I add create ListGridField objects and add them to the grid. On the fields I call setPrompt() to add a tool tip to the column header. On some of the columns I set canSort to true and some to false. When my application runs I only get tool tip prompts on the column headers for columns where canSort is false (no tool tip pops when canSort is true).

Also, when canSort is true the mouse cursor changes to a hand when it is over the column header and when it is false the cursor changes to an arrow.

Is there something I'm missing or is it not possible to have a tool tip for column headers where the column can be sorted?

[davidj6]

Have you re-tested with a more recent 8.3p build?

No. We've tried upgrading to a newer nightly a few times and each version we've tried has destablized our product UI. Why, do you have some reason to think this is fixed?

[Isomorphic]

Sorry to hear that - this may or may not be due to actual issues in SmartGWT (other possibilities include improper installs, caching, breakage due to invalid usage, etc).

If you think the problems were due to issues in SmartGWT, try posting about the issue, with the required details.

As far as your current issue however, the starting point is to try it against the latest patched build for your version. We can't look into issue reports that may have already been fixed (doubly so with no test case).

[davidj6]

It appears to work correctly with v8.3p_2013-02-01 but your test case could be different. Note that mouse pointer change is correct.

I need some clarification on you support policy/model.

Every place I've read indicates that if I run into a problem I should note the version number and include that in the submittal. It says nothing about a requirement that I roll to the latest nightly and verify it before I submit it. Has that policy changed or do I misunderstand the policy?

[Isomorphic]

You should always include the version number, yes.

When we get a good, clear issue report we generally just check the latest patched build. If we think there's a good chance the issue is already fixed, we'll ask you to check on that before looking ourselves, especially if there's no ready-to-run test case and you don't have a support contract with us.

It would be very unusual for us to investigate whether a bug is present specifically in an out-of-date patched build - it would have to be an emergency fix attempt for a production problem for a customer with a support contract.

Nothing about this policy has changed.

Also note that your organization doesn't have support at all.

You mentioned an out-of-date patched build. What about a 3.1 non-patched build? Is this treated any differently? Can I get that version somewhere? The latest release links seem to take you to a patched version.

[Isomorphic]

The point is to reduce duplicate issue reports and therefore duplicate work (for both our customers and community and for Isomorphic itself), so no, running 3.1 completely unpatched is not any better than running 3.1 with some patches but not others. In fact it's much worse.