1
Bug Report / Re: Grid break with string of specific pattern
« on: January 30, 2020, 07:20:41 am »
We confirmed that it was fixed.
Many thanks.
Many thanks.
ParamQuery Grid
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1] 2
2
Bug Report / Re: Grid break with string of specific pattern
« on: January 21, 2020, 02:10:59 pm »
I'm relieved.
Thank you.
Thank you.
3
Bug Report / Re: Grid break with string of specific pattern
« on: January 21, 2020, 01:47:01 pm »
By applying the code presented, it was displayed correctly.
Many thanks.
By the way, will this fix be included in future releases?
Many thanks.
By the way, will this fix be included in future releases?
4
Bug Report / Grid break with string of specific pattern
« on: January 20, 2020, 06:52:37 am »
Hi.
If a character string of a specific pattern using tags is set as data, the grid will be broken.
Pattern: "<<x"
* x is any alphabet
Specifically, it occurs only when the alphabet continues after "less than" is repeated twice as shown below.
NG:
<<x
OK:
<
<<
<<x>
<x>>
x>>
>>
>
<<=
<<あ
Is there any workaround for this?
Thank you.
If a character string of a specific pattern using tags is set as data, the grid will be broken.
Pattern: "<<x"
* x is any alphabet
Specifically, it occurs only when the alphabet continues after "less than" is repeated twice as shown below.
NG:
<<x
OK:
<
<<
<<x>
<x>>
x>>
>>
>
<<=
<<あ
Is there any workaround for this?
Thank you.
5
Bug Report / Re: Nested grid columns are grayed out
« on: January 08, 2020, 07:47:43 am »
We confirmed that it was fixed.
Many thanks.
Many thanks.
6
Bug Report / Re: Nested grid columns are grayed out
« on: September 20, 2019, 06:56:49 am »
As a result of applying the settings you gave us, drag-like behavior is possible, but the following problems remain.
1. In the grid using Nested Grid or freezeCols, it can't be selected correctly.
2. Can't copy while maintaining the grid format with tabs and line breaks like when setting {type: 'cell'}.
Is it difficult to prevent overlays from being displayed when setting {type: 'cell'}, as in version 6.1.0 and earlier?
1. In the grid using Nested Grid or freezeCols, it can't be selected correctly.
2. Can't copy while maintaining the grid format with tabs and line breaks like when setting {type: 'cell'}.
Is it difficult to prevent overlays from being displayed when setting {type: 'cell'}, as in version 6.1.0 and earlier?
7
Bug Report / Re: Nested grid columns are grayed out
« on: September 19, 2019, 12:05:53 pm »
With the settings you have given, overlays are no longer displayed, but we can no longer drag and copy grids
that were possible when selectionModel was { type: 'cell' } or not set.
Is there a way to allow drag and copy of the grid without displaying an overlay?
that were possible when selectionModel was { type: 'cell' } or not set.
Is there a way to allow drag and copy of the grid without displaying an overlay?
8
Bug Report / Re: Nested grid columns are grayed out
« on: September 05, 2019, 06:05:44 am »
After applying the settings you gave me, the overlay was no longer displayed.
Thank you for your advice.
Thank you for your advice.
9
Bug Report / Nested grid columns are grayed out
« on: September 04, 2019, 08:17:56 am »
As a result of upgrading to 6.2.4, the following two problems occur in the nested grid.
Are these bugs?
1. Click on the icon to expand the grid and the area from the icon column to the bottom of the nested grid is grayed out.
2. After expanding the grid, click on the column of the parent row, the area from this column to the bottom of the nested grid is grayed out.
These did not occur in version 6.1.0, so please check.
Are these bugs?
1. Click on the icon to expand the grid and the area from the icon column to the bottom of the nested grid is grayed out.
2. After expanding the grid, click on the column of the parent row, the area from this column to the bottom of the nested grid is grayed out.
These did not occur in version 6.1.0, so please check.
10
Bug Report / Re: Default order after filtering by range
« on: January 28, 2019, 02:38:43 pm »
We confirmed that it was fixed.
Thank you very much.
Thank you very much.
11
Bug Report / Re: Default order after filtering by range
« on: December 19, 2018, 11:23:16 am »
In the list without paging, We confirmed that it is fixed.
However, in the list where paging exists, this bug is still occurring.
You can confirm by adding the following settings to the demo page.
https://paramquery.com/pro/demos/filter_header_local
However, in the list where paging exists, this bug is still occurring.
You can confirm by adding the following settings to the demo page.
https://paramquery.com/pro/demos/filter_header_local
Code: [Select]
pageModel: {
type: "local",
rPP: 10,
rPPOptions: [10, 100, 500]
},
12
Bug Report / Default order after filtering by range
« on: December 04, 2018, 07:12:46 am »
We were wondering if this is a glitch for the latest version.
Once we filtered by range, the default displaying order won't be restored even though we remove the filter.
For example, see the default order for the demo page.(see 1-1.png)
https://paramquery.com/pro/demos/filter_header_local
1. Filter only "United Package" by Shipping Via and the result is correct.
(Uncheck Shipping Via and check "United Package": see 1-1.png, 1-2.png)
2. Remove the filter but the displaying order look different than the default displaying order.
(Check Shipping Via: see 2.png)
Select filter for version 4 was restored the default dsiplaying order by removing filters by the way.
Once we filtered by range, the default displaying order won't be restored even though we remove the filter.
For example, see the default order for the demo page.(see 1-1.png)
https://paramquery.com/pro/demos/filter_header_local
1. Filter only "United Package" by Shipping Via and the result is correct.
(Uncheck Shipping Via and check "United Package": see 1-1.png, 1-2.png)
2. Remove the filter but the displaying order look different than the default displaying order.
(Check Shipping Via: see 2.png)
Select filter for version 4 was restored the default dsiplaying order by removing filters by the way.
13
Help for ParamQuery Pro / Re: Unexpected behaviors when upgrading to v5.4.0 from v4.0.3
« on: November 28, 2018, 07:43:14 am »
We updated to v5.6 but the grid doesn't work correctly.
The following error will occur on the line 3 in pq-localize-pt-br.js when it's initialized.
Can you take a look into this? Would it be addressed shortly?
The following error will occur on the line 3 in pq-localize-pt-br.js when it's initialized.
Code: [Select]
pq.pqGrid.regional.pt-br = {
It seems like syntax error occurs because we cannot use hyphen(-) in variable names.Can you take a look into this? Would it be addressed shortly?
14
Help for ParamQuery Pro / Re: Unexpected behaviors when upgrading to v5.4.0 from v4.0.3
« on: October 25, 2018, 06:51:58 am »
Thank you very much. It worked in pager!
Would the localization of filters be addressed in the upcoming versions?
Would the localization of filters be addressed in the upcoming versions?
15
Help for ParamQuery Pro / Re: Unexpected behaviors when upgrading to v5.4.0 from v4.0.3
« on: October 24, 2018, 08:29:17 am »
Thank you very much for your response.
We will try to use resfresh() instead.
We will try to use resfresh() instead.
Pages: [1] 2