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

Resolved Application close event not firing when run from PB or in Debugger

  1. Issue
0
Votes
Undo
  1. Daniel Vivier
    Daniel Vivier
  2. PowerBuilder
  3. Monday, 28 September 2020 17:03 PM UTC

In one of my two main applications, the application Close event never fires if I run it from within PB or in the debugger. It fires in the compiled (pcode) version. Almost identical code also works everywhere (in PB, debugger, or compiled) in the other application.

I put a breakpoint on the first line of code in the Close event, ran the app, exited the main window, and it just returned right back to the debugger. So it's not as if the application hasn't terminated. The Close event also fires if I do HALT CLOSE.

This is in PB2019 Build 2082.

Any bright ideas? Thanks.

  1. PowerBuilder (Appeon)
DATAWINDOW SAVEAS XLSX FORMAT
Columns in Datawindow loses original position afte...
Responses (3)
David Peace (Powersoft)
David Peace (Powersoft) Accepted Answer Pending Moderation
  1. Friday, 12 March 2021 13:57 PM UTC
  2. PowerBuilder
  3. # 1

Hi Dan

I'm seeing the same problem running in the IDE PB2019R3 Build 2670.

Did you every resolve your issue?

Cheers

David

 

Comment
Daniel Vivier
  1. Daniel Vivier
  2. Friday, 12 March 2021 14:09 PM UTC
Not resolved as far as I am aware. Thanks, David.
  1. Helpful
David Peace (Powersoft)
  1. David Peace (Powersoft)
  2. Friday, 12 March 2021 15:13 PM UTC
I started looking a bit deeper into the problem, put debugbreak at the end of the window close event. Then stepped from there and it went into the application close event. Very strange.



I then got distracted looking at another workspace and when I came back to the original one the problem was resolved. Go figure?



So in conclusion it was something flakey, which is what Chris was saying before.



I trust you are keeping well and busy :)



Cheers

David
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 28 September 2020 21:02 PM UTC
  2. PowerBuilder
  3. # 2

Hi Dan;

   Object Browser hierarchy regeneration ...

  1. Open Object Browser and Select the "Window" Class
  2. RHMB and then choose "Show Hierarchy".
  3. RHMB and then choose "Expand All".
  4. RHMB on Top ancestor and then choose "Regenerate".

HTH

Regards ... Chris

 

Comment
Daniel Vivier
  1. Daniel Vivier
  2. Monday, 28 September 2020 21:06 PM UTC
Nope, it doesn't help, but thanks.
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 28 September 2020 21:16 PM UTC
Hmmm ... it could be corrupt source code.

Did you try build 2170?
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 28 September 2020 20:08 PM UTC
  2. PowerBuilder
  3. # 3

H Dan;

  I very seldom get that issue but when I do, its normally related to making some changes in my higher up ancestors that the odd time then affects an event not firing. However, after a Full Build or better yet, a FUll System Tree regeneration in the Object Browser fixes this oddity.

  I also see that you are on an older build of PB 2019. I would highly recommend moving up to build 2170 for PB 2019 (December 2019) if your not ready for upgrading to 2019 R2 yet.

HTH

Regards ... Chris

Comment
Daniel Vivier
  1. Daniel Vivier
  2. Monday, 28 September 2020 20:43 PM UTC
Chris I already did a Full Build. What is a Full System Tree regeneration in the Object Browser? I didn't see a way to do that at all.



This problem happens even if I put "return" as the first line of the application object's Open script - it still doesn't stop at the first line of the Close script in the debugger! So it's kind of hard to see about any sort of inheritance issues etc. could be relevant.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.