[genachkaParticipant]

That’s too bad that it’s missing such consistency. In fact, to be honest, it’s been frustrating that there’s often a lack of consistency across functionality and API from one control to the other. We’ve been using jqxGrid for a long time now and have other controls from you that we use. But we need the filtering and sorting behavior on a tree or for the jqxGrid to have similar hierarchy functionality. We’re getting a hard push from our management to look else where and it appears that Infragistics (https://www.igniteui.com/tree-grid/remote-features), Telerik (http://demos.telerik.com/kendo-ui/treelist/index), and a couple others offer filtering and sorting functionality on their treegrids and it’s consistent with what’s offered in their grids. It’s great that you spend efforts on new controls, supporting new frameworks, but it seems that feature parity, consistency of features and APIs is just as important but seems neglected. Would you consider adding the sorting and filtering (if yes, can you provide timeline?)

[genachkaParticipant]

+1 for Aurelia support

[genachkaParticipant]

Not saying this is fundamental. But seems half backed when something as common as row details can’t be exported.

Anyway, your opinion and plan for future is very disappointing.

[genachkaParticipant]

Dimitar,

The link you provided would appear to be of no help. In the message from the user, he clearly states that he can’t get to the row details in his snippet and was requesting further assistance on July 8, 2013 at 1:58 pm but no further response came from support on his workaround attempt.

While I can appreciate that row details aren’t used by everyone that uses the grid, having them as an option for the grid but not being able to export them to me is missing fundamental functionality of the row details feature. As there would appear no official workaround, I hope this is something that gets supported soon as it would appear it’s been an issue for other users at least as far back as 2013.

[genachkaParticipant]

That’s disappointing to learn. I saw some posts from a couple years ago with the same questions and issues, including the one you referenced and was hoping that by now it would have been resolved. Not being able to export the row details makes using row details useless to me.

Is there a suggested work around (i.e. maybe using a nested grid resolves this?) for this?

And please add row details exporting to the feature request list!

[genachkaParticipant]

Hmm interesting. I’ll give that a shot.

I notice that when a dropdown list is used in a grid and checkboxes are enabled for the values that after you select the items, it separates them with a comma. Does it means that if I get the multiple values read from the JSON for city that it will on initial display in the grid be also comma separated?

[genachkaParticipant]

Is it not possible?

[genachkaParticipant]

Really? That’s expected behavior? That makes no sense! What’s the point of making the input field read-only if the spin buttons still can manipulate it? Which means that the value has changed in what was expected to be a readonly field and if it’s used in a CRUD operation it will potentially allow an update. If I have to make the widget disabled, then what good is the readonly property to me?

[genachkaParticipant]

Nevermind. This thread is more helpful, although still no real solution but a work around for I think is a strange approach in the first place… http://www.jqwidgets.com/community/topic/selectdeselect-all-in-checkbox-selection-mode/

[genachkaParticipant]

Thanks for your response. I’m sure there’s some internal logic to it, but I still find it strange that the result of the array contents should differ based on how they are selected/unselected (manual vs. checkbox header).

I’m looping through currently as a solution, but +1 for feature request to add “getselectedrowcount” that would work on both manual select/unselect but also those triggered by checkbox header select all/unselect all.

[genachkaParticipant]

Dimitar,

Not sure how that’s helpful? Last response is from jQWidgets in 2012 that it will be looked into.

[genachkaParticipant]

I encountered same issue and was hoping for a better solution than to loop through. From my view, I don’t agree that the assumption is wrong in expecting that getselectedrowindexes.length returns the count of selected items because it is 0 until something is selected. And if you select and unselect by rows, everything works correctly. Unselecting a row at a time does remove the array item. It only fails when you use the checkbox on the header to unselect that it fails as instead of it removing the array item, it (for whatever reason?) leaves the item but sets the value to -1. If it were to remove the array item just as a manual unselect did, this wouldn’t be an issue and wouldn’t require a loop or other workaround.

[genachkaParticipant]

Is it possible with another jqx control without alot of manual effort?

If not, feature request! 🙂

[genachkaParticipant]

Dimitar,

Thanks for the workaround. Hopefully it will be part of default behavior at some point.

[genachkaParticipant]

Turning it on when widget is created takes extra space. Filter is nice feature but not everyone will use it. So don’t want to force it on and take the extra space. But since toolbar I’m using for more than just filter, putting a filter toggle button doesn’t take much space and would allow users to decide if they also want to take more space by having the filter on or off.

[Author]

Posts