| 2021-05-04 07:35:10 |
richard clarke |
description |
3.8.2 in Arch (openbox) and Porteus(Slackware based) openbox and wayfire
attempting to set background opacity causes the window to "disappear" (looks like it crashes but is actually setting the opacity to zero, thus becoming invisible, though panel taskmanager shows it)
After lookin g a bit at the commit history, i noticed in https://git.launchpad.net/sakura/commit/?id=a09eb26c45f1283e5d3206887c3c26ab6ebea346 :
line :
GtkSpinButton *opacity_spin = g_object_get_data(G_OBJECT(dialog), "spin_opacity");
should read:
GtkSpinButton *opacity_spin = g_object_get_data(G_OBJECT(dialog), "opacity_spin");
patching that and recompiling confirmed this.
While i'm at it, it seems that there's new opacity behavior ie. the entire window, including the windowmanager decoration becomes transparent, where previously(eg. 3.7.1) only the terminal backgound is affected. Is this intentional? |
3.8.2 in Arch (openbox + compton) and Porteus(Slackware based) openbox+compton and wayfire
attempting to set background opacity causes the window to "disappear" (looks like it crashes but is actually setting the opacity to zero, thus becoming invisible, though panel taskmanager shows it)
After looking a bit at the commit history, i noticed in https://git.launchpad.net/sakura/commit/?id=a09eb26c45f1283e5d3206887c3c26ab6ebea346 :
line :
GtkSpinButton *opacity_spin = g_object_get_data(G_OBJECT(dialog), "spin_opacity");
should read:
GtkSpinButton *opacity_spin = g_object_get_data(G_OBJECT(dialog), "opacity_spin");
patching that and recompiling confirmed this.
While i'm at it, it seems that there's new opacity behavior ie. the entire window, including the windowmanager decoration becomes transparent, where previously(eg. 3.7.1) only the terminal backgound is affected. Is this intentional? |
|
