https://bugs.documentfoundation.org/show_bug.cgi?id=145725
--- Comment #6 from Wolfgang Jäger <j...@psilosoph.de> --- (In reply to Julien Nabet from comment #4) > (In reply to Wolfgang Jäger from comment #3) > > ... ... > > But: There is a RGB() function in VBA, > > and it expects the arguments in order r, g, b. > > > > See also > > https://docs.microsoft.com/en-us/office/vba/language/reference/user- > > interface-help/rgb-function > > The pb isn't the order of arguments when calling the function, both LO and > MS use R, G and B args in this order but it's a matter of how to store the > values in one single Long value. > > It's precisely indicated in Mike's link: > " > In other words, the individual color components are stored in the opposite > order one would expect. VB stores the red color component in the low-order > byte of the long integer's low-order word, the green color in the high-order > byte of the low-order word, and the blue color in the low-order byte of the > high-order word > " Sorry. I simply couldn't imagine such an absurd lack in standards. I should have known better. In addition I feel lost considering the consequences for users Of VBA in LibO generally. And what would be the effect if LiBO running code under VBAsupport 1 Would revert the byte order for the RGB result to its own habit. Where are RGB results ever exported to the file except when assigned to a colored object? The visible color is interpreted the LibO way, of course, and written after encoding it the LibO way. -- You are receiving this mail because: You are the assignee for the bug.
