1. Peter Piechutzki
  2. PowerBuilder
  3. Tuesday, 14 April 2020 10:44 AM UTC

Hi,

I stumbled across a disturbing bug or maybe feature in the PB IDE.


If a user definded object 'u_dw' derived from standard datawindow is on a standard class window and named 'dw_1' a System Tree search  for 'u_dw' will report a match found on the window
.
If the same user defined object 'u_dw' derived from standard datawindow is on a standard class window and named 'dw_auf' a System Tree search for 'u_dw' will report 0 matches

Staying with standard class it is veriy eaasy to reproduce:

If a standard commandbutton placed on a standard window and named 'cb_test' a system tree search for 'commandbutton' will report the window

If a standard commandbutton placed on a standard window and named 'cb_auf' a system tree search for 'commandbutton' will report 0 result matches.

Is this a Bug or some sort of feature omitting all Objects containing 'auf' in their name from search???


Appeon Powerbuilder Standard Edition Version 2019 Build 2170  

To Reproduce:
Create new Workspace
Create new Application

Create new Window w_test1
Place commandbutton on window w_test1
Name commandbutton cb_test
Save Window w_test1

Create new Window w_test2
Place commandbutton on window w_test2
Name commandbutton cb_auf
Save Window w_test2

Perform search on System Tree for 'commandbutton' (without the quotes!)

Search only finds w_test1 but doesn't find w_test2

Any Ideas?

Miguel Leeuwe Accepted Answer Pending Moderation
  1. Tuesday, 14 April 2020 12:57 PM UTC
  2. PowerBuilder
  3. # 1

This also happens in PB12.6 by the way

and pb 2019 R2 ...

So 12.6, 2017 x, 2019 x

Comment
  1. Mark Lee @Appeon
  2. Wednesday, 15 April 2020 08:42 AM UTC
Hi Miguel,



Thanks for reporting this problem.

We can reproduce it on our side in PB 12.6, PB 2017 and PB 2019.

We will need some time to figure it out and will keep you updated.



Regards,
  1. Helpful
There are no comments made yet.
Peter Piechutzki Accepted Answer Pending Moderation
  1. Tuesday, 14 April 2020 12:30 PM UTC
  2. PowerBuilder
  3. # 2

even more 'WOW' from me,

i've tried all kinds of conbinations but did'nt realise it hast to do solely with the letter F or f.

As a side effect, after more than 20 years of pb development I just realised that PB converts Names of Objects on Windows to Lowercase.

 

Comment
  1. Miguel Leeuwe
  2. Tuesday, 14 April 2020 12:35 PM UTC
I mean ... I've never noticed this bug before. As far as pb converting uppercase to lowercase in object names, yes I did and I think that's a good thing when writing generic code. (Avoids you having to do upper() or lower() everywhere when checking for object names).
  1. Helpful
  1. Peter Piechutzki
  2. Tuesday, 14 April 2020 12:41 PM UTC
I agree fulle to the upper/lowercase and thanks for the bug report.
  1. Helpful
  1. Miguel Leeuwe
  2. Tuesday, 14 April 2020 12:56 PM UTC
Forget about what I said about not finding ANY window when using cb_ff instead of cb_f. It seems I cannot reproduce that case any m ore :(
  1. Helpful
There are no comments made yet.
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Tuesday, 14 April 2020 11:32 AM UTC
  2. PowerBuilder
  3. # 3

One word: WOW  !

I've done the test with the 2 windows and commandbuttons.

I've name one of the buttons: cb_f and it's not being found! (the other button on the other window is found)

I've renamed that button to cb_ff and then the OTHER button isn't found either.

So my guess is that it has to do with having an 'f' in the name of the button.

This is definitely a bug.

Comment
  1. Miguel Leeuwe
  2. Tuesday, 14 April 2020 11:35 AM UTC
I've renamed the button to cb_mybutton, all okay. I've then renamed to cb_mybuttonf and Not OK.

The same thing happens in PB 2017 R3 and it also happens when doing a search from the library painter.

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