Our legacy application has a couple hundred references to backcolor in objects or bitmapbackcolor in menus set to 141454956. This isn't a legitimate RGB value, but I know in the past PB has had special values for special colors. This setting is currently causing the IDE to crash when opening some of the objects with this value set. Has anyone else experienced this issue? Now that I've discovered this, the fix/workaround seems to be fairly easy by editing the source, but wondering why this should be occurring now.
-
Jim Reese
- PowerBuilder
- Monday, 17 July 2023 16:18 PM UTC
Comment
- Miguel Leeuwe
- Monday, 17 July 2023 17:26 PM UTC
LOL, I don't know, what I do know is that PB is crashing quite a bit more lately. Used to be a lot stabler in PB 2017
- Roland Smith
- Monday, 17 July 2023 17:32 PM UTC
My guess is the number is too large and causing the variable in the C++ code to wrap around to negative which then causes an error calculating the RGB value.
- John Fauss
- Monday, 17 July 2023 18:29 PM UTC
The "special" colors that PB has names for (such as "ButtonFace", "WindowBackground" and "Transparent" all have non-zero bits in the high-order byte (above the encoded RGB value) of an unsignedlong color value, resulting in decimal values for these colors in excess of 16,777,215 (0x00FFFFFF), so there is not a restriction per se for a color value being too large.
Most (but not all) of the values of these named colors utilize 0x08 in the high-order byte, and 141454956 is 0x086e6e6c, which does not match any recognized named color, by the way.
My guess is that beginning in PB 2022, color values are now being validated at some point. If this is the case, however, an exception or other run-time error should be thrown instead of crashing the IDE/app.
Most (but not all) of the values of these named colors utilize 0x08 in the high-order byte, and 141454956 is 0x086e6e6c, which does not match any recognized named color, by the way.
My guess is that beginning in PB 2022, color values are now being validated at some point. If this is the case, however, an exception or other run-time error should be thrown instead of crashing the IDE/app.
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.
However, you are not allowed to reply to this question.