Skip to main content

$labelproperties

Author: i.sharp@pcisystems.co.uk (Iain Sharp)

I have recently been able to go back to a prototype which I had just about working under version 9.4, in 9.5 however, the $labelproperties function appears to behave differently., I have a repeating entity painted with a single button (non-database) with attached label (so the label is rendered 3d like the button). This allows for the display of as many buttons as I need. There is then a routine to populate these, which changes the glyph and label based on the action associated with this occurrence. In 9.4, using $labelproperties on a non-database button painted in repeating occurrences, allowed for different labels for each occurrence, in 9.5 it appears that it sets the label for all occurrences. Which is the correct behaviour? Should I be looking for a different way to do this, or for a fix to this introduced behaviour? Iain

$labelproperties

Author: i.sharp@pcisystems.co.uk (Iain Sharp)

I have recently been able to go back to a prototype which I had just about working under version 9.4, in 9.5 however, the $labelproperties function appears to behave differently., I have a repeating entity painted with a single button (non-database) with attached label (so the label is rendered 3d like the button). This allows for the display of as many buttons as I need. There is then a routine to populate these, which changes the glyph and label based on the action associated with this occurrence. In 9.4, using $labelproperties on a non-database button painted in repeating occurrences, allowed for different labels for each occurrence, in 9.5 it appears that it sets the label for all occurrences. Which is the correct behaviour? Should I be looking for a different way to do this, or for a fix to this introduced behaviour? Iain

Hi Iain, I think there was a problem with $labelproperties that not all occurences have been adressed and the lab has corrected this. It's a very fine feature for flexibility w/o abusing editboxes/unifields/maps/hyperlinks. Perhaps we should ask for a $fieldlabelproperties so it is clear what goes for all occurences and what is "this occurence only". P.S my math checker reads 10+12, so it seems to become more difficult


Author: ulrich-merkel (ulrichmerkel@web.de)

$labelproperties

Author: i.sharp@pcisystems.co.uk (Iain Sharp)

I have recently been able to go back to a prototype which I had just about working under version 9.4, in 9.5 however, the $labelproperties function appears to behave differently., I have a repeating entity painted with a single button (non-database) with attached label (so the label is rendered 3d like the button). This allows for the display of as many buttons as I need. There is then a routine to populate these, which changes the glyph and label based on the action associated with this occurrence. In 9.4, using $labelproperties on a non-database button painted in repeating occurrences, allowed for different labels for each occurrence, in 9.5 it appears that it sets the label for all occurrences. Which is the correct behaviour? Should I be looking for a different way to do this, or for a fix to this introduced behaviour? Iain

Well, this is in the latest patch for 9.5. So if' they've fixed it so it does this, I've got to find another way of doing what I want to which involves editboxes or something and loses the ability to render the label as part of the button. If' this is an introduced problem, then I need to request a fix. Which is why I need to know what it's supposed to do. Either I wait for a fix, or I reprogram the whole thing to look worse and do more work. I therefore need a definitive answer before I proceed,


Author: Iain Sharp (i.sharp@pcisystems.co.uk)

$labelproperties

Author: i.sharp@pcisystems.co.uk (Iain Sharp)

I have recently been able to go back to a prototype which I had just about working under version 9.4, in 9.5 however, the $labelproperties function appears to behave differently., I have a repeating entity painted with a single button (non-database) with attached label (so the label is rendered 3d like the button). This allows for the display of as many buttons as I need. There is then a routine to populate these, which changes the glyph and label based on the action associated with this occurrence. In 9.4, using $labelproperties on a non-database button painted in repeating occurrences, allowed for different labels for each occurrence, in 9.5 it appears that it sets the label for all occurrences. Which is the correct behaviour? Should I be looking for a different way to do this, or for a fix to this introduced behaviour? Iain

Hi, If you can hold out till Uniface 9.6 your problem will be solved. Just paint a Uniface button and assign someting like @filename.png+!lsometext to the it. This will put both an icon and a text on the button. Regards, Theo Neeskens


Author: Theo Neeskens (tneeskens@itblockz.nl)
Terms & ConditionsAccessibility statement