All,
Is there something I'm missing in the Scintilla documentation when it comes to whatever RGBA64 format it is using? In particular a method that would cleanly bust it up into the R, G, B, A values?
I'm just being thick headed and stubborn I know, but in example3 I wanted the EDT prompt line to match the edit window like it does in Emacs.
They are actually nice and use the comment syntax color for the prompt text and the standard text color for typed information. There are not syntax colors in example3. That will be another couple of examples from now.
What I have currently is the default gray, black, and white one gets under Ubuntu 20.04 LTS, which is fine.
I dutifully pulled the values via the method calls and passed them into the function where I dutifully tell CopperSpice (will be much the same if not exactly the same for Qt) this 64-bit value is an RGBA64 value.
There are no errors or complaints.
A big part of the shaft I'm receiving is the alpha value being 0 (completely translucent). Instead of the "Search for:" prompt followed by an entry field with a white background where typed text appears in black, I get this.
It's not a logic error. If I type my text then drag the mouse to select it I can see the text.
When I go to
this site and key in the RGB values the colors don't seem correct. It's like the default colors aren't ever really set anywhere internally. Everything is set to transparent and somehow the widget "just knows" it is using system colors that it never shares.
So, I guess my questions are thus:
- Is there a tool/function for busting this value up properly?
- Is my worst fear correct that when you have set no style, all of the values returned by styleFore() styleBack() are deliberately (or regularly) invalid with an alpha of zero for safety?
- If 2 is correct, how does one determine what colors are being used or can that only be done if a style has been set?
Thanks for taking the time to read.
If you are in America I hope you are having a fantastic Labor Day!
Roland