You are not logged in.
Should be fine now. It was just a line of code I changed accidentally when I patched in the gradients.
Offline
Should be fine now. It was just a line of code I changed accidentally when I patched in the gradients.
...and within 4 minutes of your post, I've git pulled, built, installed and.....everything is cool
EDIT: Screenshot
Last edited by damo (2016-10-04 13:33:35)
Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt «» BunsenLabs on DeviantArt
Offline
I removed all the element_gradient_id config options, instead the backgrounds have 3 options gradient_id, hover_gradient_id and pressed_gradient_id. Documented in https://gitlab.com/o9000/tint2/blob/mas … #gradients
Still no tint2conf support. I'd like to release a new version, as a few old bugs have been fixed, but without tint2conf in sync it's not right.
But I hate writing config GUIs, so I really don't feel like doing it any time soon
Or I could just add a text edit for the gradients and be done with it
Last edited by o9000 (2017-02-19 18:38:55)
Offline
Do I really need to define separator block twice to use it twice? (or I'am missing something)
if true;
perhaps last one should be just reused by default (same for E)?
Last edited by brontosaurusrex (2017-02-20 19:04:35)
Online
Yes. I will think about it more.
Offline
i recently noticed that tint2-git depends on gtk2 - is that really so? i'm a little surprised. maybe it's only for tint2conf?
Offline
Offline
^ just like i thought.
i'm not concerned by this; i was having a discussion with someone who was vaguely annoyed that even the most lightweight panels have "too many dependencies"...
but thanks anyway.
Offline
I could get rid of glib too, and I would actually like to, since it has an idiotically designed memory management that has caused some crazy problems (basically it hides under the carpet certain bugs, that end up biting you later; it's so bad that even advanced memory checking tools like Google's ASAN are unable detect the bugs). But it would have to be replaced with something else, maybe C++, which is something I don't have time for this spring.
Offline
Heck, I think even valgrind wouldn't catch those problems. It's insane.
Offline
Heck, I think even valgrind wouldn't catch those problems. It's insane.
https://github.com/dtrebbien/GNOME.supp
Might help...
Nevermind, you're talking about detection, not suppression. Leaving the link anyway!
If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres
Offline
o9000 wrote:Heck, I think even valgrind wouldn't catch those problems. It's insane.
I can recommend looking at libtalloc from the Samba project. It's a well-written tree allocator with special support for arrays and suchlike, has helped me tremendously in C when it came to more complex memory management. No hash tables however (though a simple HT implementation is simple, and existing small implementations could easily get adapted for talloc).
Looks interesting, thank you.
Offline
Now there is almost complete support for gradients in tint2conf (except for extra color stops; but if you add them by hand to the config file, tint2conf will preserve them).
Feedback would be appreciated. Once I add support for the color stops, I will release 0.13.
Offline
New release.
Offline
Big moment
I've compiled and installed.
Have you pushed the v0.13 tag?
Offline
Oops. It's pushed now Thanks.
Offline
Will try to add start button in 0.14.
Offline
^ Nice work!
I've just flagged the Arch package as out-of-date, let's see how long it takes them to catch up...
8)
Offline
Here is a demo of the new config options: whats-new-0.13.0.gif
Offline
re: demo, wow wow wow.
Thanks for your hard work!
No, he can't sleep on the floor. What do you think I'm yelling for?!!!
Offline