Menu
Download Free Trial

Selection in Grid is not picking up location of mouse properly

I just tried upgrading from 2.3 to 2.402 and I am seeing a very strange behavior as is pertains to mouse selection within the grid. When I click in grid (no report loaded), say cell [r:1,c:1], the cell that is selected is cell [r:3,c:2].  When I click in the column header of a column the cell at r:2 of that column is selected, but ONLY if I select in the beginning portion of the column header.  If I select in the column header behind the label, the next column is selected (still 2nd row cell)

If I click on a row or column divider to resize it, the divider jumps down (row divider) or to the right (column divider) about 75-100px

It appears as though the location of mouse is being remapped to a different locations.  This makes the grid unusable.  I am using the default CSS file and don’t have any overrides of CSS in my files.  This was not an issue in 2.3

By the way, mouse movement and selection over the toolbar is working just fine

5 answers

Public
Tanya Gryshko Flexmonster September 7, 2017

Hello Dennis,
Thank you for writing. We have not managed to reproduce such mouse movement and selection issues on our side. Could you please share some JSFiddle sample demonstrating the issues? We would be grateful for your feedback.
Regards,
Tanya

Public
Dennis Urech September 7, 2017

If it helps, this is an integration with Angular (1.x), so I am creating the  Flexmonster component with the “fm-pivot” directive. 
 
My DIV containing the directive looks like this
 
 
    <div fm-pivot
         fm-width=”100%”
         fm-height=”100%”
         fm-toolbar=”true”
         fm-license-key=”{{flexmonsterLicenseKey}}”
         fm-ready=”onAlertFlexmonsterReady(pivot)”
         fm-before-toolbar-created=”customizeToolbar(toolbar)”
         id=”alertPivotContainer”>
      </div>
 
I’ll see what I can do about make a sample, but my time is limited.
 
I did add an event handler for “fm-cell-click” and it is reporting the correct row and column selection.  It is only the grid itself that that is showing the wrong selection

Public
Tanya Gryshko Flexmonster September 9, 2017

Hello Dennis,
Thank you for your reply. We have checked with Angular (1.x) and yet have not reproduced the issue. Could you please run this example from GitHub and confirm whether it works as expected?
Your feedback would be much appreciated.
Regards,
Tanya

Public
Dennis Urech September 11, 2017

Tanya,
Just ran it in JSFiddle and it works as expected IF you start with a defined report.  If you REMOVE the “fm-report=report” from the directive, and re-run it you will see strange behavior.  Not having a selected report is the state of our Flexmonster component, when the component is initially displayed. Any way. I am not seeing the exact same strange behavior that I see in my application, but similar.  Here is what I see (again, with no report defined)
 

  • Click over r1,c1 and r2,c1 is selected (if you select at the very top of a cell, then the cell is selected)
  • Click in header of column 3 (or any column) and instead of the entire column being selected, only the first cell on row 1 is selected
  • Click in the column header close to the right side (but before the cursor changes to the “move” column cursor) and the column to the right is selected, not the one the mouse id over.
  • When I attempt to resize a row and ‘grab’ the row divider to resize it, as I move it down just a bit, the row divider jumps down one full row height.  Resizing a column also has a similar jump, but not as pronounced.

 
Lastly, in addition to using Angular, we are also using the component library jQWidgets.  jQWidgets has Splitter component.  In our application, the Flexmonster component is displayed int the right panel of the ‘splitter’.  I don’t know if this affects anything, but it is an addition difference in our environment from a pure Angular only environment.  BTW, jQWidgets fully supports the Angular framework and this is the same environment & layout we are currently using with FLexmonster 2.3 which does not demonstrate these problems

As the name implies, jQWidgets, requires the use of jQuery.  Since you guys have removed that dependency, perhaps there is now some compatibility issues

Public
Tanya Gryshko Flexmonster September 13, 2017

Hello Dennis,
Thank you for all the details. It really helped us to reproduce the issue. The fix will be delivered as part of minor release 2.405, ETA Oct 9. Please let me know in case of further questions.
Regards,
Tanya

Please login or Register to Submit Answer