[ icewm-Bugs-2820195 ] using gradients menu highlight not displaying correctly

Bugs item #2820195, was opened at 2009-07-12 02:42
Message generated for change (Settings changed) made by captnmark
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100031&aid=2820195&group_id=31

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
>Category: icewm-1.3
Group: appearance
>Status: Closed
Resolution: Fixed
Priority: 5
Private: No
Submitted By: Bobby Baldwin (oldhoghead)
Assigned to: Marko Macek (captnmark)
Summary: using gradients menu highlight not displaying correctly

Initial Comment:
This is my first bug report, so bear with me, Currently running antiX- M8.2, in icewm version 1.2.35-1 all themes worked perfectly, when upgraded to icewm 1.2.37+1.3.4pre2-2 some themes, with gradients, the menu background is fine, but the menu highlight causes a sort of double vision, picking up the previous entry and moving it over the top of the next entry that is higlighted, if I use a # on the gradient line, then the double vision goes away, but instead of a solid highlight I get a sort of striped bar. I have attached a snapshot of each to clarify my poor skills at explaining this anomaly.

----------------------------------------------------------------------

Comment By: Stanislav Maslovski (s_i_m)
Date: 2010-01-11 21:30

Message:
Thanks for fixing this.

To thefirstone: my comment was indeed somewhat inappropriate, I am sorry
for that. I had to check the commit history before jumping to conclusions.

----------------------------------------------------------------------

Comment By: Marko Macek (captnmark)
Date: 2010-01-03 19:24

Message:
fixed in icewm-1-3-BRANCH

----------------------------------------------------------------------

Comment By: Eduard Bloch (thefirstone)
Date: 2010-01-03 00:47

Message:
@s_i_m: there is no discrepance between what I wrote in the last comment
and the changelog you just quoted. If you disagree, please reread the
wording of your accusations. Have a nice day...

----------------------------------------------------------------------

Comment By: Frank W McCormick (frankzen)
Date: 2010-01-02 20:22

Message:
I solved my problem by downgrading to 1.2.35 which uses Imlib. Bingo no
more artifacts. I may eventually switch to Fluxbox or Openbox but that's
another story.


----------------------------------------------------------------------

Comment By: Stanislav Maslovski (s_i_m)
Date: 2010-01-02 16:05

Message:
> @s_i_m: as far as you know? What's the source of your knowledge?

That was your changelog:

icewm (1.2.37+1.3.4pre2-1) unstable; urgency=low 
   * Based on upstream development branch release
     + using libgdk_pixbuf instead of Imlib1.x which is now deprecated
       in Debian Unstable (closes: #456127)

After this the bug appeared. I know that you had to do something to get
rid of imlib, but... Now we have 1.3.5 in sid, with the same bug, of
course.

----------------------------------------------------------------------

Comment By: Eduard Bloch (thefirstone)
Date: 2010-01-01 18:20

Message:
@s_i_m: as far as you know? What's the source of your knowledge?

Of course this bug hits the Debian users, because AFAICS Debian packages
are the first ones using 1.3-branch on large scale... and this issue comes
straight from the 1.3-branch, so obviously it appeared in the Debian
package right after switching to it.

It needs to be fixed RSN but my time is limited.

----------------------------------------------------------------------

Comment By: Stanislav Maslovski (s_i_m)
Date: 2010-01-01 17:31

Message:
There is this Debian bug report about the same problem:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544222. Anyone interested
must go and complain there (hint: learn how to use reportbug). It is
pointless to report this at sourceforge as the bug was introduced by the
maintainer of the debian package and is, AFAIK, purely debian-related.

----------------------------------------------------------------------

Comment By: Frank W McCormick (frankzen)
Date: 2009-12-28 19:50

Message:
Guess nobody is looking into this - there are complaints all over the net
and there have been complaints on the Icewm mailing list.
I have tried many gradient-based themes and they all do the same thing.
I'm running th latest from the Debian testing repositories. 


----------------------------------------------------------------------

Comment By: Frank W McCormick (frankzen)
Date: 2009-07-12 14:07

Message:
I get exactly the same thing...and someone else on the IceWm mailing list
reported the same thing. Any gradient theme causes the problem...in fact
some themes drag the CPU to its knees and IceWm becomes unresponsive.


----------------------------------------------------------------------

Comment By: Eduard Bloch (thefirstone)
Date: 2009-07-12 12:04

Message:
Doublevision, nice term here *g*, but don't worry, you are not drunk. I see
the same errors. And there is another similar  appearing in following
situation:

a) use a gradient theme
b) open the PSI client
c) open a chat window, then close the chat window

Result: some window entry shapes in the task bar get pixel garbage sprayed
all over them.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100031&aid=2820195&group_id=31

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev