1. Dave Haas
  2. PowerBuilder
  3. Friday, 22 May 2020 17:42 PM UTC

Hello All,

I have a window with tab control where each tab has a composite datawindow on it.  When I try to open window,  it takes so long to open....over 3 minutes some times.  I had noticed print spooler etc. was very busy and that the current printer was a network printer.  The hokey workaround I noticed was to change to a non-network printer like 'Sybase DataWindow PS', 'One Note' etc. I did this programically and then changed printer back when window is finshed opening...open time drops from 10-30 seconds.

I'm looking for a better solution instead of this workaround.

Has anyone seen this behavior?  Thanks in advance for any help!

Dave

Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 22 May 2020 18:39 PM UTC
  2. PowerBuilder
  3. # 1

Hi Dave;

  Wow ... 10-30 seconds is still along time to open any Window object! However with a Tab Control, each Tab Page has to instantiate and then instantiate its controls. Add to that DWO's retrieving and those DWO's firing Child DWO's and that can certainly "add up" to some lengthy instantiation / open wall clock time.  :-(

  Have you tried using the Tab Control's "CreateOnDemand" property option?

Regards ... Chris

 

Comment
  1. Dave Haas
  2. Friday, 22 May 2020 19:57 PM UTC
Hi Chris,



Than you for reply! This window with tab control has composites on each showing results/averages of data entered in another window with identical tab control (contents different in each). This data entry with same tabs in tab control opens within 10 seconds. So it appears to me that the common denominator is contents of tabs. The results that has composites opens slow while the data entry tabs window that doesn't have composites opens quick.



So it looks like composite DWs is issue. Changing the selected printer before opening this window makes the difference between opening in over 3 minutes and 10 -30 seconds (there's a lot of calculations going on so this is very acceptable to users)...this workaround is hokey
  1. Helpful
  1. Chris Pollach @Appeon
  2. Friday, 22 May 2020 20:15 PM UTC
Hi Dave ... Yes, each DW relies on the current "default" printer for the fonts needed to render the DWO in each DW Control or in the case of a composite, each parent window. In the end, what you see in the DW Control is a bitmap rendering of all the DWO's. However the font management used to render the DWO area can perform exponentially better or worse depending on the default printer. The best rendering performance would be from a local printer attached to an actual machine. The second best will be a network printer located on the same network segment.
  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.