[FIXED][BUG] Gpick doesn't work - used by Colorizer

News & Development Bug reports
1

Gpick is broken, so many functions in Colorizer does not work at the moment :frowning:

Picking colors from screen not possible.

2

Seems to work just fine on my end.

image
image827×496 88 KB

1 Like
3

Yes, already fixed with gpick-0.4-2 pushed to Mabox’s repo.

4

Yeah, but I had yet to upgrade…

image
image476×196 13.7 KB

5

colormenu color pick is working again. Thanks for the update :wink:

I was wondering this morning.

6

@napcok For me when using colormenu gtk-color gui to choose color. I have to save the color first and then copy the code, after that it will be added to colormenu list.

I cannot just pick a color copy color code, close window. The color is not added to the menu.

Is this what you experience too.

7

Very strange, I checked 3 machines, it did not work before update

Yes, from color picker you have to save color with ctrl + s, otherwise it does not return any value (hexcode). I think it always worked like that.

I’m using mostly Pick color from screen option. This one was broken in the morning :wink:

8

Ah, I was using Ctrl-c on the code. :+1:

Mee toooo :stuck_out_tongue_winking_eye:
indeed this was broken… needed the gtk-gui color picker this morning

ps i added mabox auto theming to volbar. It uses now the auto theming too. Testing it … when i think volbar is in its stable final stage, i will create a special topic…

1 Like
9

Now i know the confusion with gcolor3 and having to use super + s with colorizer

I use gcolor3 with picom-simple.

snipped

update_picom_conf() {
     new_color="$1"    # The new color passed as an argument
     config_file="$2"  # The original configuration file (target of the symlink)

    if [ -n "$new_color" ]; then
        sed -i "s/^shadow-color = \".*\"/shadow-color = \"$new_color\"/" "$CONFFILE"
        echo "Updated shadow-color to $new_color in $CONFFILE"
    else
        echo "No color selected. Exiting..."
    fi
}

# Function to select a color using gcolor3    
    symlink_file="$1"  # The symlink file

    # Get the target file of the symlink
    config_file=$(readlink -f "$symlink_file")

    # Ensure we have the target file
    if [ -n "$CONFFILE" ]; then
        color=$(gcolor3 2>/dev/null)  # Get the selected color
        if [ -n "$color" ]; then
            update_picom_conf "$color" "$CONFFILE"
        else
            echo "No color selected or gcolor3 was closed."
        fi
    else
    notify-send -T 500000 -i warning "$NOLINK" "$RELOAD"
        echo "The symlink doesn't point to a valid file."
    fi

When i open gcolor3 and just click a color and close the window, it changes the shadow for picom directly.

It is possible without super+s.

1 Like
10

Thanks, I will update colormenu later tonight.

1 Like
11

Feature request: Differentiate colorizer menu entries

The two colorizer options in the menu currently share the same name, which can be confusing when choosing between them.

Mabox_20260204-18-50-25
Mabox_20260204-18-50-252560×1437 140 KB

Could one be renamed to distinguish them? For example:

  • “Colorizer (jgmenu)” and “Colorizer (yad)”
  • Or “Colorizer” and “Colorizer GUI”

I don’t use the menu colorizers frequently, so each time I need to pause and remember which is which. Clearer naming would help.

1 Like
12

This one is interesting. Desktop files have diferrent names defined, but while searching search shows item from “Mabox config” menu part.
To fix, open ~/.config/mabox/settings.csv and replace label “Colorizer” with “Colorizer Menu” at line 11 (?)
I can’t fix that by package update.

1 Like
13

Nice :wink: click and go…