Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (1)

Resolved Datawindow Zoom causing RowFocuschanging

  1. Issue
1
Votes
Undo
  1. David Vasconcelos
    David Vasconcelos
  2. PowerBuilder
  3. Thursday, 27 August 2020 13:07 PM UTC

I am adding appeon resize service to our application and notice that when Zoom is changed on the datawindow it fires off rowfocuschanging event and set the datawindow back to row 1.  I also tested this just by directly changing the zoom on the datawindow and sure enough the rowfocuschanging event fired off and set my dw back to row 1.  Is this a bug or normal behavior for zoom?  (Because of this I now need to keep track or detect resize is occuring and make sure the row does not change.)

 

Env.  PB 2017 R3, Windows 64 bit.

Google API access Token using JSON Private Key
Cannot use an OUTPUT option when passing a constan...
Accepted Answer
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 27 August 2020 15:32 PM UTC
  2. PowerBuilder
  3. # Permalink

Hi David;

  This behaviour was the same back in the PB 12.x releases as well. I compensated for this in my framework by ...

Ib_zooming = true

This.SetReDraw(false)

ll_row = This.GetRow()

// Zoom logic

This.SetRow(ll_row)

Ib_zooming = false

This.SetReDraw(true)

   Note that in the RowFocusChanging event, do not perform any action if ib_zooming = true.

HTH

Regards ... Chris

 

Comment
Load more comments
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 27 August 2020 19:54 PM UTC
FWIW: feel free as well to create a Support Ticket for this improper behaviour too. I was just giving you one possible workaround for now.
  1. Helpful
James Levin
  1. James Levin
  2. Tuesday, 14 March 2023 19:52 PM UTC
This still is an issue in PB 2022
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 14 March 2023 20:10 PM UTC
Hi James;

FYI: Looks like this issue was logged in ticket # 4528. In looking at that ticket, the ticket system still does not reflect that this issue was fixed. Thus, I suspect that the issue is still there in PB 2022 build 1892.

Regards ... Chris
  1. Helpful
There are no comments made yet.
Responses (1)


There are replies in this question but you are not allowed to view the replies from this question.