Skip to main content

Bug or Feature: UXCROSS and handle

Author: i2stiller@gmx.de (istiller)

Hi Just doing some coding with handles and the "->" operator. After compiling a did a look into UXCROSS and didn't find the expected information 1.  $handle$->hello()  UREFTYP  = "HND"  UREFFLD  is empty (NULL)  UREFENT  = "hello" 2.  $handle$->"hello"()  No entry at all   There is no clue, which (global) variable is involved. When using variable names like $HND_COMPNAME$, one could extract the name of the called component (or an "interface") And as the second example shows, with a string there is no clue at all. Yes, you need this kind of activate if you do have a variable operation name like $handle$->"%%$OPERNAME$%%%"() So, it this a bug or a feature? Ingo

Bug or Feature: UXCROSS and handle

Author: i2stiller@gmx.de (istiller)

Hi Just doing some coding with handles and the "->" operator. After compiling a did a look into UXCROSS and didn't find the expected information 1.  $handle$->hello()  UREFTYP  = "HND"  UREFFLD  is empty (NULL)  UREFENT  = "hello" 2.  $handle$->"hello"()  No entry at all   There is no clue, which (global) variable is involved. When using variable names like $HND_COMPNAME$, one could extract the name of the called component (or an "interface") And as the second example shows, with a string there is no clue at all. Yes, you need this kind of activate if you do have a variable operation name like $handle$->"%%$OPERNAME$%%%"() So, it this a bug or a feature? Ingo

istiller said And if it is allready logged, why isn't there a solution by now :-)

It seems that you've agreed that this problem is not that important. So the chances are not very high that this will be picked up any time soon. Sorry, but it's all about priorities. Daniel


Author: diseli (daniel.iseli@uniface.com)

Bug or Feature: UXCROSS and handle

Author: i2stiller@gmx.de (istiller)

Hi Just doing some coding with handles and the "->" operator. After compiling a did a look into UXCROSS and didn't find the expected information 1.  $handle$->hello()  UREFTYP  = "HND"  UREFFLD  is empty (NULL)  UREFENT  = "hello" 2.  $handle$->"hello"()  No entry at all   There is no clue, which (global) variable is involved. When using variable names like $HND_COMPNAME$, one could extract the name of the called component (or an "interface") And as the second example shows, with a string there is no clue at all. Yes, you need this kind of activate if you do have a variable operation name like $handle$->"%%$OPERNAME$%%%"() So, it this a bug or a feature? Ingo

Hi Ingo, I believe this issue already has been recognized as BUG#31199 - Cross reference does not generate any information for "calls" by handle. Currently this is just a low priority item on the maintenance backlog (so there is no planning for a fix yet). And if I'm not mistaken then this problem was reported by you. Hope this helps. Daniel


Author: diseli (daniel.iseli@uniface.com)

Bug or Feature: UXCROSS and handle

Author: i2stiller@gmx.de (istiller)

Hi Just doing some coding with handles and the "->" operator. After compiling a did a look into UXCROSS and didn't find the expected information 1.  $handle$->hello()  UREFTYP  = "HND"  UREFFLD  is empty (NULL)  UREFENT  = "hello" 2.  $handle$->"hello"()  No entry at all   There is no clue, which (global) variable is involved. When using variable names like $HND_COMPNAME$, one could extract the name of the called component (or an "interface") And as the second example shows, with a string there is no clue at all. Yes, you need this kind of activate if you do have a variable operation name like $handle$->"%%$OPERNAME$%%%"() So, it this a bug or a feature? Ingo

diseli said Hi Ingo, I believe this issue already has been recognized as BUG#31199 - Cross reference does not generate any information for "calls" by handle. Currently this is just a low priority item on the maintenance backlog (so there is no planning for a fix yet). And if I'm not mistaken then this problem was reported by you. Hope this helps. Daniel  

Hi Daniel I'm an old guy. I forget somtimes something. And if it is allready logged, why isn't there a solution by now :-) Ingo


Author: istiller (i2stiller@gmx.de)
Terms & ConditionsAccessibility statement