1. Monica Petersen
  2. PowerServer Web
  3. Saturday, 03 November 2018

I have an n-up datawindow with 10 columns (the client wants to emulate a spreadsheet their field staff are using).  The first row has additional fields that apply to all subsequent rows.  To save space, I added expressions to the fields to move them up when getrow() > 10.

When running it in the development IDE, clicking the mouse correctly positions on the field that was clicked, even if it's been shifted up.

When the same application is deployed to the web, clicking works for fields in the first row, that haven't been repositioned.  But for fields that are repositioned, the click event places you on the field above, which was actually the field that used to be in that location.

Also, I was hoping to compress the detail band for the rows I shifted up, but it didn't work in the development environment or on the web app.  Perhaps that feature's not applicable for n-up reports?  It doesn't work even in the simplest case, when there isn't any repositioning.

mike S Accepted Answer Pending Moderation
0
Votes
Undo

even as a display (reporting) only datawindow, mouse events are needed and we must know what was clicked.  

Reporting systems should offer drilldown, and without a mouse event this is not possible.

Also, security and customization processing requires mouse events and correct clicked information

Comment
There are no comments made yet.
  1. Sunday, 4 November 2018
  2. PowerServer Web
  3. # 1
Olan Knight Accepted Answer Pending Moderation
0
Votes
Undo

If there's not a better way to solve this, here's a workaround.

1. Create an instance variable:  boolean    ib_called_from_pointer

2. At the top of the Clicked() event:
         IF (NOT (ib_called_from_pointer)) THEN RETURN 1

        

         ib_called_from_pointer = FALSE

         RETURN

3. At the top of the RBUTTONDOWN() event
         ib_called_from_pointer = TRUE

        

 

 

Good Luck,

Olan

Comment
Thanks for the suggestion Olan. I've taken all the expressions off the fields and its working much better. There was no point in shifting the fields up if autosize wasn't going to compress the row anyways.
  1. Monica Petersen
  2. Saturday, 3 November 2018
There are no comments made yet.
  1. Saturday, 3 November 2018
  2. PowerServer Web
  3. # 2
Chris Pollach Accepted Answer Pending Moderation
0
Votes
Undo

Hi Monica;

   N-UP DWs as you correctly point out are for "reporting". Also, once you add shifting up / left and auto-size height to any DWO - you are definitely into a "report only" use. So in these cases, there should be no allowed mouse or keyboard entry interaction, as these DWO's now are for "display only". Trying to interact with these DWO's with a mouse or any input device will be unpredictable (native or web).

Regards ... Chris

Comment
Thanks, good to know. Having said that, the n-up datawindow actually works quite well for emulating a spread sheet, as long as I keep it simple. And it makes the client happy, so who am I to question :)
  1. Monica Petersen
  2. Saturday, 3 November 2018
There are no comments made yet.
  1. Saturday, 3 November 2018
  2. PowerServer Web
  3. # 3
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.