1. Hugo Moors
  2. PowerBuilder
  3. Wednesday, 9 November 2022 08:47 AM UTC

I have a userobject that is used on a window and can't open this object in the IDE because PB says an ancestor or descendant is already open.

I have no windows open in PB the only way to open that object is to close the IDE and open it again.

 

I don't have a consistent way to reproduce this yet and don't have time at the moment to investigate but this seems to come more when debugging and either the application giving an error on that window or stopping the debugger when stepping through code on that window and returning to the IDE.

 

PB 2022 Build 1878

 

Olan Knight Accepted Answer Pending Moderation
  1. Thursday, 10 November 2022 22:44 PM UTC
  2. PowerBuilder
  3. # 1

One more thing:  Occasionally no matter how many times you reboot the PowerBuider IDE the wierd issue just will not go away.
Fine.

Shut down all apps.
Run a cleaner on the platform if you have one (CCleaner, for example.)
Reboot the platform (PC or VM).

I have found that in most instances the bizarre issue goes away after the platform has been rebooted.

Comment
There are no comments made yet.
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Wednesday, 9 November 2022 15:53 PM UTC
  2. PowerBuilder
  3. # 2

Shot in the dark:

Optimize every PBL and do a full rebuild?

Comment
  1. Olan Knight
  2. Thursday, 10 November 2022 22:41 PM UTC
That never hurts and often will fix bizarre issues like this one.

  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 9 November 2022 12:55 PM UTC
  2. PowerBuilder
  3. # 3

Hi Hugo & Ben;

   FWIW:  I use the PB IDE every day in a combination of Apps, Test Cases, Ticket recreation & my own STD Framework. I can honestly say that I have not encountered any of these issues. I use real W10/W11 based machines with AMD CPUs & 12-16G of memory each.

   PS: I also use the debugger a lot. That also now includes the remote debugger for PC/PS Apps in PB 2022 as well (no issues). Of course, instability can be forced by A) Exiting the debugger without pressing the "Stop Debug" toolbar icon first or B) Debugging complex logic in the Activate/Deactivate or GetFocus/Losefocus events where you disturb the event by creating a loop back as the Debugger acquires access and introduces a Get/Lose event recursion. BTW: These are long time known & documented "Gotchas" around the debugger use.

HTH

Regards ... Chris 

Comment
  1. Roland Smith
  2. Wednesday, 9 November 2022 15:14 PM UTC
I had this happen once. I don't remember what version it was.
  1. Helpful 1
There are no comments made yet.
Benjamin Gaesslein Accepted Answer Pending Moderation
  1. Wednesday, 9 November 2022 12:18 PM UTC
  2. PowerBuilder
  3. # 4

General instability after the debugger terminates abnormally has been a staple of PB ever since I can remember. I would advise to always restart the IDE after the debugger was stopped manually or due to some error. Another symptom of this is that sometimes objects won't save after editing but there won't be an error message either and work will be lost.

Comment
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.