1. William Beale
  2. PowerBuilder
  3. Saturday, 10 April 2021 04:47 AM UTC

I've just migrated from PB 2019R2 to R3.  Now, the 'timer' from the status bar appears mid-screen.  The status bar works ok for MicroHelp.

I've looked at similar posted issues and the recommendations appear to setting the  is_classname[] variables to 'FNHELP' and 'FNFIXDBAR' in w_statusbar and w_toolbar windows, while another recommends changing is_classname[] in the n_cst_platform constructor event. 

But I do not have the is_classname variable in any of these object.  In that respect, my pfc library goes back to 1998. 

Any advice would be appreciated.

Accepted Answer
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Saturday, 10 April 2021 13:36 PM UTC
  2. PowerBuilder
  3. # Permalink

Hi William;

   This is a known issue and not only for PFC based applications. Appeon engineering is currently QA'ing an R3 maintenance release and this should be released in the next week or so. I am expecting that these positioning & resizing issues will be resolved for most applications by applying that MR.

Regards... Chris

 

 

 

 

Comment
  1. William Beale
  2. Saturday, 10 April 2021 22:59 PM UTC
Your feedback is appreciated.
  1. Helpful
  1. William Beale
  2. Sunday, 25 April 2021 01:53 AM UTC
Further to Chris' post, I've just installed the new R3 version and the problem was resolved - Thank you
  1. Helpful
  1. Chris Pollach @Appeon
  2. Monday, 26 April 2021 15:50 PM UTC
That is awesome news William .. thank you for letting us know! :-)
  1. Helpful
There are no comments made yet.
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Saturday, 10 April 2021 15:30 PM UTC
  2. PowerBuilder
  3. # 1

Since the timer is appearing centered, I think the problem is different than the one related to in previous Q&A.

Chris is probably 100% right on this one.

regards

Comment
There are no comments made yet.
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Saturday, 10 April 2021 15:26 PM UTC
  2. PowerBuilder
  3. # 2

Hi William, I think you are referring to this post?

https://community.appeon.com/index.php/qna/q-a/powerbuilder-2019r3-statbar-is-not-visible?limitstart=0#reply-25420

The values 'FNHELP' and 'FNFIXDBAR' aren't part of the pfc classes, they're defined in the w_toolbar window of the sampl app in the above link.

regards, hope it helps.

MiguelL

 

Comment
There are no comments made yet.
Arthur Hefti Accepted Answer Pending Moderation
  1. Saturday, 10 April 2021 14:22 PM UTC
  2. PowerBuilder
  3. # 3

Hi

doing a This.TriggerEvent( Resize! ) in the pfc_postopen event of the frame should position the statusbar on the bottom.

Regards
Arthur

Comment
  1. Miguel Leeuwe
  2. Saturday, 10 April 2021 15:14 PM UTC
Or do this in the pfc_open() event (so no flickering as the window isn't visible yet):

// the pfc_show will call the iw_statusbar.of_RefreshPosition()

if IsValid(inv_statusbar) then

this.inv_statusbar.event pfc_show()

end if



But someone said that didn't do the trick and what worked for him was:



Thanks, but that didn't fix it for me. I had to add this line in the frame OPEN event instead. Because the window wasn't open yet, pfc_show doesn't execute of_refreshposition. This line is normally executed from the pfc_postopen event of pfc_w_frame).



inv_statusbar.of_Open(True)



That fixed it for me.

Dean Helsley Friday, 5 February 2021 15:15 PM UTC



So I'm not sure why it worked for me, maybe a difference in PFC versions or PB version.

regards



  1. Helpful
  1. Miguel Leeuwe
  2. Saturday, 10 April 2021 15:28 PM UTC
Though, I have to correct myself, with you're method Arthur, there wouldn't be any flickering either, if you'd make the statusbar invisible (in the open() for example) before moving it in the pfc_postopen and then making it visible.

regards.
  1. Helpful
  1. Miguel Leeuwe
  2. Saturday, 10 April 2021 15:31 PM UTC
Correction: "before moving ..." should be "before resizing ...".
  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.