Recent Posts

Pages: [1] 2 3 ... 10
1
Help for ParamQuery Pro / Re: Column filter on remote source override
« Last post by paramvir on July 14, 2025, 03:27:05 pm »
beforeFilter event can be used to hook into filter for specific column(s). return false in this event cancels the remote filter request.

Code: [Select]
beforeFilter: (evt, ui)=>{
if(ui.rules.find(rule=> rule.dataIndx == 'ShipCountry')){
                //do your thing..
return false; //cancel filtering.
}
},
2
Help for ParamQuery Pro / Column filter on remote source override
« Last post by jplevene on July 13, 2025, 07:46:19 pm »
I have a grid with multiple columns and different filter options that uses a remote data source.

One column filter (being a range drop down grid), when options are selected, I don't want to trigger a reload or even a filter, I want to call my own function that does it's own thing, does NOT request data to loaded remotely, that has nothing to do with the grid and does not affect the grid.

Is this possible and how can I do it?
3
ParamQuery Pro Evaluation Support / Re: ParamQuery Pro is not EAA compliant
« Last post by datapa on July 10, 2025, 01:40:20 pm »
Many thanks, we look forward to the release.
4
ParamQuery Pro Evaluation Support / Re: ParamQuery Pro is not EAA compliant
« Last post by paramvir on July 09, 2025, 06:13:27 pm »
Thank you for bringing this to our attention. We appreciate your commitment to accessibility and for highlighting the importance of the EAA and WCAG 2.2 compliance.

We are currently working toward ensuring compliance with the European Accessibility Act and plan to implement necessary updates by Aug / Sept 2025.

Your feedback is invaluable in helping us align with both legal standards and user needs.
5
ParamQuery Pro Evaluation Support / ParamQuery Pro is not EAA compliant
« Last post by datapa on July 03, 2025, 07:31:57 pm »
Hi,

As you may be aware, the European Accessibility Act (EAA) came in to force at the end of June.  Any web application used in the EU must comply.

We use ParamQuery Pro, and need it to comply with the EAA, which is now a legal requirement.

Indeed, you are now legally obliged to comply with EAA to sell to EU customers.

In order to comply with the EAA, you need to adhere to WCAG 2.2 AA standards.  Quick checks with tools such as Lighthouse and Accessibility Isights for Web  indicate that you do not yet. 

Please can you confirm your intention to comply with the EAA and the timescale for this?

Regards,

Paul
inmydata.com
6
If the checkbox is embedded within a grid cell, toggling its state should update the underlying data model—this, in turn, should enable the Save Changes button.

You can see this behavior in action in the following example: https://paramquery.com/pro/demos/editing_batch

It’s possible that in your implementation, the checkbox isn’t properly data-bound, which would prevent the grid from detecting the change.
7
@paramvir, its my client requirement, when we check the checkbox then savechanges button should enable, is there any way to enable savechanges button please suggest.

Thanks
Srinivasarao p
8
Though it doesn't make sense why would you do that.

you can enable save button by getting DOM reference to it and calling disabled false.

Code: [Select]
$( selector of save button ).button("option", "disabled", false );
9
This patch can be used to fix the issue.

Code: [Select]
var p=jQuery.paramquery.cDragColumns.prototype;jQuery.paramquery.cDragColumns=function(e){var r,o,t=this,a=e.options,n=a.dragColumns||{},d=function(r,o){return $("<div class='pq-arrow-"+r+" ui-icon "+o+"'></div>").appendTo(e.$grid_center)};t.that=e,t.rtl=a.rtl,t.status="stop",t.$arrowTop=d("down",n.topIcon),t.$arrowBottom=d("up",n.bottomIcon),t.hideArrows(),n.enabled&&e.$head_i.draggable({distance:5,cursorAt:{top:-10,left:-10},cancel:".pq-grid-header-search-row,input,textarea,button,select,option,.pq-grid-number-cell",zIndex:"1000",appendTo:"body",revert:t.revert.bind(t),helper:function(o,a){var n=o.target.closest(".pq-grid-col");if(n){var d,c=t.colIndicesDrag=e.getHeadIndices(n),i=t.columnDrag=c.column,l=i.parent,p=e.options.dragColumns.rejectIcon,s=e.getScale();return r=pq.getScale(document.body),!i||i.nodrag||i._nodrag||l&&1==l.colSpan||i.empty||!1===e._trigger("columnDrag",o,{column:i})?"<span/>":(e.$head_i.find(".pq-grid-col-resize-handle").hide(),(d=t.$helper=$("<div class='pq-col-drag-helper pq-theme pq-grid-cell' data-di="+i.dataIndx+" ><div><span class='pq-drag-icon ui-icon "+p+"'></span>"+i.pq_title+"</div></div>")).css({scale:s[0]/r[0]+" "+s[1]/r[1]}),d[0])}return $("<div></div>")},start:function(){},drag:function(a,n){if(t.$helper){t.status="drag";var d,c=n.position,i=a.originalEvent,l=(i&&i.target!=document?i.target:a.target).closest(".pq-grid-col"),p=t.colIndicesDrag,s=p.ri,g=p.column,u=g.leftPos,h=u+g.o_colspan;if(c.left=c.left/r[0],c.top=c.top/r[1],console.log("cDragColumn.js td = ",l),l&&!l.closest(".pq-grid-header-search-row")&&e.evtBelongs(i)){var m=e.getHeadIndices(l),v=m.column,f=m.ri,q=m.colIndx;if(!(v.empty||v==g||v.nodrop||v._nodrop||s<f&&q>=u&&q<h))return o=l,t.colIndicesDrop=m,void t.onDrag(a,l);o!=l&&t.updateDragHelper(!1),o=l}else t.hideArrows(),d=$(".ui-droppable-hover",e.$top),console.log("cGroup.js $group = ",d[0]),t.updateDragHelper(!!d[0]);t.colIndicesDrop=null}},stop:function(r){if(t.status="stop",t.$helper){t.hideArrows();var o=t.colIndicesDrop;e.$head_i.find(".pq-grid-col-resize-handle").show(),o&&t.onDrop(t.colIndicesDrag,o,r)}}})},jQuery.paramquery.cDragColumns.prototype=p;
10
There is a problem in the way you have made changes in rowData directly and passed updated rowData to newRow parameter of updateRow method.

Code: [Select]
activeGrid.updateRow({
                rowIndx: ui.rowIndx,
                newRow: rowData, //pass new object here instead of rowData, and don't make any changes in rowData
                track: true,
                history: false,
                checkEditable: false,
                refresh: false
            });


newRow is supposed to be a new object containing only the changes in the fields you want.
Pages: [1] 2 3 ... 10