OpenXTalk Forums

More 'Non fun' #2
This time, just a simple example of picking a colour, then returning the web colour reference (#ff0000) for example.
(will be using this in my properties inspector stack), but thought I'd post it on it's own in case anyone found it interesting.

version 2, added the ability to drag a colour from the swatch above, into saved swatches - or drag onto the + to create a new swatch: (sliders look different, just because I'm back on my linux box, not because I've made a decision to change them)
edit: emphasized the above point. edit2: deleted extra comments after this, in the interests of clarity, and expanded on that further down the page.

You don't have dark mode loaded properly.

Let's see:-
- - -
That would seem to indicate that anyone else using dark mode with OXT Lite and MacOS 14 Sonoma is going to experience similar difficulties.

No, your screenshots of the appearance control panel in Mac OS - that's not what I mean. Don't worry. It's because dark mode isn't being invoked properly past MacOS 10.15
I know where the bug is, just set to light mode (didn't think you used dark mode anyway?)
Putting all these screenshots on here is all well and good, but only solves to muddy the waters. Especially when it has nothing to do with the swatch stack. Your issue is with the inspector and how fields don't look correct in it, (and you do know I'm remaking that anyway, don't you?).

You might have missed it, but the reason why dark mode might not be triggering for MacOS users past 10.15 is mentioned here, directly under your first paris hilton post (which is another issue I need to bring up with you if I'm supposed to be moderating effectively [1] [2])

https://www.openxtalk.org/forum/viewtop ... 7580#p7580

My reasons for not catching this sooner is due to not having anything that runs MacOS past 10.15.

Edit: hang on a minute, what really boggles my noggin is that you must of read that, because you commented directly underneath. So I don't understand why things not looking right in MacOS under dark mode would be a surprise.
Or are you genuinely just pulling my leg and messing with my head here?

As I say - that's entirely off topic for this particular post, because it's related to the other problem [dark mode not firing due to incorrect system version detection] - not an issue with the swatch stack above.

Why do I bother to post anything, when it's instantly jumped upon and picked apart?

Why do I bother to post anything, when it's instantly jumped upon and picked apart?

1. Oh: I was not 'jumping upon' anything: I was pointing out HOW your swatch thing looked on MacOS Sonoma.

2. You have a kinky, masochistic 'thing' . . .

3. I suppose you want me to cover you with virtual, slobbery kisses because of the 99% of your work which is wonderful . . .

Right: 'OFF' to torture some tinies for the next 3 hours.

richmond62 wrote: ↑Thu Mar 28, 2024 1:47 pm 3. I suppose you want me to cover you with virtual, slobbery kisses because of the 99% of your work which is wonderful . . .

You don't have to go that far, but there's probably a reason nobody has attempted fixing half this stuff - it's not an easy task in most cases, so I'd just ask you to be mindful of that before using comments like "terrible / dreadful". If it doesn't get my back up (which it instantly will), I'm sure it'll make other people who post contributions here feel the same as in 'why the did I bother'?

I have nearly walked away from the entire project before [too sensitive? probably, but then criticism hurts if you have ADHD], and it's only because I'm interested in seeing OXT lite be a working alternative, that I came back. Potential contributors might think 'nope - not putting my offering out there, if that's what's going to happen'. We want to be encouraging submissions, not batting anything aside, or pushing anyone's work back at them - as there's always an interesting nugget of information to glean from any submission, no matter how much it can be improved.

richmond62 wrote: ↑Thu Mar 28, 2024 1:47 pm Right: 'OFF' to torture some tinies for the next 3 hours.

Pass on my sympathies to them.

Version 3.
Now with a popup control, so you can type RGB num 0 to 255 in manually. I also thought, a popup like this is also how you could handle a discreet progress bar notification (discussed elsewhere on another thread).

You don't want a progress bar to be TOO discreet: it has to be noticed.

Well, here I am at home (which means MacOS 12) and your new version seems good, and (Shock, Horror!) the preference palettes are slightly better than on 'Snowman':
- - -
I hope you appreciate the fact that I had to put myself through a considerable amount of personal pain NOT to lob you a neg. comment. LOL

Tom Version 3 looks great with that 'HUD' style display, slick. And being able to input the R,G,B numeric values via keyboard input is essential imo, can it also use tabKey to go from R-to-G-to-B fields?

richmond62 wrote: ↑Thu Mar 28, 2024 7:56 pm Well, here I am at home (which means MacOS 12) and your new version seems good, and (Shock, Horror!) the preference palettes are slightly better than on 'Snowman':
-
Screenshot 2024-03-28 at 21.52.36.png
-
Screenshot 2024-03-28 at 21.53.15.png
-
I hope you appreciate the fact that I had to put myself through a considerable amount of personal pain NOT to lob you a neg. comment. LOL

THIS is actually a problem with the slider-style scrollbars classic controls on macOS with DarkMode. that center line is always black an so is nearly invisible in darkMode, I'm I don't think there's a property to set the color for that line. In the past I've group those so that I can stylize the group with overlay effects to try to make it them look better in darkMode.

Another option, like my progressbar widget, I also have a widget implementation of a slider.

In fact I think I may have nearly a full set of 'classic controls' replacements as widgets, or at least a usable base for that. they would need work to ensure they would have all or most of the same properties as our 'classic controls'.

OpenXTalkPaul wrote: ↑Fri Mar 29, 2024 2:51 am Tom Version 3 looks great with that 'HUD' style display, slick. And being able to input the R,G,B numeric values via keyboard input is essential imo, can it also use tabKey to go from R-to-G-to-B fields?

Good idea . It now does this
(v4) Oh, and if anyone is wondering how I solved the scrollbars having 'no track' on Linux, I edited my linux system appearance theme, restarted OXT Lite, and they are correct. *You would not be able to fix that so easily under MacOS I'm afraid. So, now all subsequent scrollbars I see & create will have a 'track' - without having to put a background colour behind it to compensate.

Point is, this is how oxt should pick up on the system themes on other platforms too, but that was another conversation; not related to the swatch stack.

You would not be able to fix that so easily under MacOS I'm afraid.

About 30 seconds:
- -

Better 'blob' contrast:
- -

Each to their own, personally I really dislike having a 'blob' behind the sliders. Especially an orange one.

I'm not that keen on the orange background either. But I cannot work out a way to make the contrast between the 'tracks' and the standard card background better.

If you use a Custom Control or Extension Widget for a slider, unlike the classic control sliders, it will look exactly the same on every platform. I found it is much too difficult to ensure that the same 'classic control' based slider looked good on multiple platforms with various UI themes.

OpenXTalkPaul wrote: ↑Thu Apr 11, 2024 2:04 am If you use a Custom Control or Extension Widget for a slider, unlike the classic control sliders, it will look exactly the same on every platform.

Could you give us an example please, in a stack we can download - that would be excellent.

Worth a look:

https://forums.livecode.com/viewtopic.p ... et#p227634

richmond62 wrote: ↑Thu Apr 11, 2024 9:39 am Worth a look:
https://forums.livecode.com/viewtopic.p ... et#p227634

That does indeed seem to function. It's fairly simplistic, just made using a group and graphics.
Is that what you meant Paul, or did you have something else in mind?

I am sure that is NOT what Paul meant, as he used the word 'widget', and those are NOT widgets.