jQWidgets Forums
Forum Replies Created
-
Author
-
Hi all!
Did this EVER happen ?!November 12, 2019 at 2:48 pm in reply to: Alternatives for ensurerowvisible? Alternatives for ensurerowvisible? #1073141.
Thanks for ‘selectrow’ explanation.
2.
The sample you are referring to still does not work.
I expanded like 20+ groups and clicked the button yet nothing happened …
Possibly 50 groups have to be expanded, if so, please rethink the sample.
3.
I do not understand why this is so convoluted.
If ‘grouping’ is ‘on’ one would expect that calling ‘ensurerowvisible’
will scroll down to the group containing the row, expand it if necessary, and show the row.
This would be expected and common sense behavior …November 11, 2019 at 9:54 pm in reply to: Alternatives for ensurerowvisible? Alternatives for ensurerowvisible? #107305Update on my last post – it appears that ‘ensurerowvisible’ does nothing is grouping is used, at least in the version 5.4
as is my case.
Is any workaround this?
How about ‘selectrow’ with grouping?November 11, 2019 at 9:37 pm in reply to: Alternatives for ensurerowvisible? Alternatives for ensurerowvisible? #107304This sample does not work … I have similar issues with using ‘selectrow’ and/or ‘ensurerowvisible’ when using ‘details’.
For this sample, after data loads, click on ‘showdetails’ for the first row, then click on ‘Select the 100 element’ button …
grid does not scroll at all.November 5, 2019 at 3:12 pm in reply to: grid grouping with row details grid grouping with row details #107245Forget about this …
It was my “custom” grouping.
Sorry for the mess.November 4, 2019 at 2:33 pm in reply to: grid grouping with row details grid grouping with row details #107240Howdy,
Again, if no grouping is used then “row details” works fine.
However, if grouping is being used then “row details” column appears right below level of the top group as a “separate grouping level”.
Here are some sketches which may help:
When no grouping is used the grid looks like this:
RowDetailsColumn, ClientNameColumn, OrderIdColumn
> Client1 Order1
> Client1 Order2
> Client2 Order1
Now, when user clicks in “RowDetailsColumn”, say in the first row, the gird looks like
RowDetailsColumn, ClientNameColumn, OrderIdColumn
^ Client1 Order1
OrderDateColumn, OrderQuantityColumn, OtherColumn
11/01/2019 100 Foo
11/02/2019 200 Change of quantity …
> Client1 Order2
> Client2 Order1
This is all good, this is what I want.
Now let’s assume user grouped on the “ClientNameColumn”
This is how I want grid to look like after grouping and collapsing is done:
GroupByCollapse/Expand, ClinetNameColumnGrouped
> Client1, OrderCount: 2
> Client2, OrderCount:1
This is working fine as well.
But when user expands by clicking on the GroupByCollapse/Expand column I want to see this:
GroupByCollapse/Expand, ClinetNameColumnGrouped
^ Client1, OrderCount: 2
RowDetailsColumn, OrderIdColumn
> Order1
> Order2
> Client2, OrderCount:1
Please note position of “RowDetailsColumn” and “OrderIdColumn”.
Originally, that is before any grouping was done, “RowDetailsColumn” and “OrderIdColumn” belonged to the same “level”.
This is what I want to preserve.
The point is that when I use grouping and “showrowdetails” is set to true,
the “row details” appears at the top, right under grouping level.
Here is the picture of what I get:
GroupByCollapse/Expand, ClinetNameColumnGrouped
> Client1, OrderCount:2
> Client2, OrderCount:1
and when the “GroupByCollapse/Expand” is clicked I get this:
GroupByCollapse/Expand, ClinetNameColumn/GroupedColumn
^ Client1, OrderCount:2
“RowDetailsColumn”
>
>
> Client2, OrderCount:1The problem is that “RowDetailsColumn”, all of the sudden, forms its own “grouping level” and “OrderIdColumn” falls under it.
As I said in my first email, I could fake “rowdetails” by using a hidden column.
But I thought that maybe there is a declarative way of achieving the same.January 12, 2018 at 2:27 am in reply to: Removing items from jqxTree Removing items from jqxTree #98231Has this issue been resolve?
I ran into it and … it is 2018 now!
If there is any workaround it please let me know.December 9, 2016 at 6:02 pm in reply to: Problems persisting docking layout Problems persisting docking layout #89729Hi Dimitar,
well, “layout” is useful only if it can be persisted. If user has to recreated page layout each time after page loads then it does not make much sense.
My understanding was that “saveLayout”/”loadLayout” methods are for this purpose, i.e. getting “layout” object from “saveLayout” then serializing it, saving in the database, and reloading via “loadLayout” on the way back.
Is there another way of getting “layout” object?
How should one create a persistent, user configurable layout using jqxWidgets?Thx,
Bogdan -
AuthorPosts