1
Bug Report / Re: Full screen preview of a detail row's element not works
« on: October 23, 2017, 01:31:54 pm »
ok! it works
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 / Double request on load restore saved settings
« on: October 20, 2017, 02:29:05 pm »
Hi again,
I found the references to save and load grid's state at this page: https://paramquery.com/pro/demos33/grid_state
I'm going to explain the problem.
I've a table with REMOTE data and REMOTE paging and I need to save its settings and restore them when the table appear. So it's like the demo (link) but with remote paging so this:
create: function () {
//restore state of grid.
loadStateSuccess = this.loadState({ refresh: false });
},
will become:
create: function () {
//restore state of grid.
loadStateSuccess = this.loadState({ refresh: true});
},
I saw that the library apply the settings after the first call with that conseguences:
- the backend will receve the uncorrect request and the correct one so increase the BE side's work.
- If the response arrive fast I can see for an instant the uncorrect data before the new data (and correct) arrives.
- the user will have a bad experience of our product
We have Paramquery Pro v.3.3.5.
I found the references to save and load grid's state at this page: https://paramquery.com/pro/demos33/grid_state
I'm going to explain the problem.
I've a table with REMOTE data and REMOTE paging and I need to save its settings and restore them when the table appear. So it's like the demo (link) but with remote paging so this:
create: function () {
//restore state of grid.
loadStateSuccess = this.loadState({ refresh: false });
},
will become:
create: function () {
//restore state of grid.
loadStateSuccess = this.loadState({ refresh: true});
},
I saw that the library apply the settings after the first call with that conseguences:
- the backend will receve the uncorrect request and the correct one so increase the BE side's work.
- If the response arrive fast I can see for an instant the uncorrect data before the new data (and correct) arrives.
- the user will have a bad experience of our product
We have Paramquery Pro v.3.3.5.
3
Bug Report / Re: Full screen preview of a detail row's element not works
« on: October 20, 2017, 01:55:49 pm »
Any news in this front?
We need to have a solution because we must release the new version of the product next week!!
We need to have a solution because we must release the new version of the product next week!!
4
Bug Report / Re: Full screen preview of a detail row's element not works
« on: October 16, 2017, 01:21:12 pm »
http://jsfiddle.net/pztgcy2q/1/
Here there is a simple example...you have to run it on Google Chrome, expand a row and click the text inside the detail.
Here there is a simple example...you have to run it on Google Chrome, expand a row and click the text inside the detail.
5
Bug Report / Full screen preview of a detail row's element not works
« on: October 13, 2017, 07:19:10 pm »
Every time that I invoke the fullscreen of an element inside a detail row, the table refresh itself and the preview will close!
For the fullscreen mode in chrome you have to run for example :
document.querySelector('.detail').webkitRequestFullscreen()
where document.querySelector('.detail') is the element to expand.
for more info about Fullscreen see here: https://developer.mozilla.org/en-US/docs/Web/API/Fullscreen_API
For the fullscreen mode in chrome you have to run for example :
document.querySelector('.detail').webkitRequestFullscreen()
where document.querySelector('.detail') is the element to expand.
for more info about Fullscreen see here: https://developer.mozilla.org/en-US/docs/Web/API/Fullscreen_API
6
Bug Report / Re: Rendering not correct for paramquery pro 3.3.5
« on: October 13, 2017, 07:05:51 pm »
This works good!!!
Thanks
Thanks
7
Bug Report / Re: Rendering not correct for paramquery pro 3.3.5
« on: October 12, 2017, 06:34:12 pm »
Okay, that's exactly what I was talking about.
Yes, refresh the view on change rPP wil be a workaround, but only in one scenario!
for example...
On page init the scrollbar there isn't. When a big collection of data arrives (for example if the user has saved rPP=100) fires the render and after the page scrollbar appear...so, the user will see the problem always
Yes, refresh the view on change rPP wil be a workaround, but only in one scenario!
for example...
On page init the scrollbar there isn't. When a big collection of data arrives (for example if the user has saved rPP=100) fires the render and after the page scrollbar appear...so, the user will see the problem always
8
Bug Report / Re: Rendering not correct for paramquery pro 3.3.5
« on: October 10, 2017, 12:51:20 pm »
Yes Sorry,
first of all, with https://paramquery.com/pro/demos33/paging_local it's the same! So you have to use this one!
The problem there is switching from 1 to 100 and also from 100 to 1...I think it's the same problem!
The problem its depentent to the appear of the page scrollbar after table rendering...the table container resize its width but will be not the same for its columns!
If you proceed with the 5 steps you can reproduce the problem!
NOTE: Its important that the page has not a scrollbar on init!! (lets try to remove any some new line space in the code)
first of all, with https://paramquery.com/pro/demos33/paging_local it's the same! So you have to use this one!
The problem there is switching from 1 to 100 and also from 100 to 1...I think it's the same problem!
The problem its depentent to the appear of the page scrollbar after table rendering...the table container resize its width but will be not the same for its columns!
If you proceed with the 5 steps you can reproduce the problem!
NOTE: Its important that the page has not a scrollbar on init!! (lets try to remove any some new line space in the code)
9
Bug Report / Re: Rendering not correct for paramquery pro 3.3.5
« on: October 09, 2017, 12:12:06 pm »
Could you a accept the attachment in the last comment?
10
Bug Report / Re: Rendering not correct for paramquery pro 3.3.5
« on: October 06, 2017, 01:46:40 pm »
I've replicated the problem in a paramquery's demo page.
1) You have to open this demo: https://paramquery.com/pro/demos32/paging_local
2) Paste this code inside the Javascrip editable section
3) Resize the page while its scrollbar disappear (resizing page or changing element height from developer console)
4) Click edit and run
5) execute the action steps to reproduce the error
thanks
1) You have to open this demo: https://paramquery.com/pro/demos32/paging_local
2) Paste this code inside the Javascrip editable section
3) Resize the page while its scrollbar disappear (resizing page or changing element height from developer console)
4) Click edit and run
5) execute the action steps to reproduce the error
thanks
11
Bug Report / Re: Rendering not correct for paramquery pro 3.3.5
« on: October 06, 2017, 12:52:50 pm »
Maybe I explained wrong.
The table must be with auto width and flex height and the page must have not scrollbar. When the page increases in height and the page's scrollbar will appear by overflow (for example changing rPP or expanding a row), you can see the rendering problem.
Another problem will appear if you resize the window (to adjust the table render), and then reduce the page height to hide the scrollbar (for example changing rPP or unexpanding a row).
I'll share an example of the issue as soon as possible.
The table must be with auto width and flex height and the page must have not scrollbar. When the page increases in height and the page's scrollbar will appear by overflow (for example changing rPP or expanding a row), you can see the rendering problem.
Another problem will appear if you resize the window (to adjust the table render), and then reduce the page height to hide the scrollbar (for example changing rPP or unexpanding a row).
I'll share an example of the issue as soon as possible.
12
Bug Report / Re: Rendering not correct for paramquery pro 3.3.5
« on: October 04, 2017, 08:56:48 pm »
I have uploaded one more here.
Yes, I've setted up those parameters but it doesn't works.
Yes, I've setted up those parameters but it doesn't works.
13
Bug Report / Rendering not correct for paramquery pro 3.3.5
« on: October 03, 2017, 01:17:38 pm »
I have a table in a empty page (no scrollbar initially).
Here, there is a table that show more than 100 rows (so will appear the scrollbar in the page).
When the datas arrives (remote dataModel) last column in the table will partially covered.
If I'll resize the page, the table rendering correctly, but if I'm going to change rPP (for example 10 rows -> no scrollbar) the table show the table background after the last column.
See the posted images
Here, there is a table that show more than 100 rows (so will appear the scrollbar in the page).
When the datas arrives (remote dataModel) last column in the table will partially covered.
If I'll resize the page, the table rendering correctly, but if I'm going to change rPP (for example 10 rows -> no scrollbar) the table show the table background after the last column.
See the posted images
14
Help for ParamQuery Pro / Re: Grouping formatted dates with paramquery pro 3.3.5
« on: October 03, 2017, 12:26:38 pm »
Thank U!
This will be the corrective way (but not correct)...So I've used titleDefault option because the date group can be in any position..
This will be the corrective way (but not correct)...So I've used titleDefault option because the date group can be in any position..
15
Help for ParamQuery Pro / Grouping formatted dates with paramquery pro 3.3.5
« on: October 02, 2017, 09:01:55 pm »
Referring to this example: https://paramquery.com/pro/demos/group_rows
I have to group rows by shipping date columns, but the dates must be formatted...so, add in the date column the italian format (it's an example).
The shipping date column going to be like this:
{ title: "Shipped Date", width: 100, dataIndx: "ShippedDate", dataType: "date", format: "dd/mm/yy" }
When I group by this column I will see the group date isn't formatted like rows...It's a bug or there is a configuration that resolve this problem?
I have to group rows by shipping date columns, but the dates must be formatted...so, add in the date column the italian format (it's an example).
The shipping date column going to be like this:
{ title: "Shipped Date", width: 100, dataIndx: "ShippedDate", dataType: "date", format: "dd/mm/yy" }
When I group by this column I will see the group date isn't formatted like rows...It's a bug or there is a configuration that resolve this problem?
Pages: [1] 2