Recently I've notice that active sliders have a heavy and thick black background, different than when disabled. Compare the two cases in the attached file. http://old.nabble.com/file/p31859141/silders.png As you can see, they are taken under Windows XP. (By the way, notice also that the "Opacity (%):" label is not grayed out). Is this intended? Personally I'd prefer having the same thin rail in both cases. Luca
And I also noticed right now that the blur bar extends a bit more than the other...
Sorry for insisting on this. I know it's a minor issue, but I just wanted to understand if it's intended or not. Should I open a "bug"(?) report about it? Regards.
Hi,
there is no Problem with R10386 on Win7. Maybe it's a problem with a certain or special theme on XP?
Sincerely,
UweSch
Am 29.06.2011 15:58, schrieb LucaDC:
Sorry for insisting on this. I know it's a minor issue, but I just wanted to understand if it's intended or not. Should I open a "bug"(?) report about it? Regards.
Uwe Schöler - OSS-Marketplace.com wrote:
Hi,
there is no Problem with R10386 on Win7. Maybe it's a problem with a certain or special theme on XP?
Sincerely,
UweSch
Thank you for the reply. Indeed, I use Windows XP's Classical theme (old Windows 95/98/2000) and after your suggestion I verified that with the "new" XP theme the sliders are ok. Anyway, I'm having this "problem" only since not so many revisions (I couldn't say which one): I've always had correct sliders before. Hence I think we should consider this a "bug".
On Thu, Jun 30, 2011 at 12:25 AM, LucaDC <dicappello@...2144...>wrote:
Uwe Schöler - OSS-Marketplace.com wrote:
Hi,
there is no Problem with R10386 on Win7. Maybe it's a problem with a certain or special theme on XP?
Sincerely,
UweSch
Thank you for the reply. Indeed, I use Windows XP's Classical theme (old Windows 95/98/2000) and after your suggestion I verified that with the "new" XP theme the sliders are ok. Anyway, I'm having this "problem" only since not so many revisions (I couldn't say which one): I've always had correct sliders before. Hence I think we should consider this a "bug".
Well, the thing that needs to be identified though is where the bug exists. Is this actually an Inkscape bug? It seems more likely to me that the bug is either in that theme or in the newer version of GTK in our devlibs. Note, by saying it could be the theme I mean it could just not have been updated with more recent changes to GTK as it might have needed to be.
Cheers, Josh
Josh Andler wrote:
Well, the thing that needs to be identified though is where the bug exists. Is this actually an Inkscape bug? It seems more likely to me that the bug is either in that theme or in the newer version of GTK in our devlibs. Note, by saying it could be the theme I mean it could just not have been updated with more recent changes to GTK as it might have needed to be.
Sorry but I think I missed the point. Which "theme" do you refer to? I assume you are not speaking about Windows XP's Classic theme as it's been there since ages and sure doesn't need any update to GTK (or if you think so you may contact Microsoft and let them know ;) So, probably you are speaking about Inkscape's theme, which I've never changed from sources (rev. 10391); but as I don't know how to change it, maybe I've got something wrong on my system without knowing. I've tried with fresh preferences (which is the only file I have not taken from sources, apart from a couple of lines added to /share/keys/default.xml) but the problem is still there. Anyway, it sounds weird that changing Windows' theme the problem changes too. As for devlibs, I'm up with rev. 24 (the latest). Is there something I can check to better understand where the problem starts from?
On Thu, Jun 30, 2011 at 8:51 AM, LucaDC <dicappello@...2144...>wrote:
Josh Andler wrote:
Well, the thing that needs to be identified though is where the bug exists. Is this actually an Inkscape bug? It seems more likely to me that the bug is either in that theme or in the newer version of GTK in our devlibs. Note, by saying it could be the theme I mean it could just not have been updated with more recent changes to GTK as it might have needed to be.
Sorry but I think I missed the point. Which "theme" do you refer to? I assume you are not speaking about Windows XP's Classic theme as it's been there since ages and sure doesn't need any update to GTK (or if you think so you may contact Microsoft and let them know ;)
I was under the impression that GTK had a different theme it used when using the classic Windows GTK theme (and it sounds like I may be off the mark on that).
As for devlibs, I'm up with rev. 24 (the latest).
Is there something I can check to better understand where the problem starts from?
It seems likely that it may have to do with something that has changed with GTK somewhere between what we had before and the version we have now. The only way I can think to test/check where things went wrong is to download other GTK binaries between what we had before and what we have now until you find one that doesn't show the issues and work up from there until you can identify when it broke.
Cheers, Josh
Josh Andler wrote:
It seems likely that it may have to do with something that has changed with GTK somewhere between what we had before and the version we have now. The only way I can think to test/check where things went wrong is to download other GTK binaries between what we had before and what we have now until you find one that doesn't show the issues and work up from there until you can identify when it broke.
Mmmh, actually I rely on the devlibs repository for all updates of such libraries. I can see that in rev.22 there has been an update to GTK 2.22 and Glib 2.26. The preceding one was in January (update to Cairo 1.10.2) and I feel that the problem was not present so far ago. The rev.22 update has been quite massive so I don't think I'll be able to make small steps back.
On Thu, Jun 30, 2011 at 10:16 AM, LucaDC <dicappello@...2144...>wrote:
Josh Andler wrote:
It seems likely that it may have to do with something that has changed with GTK somewhere between what we had before and the version we have now. The only way I can think to test/check where things went wrong is to download other GTK binaries between what we had before and what we have now until you find one that doesn't show the issues and work up from there until you
can
identify when it broke.
Mmmh, actually I rely on the devlibs repository for all updates of such libraries. I can see that in rev.22 there has been an update to GTK 2.22 and Glib 2.26. The preceding one was in January (update to Cairo 1.10.2) and I feel that the problem was not present so far ago. The rev.22 update has been quite massive so I don't think I'll be able to make small steps back.
Correct, the problem was probably not present at that time. However, a minor graphical glitch which will be present on a minority of Windows boxes is far less of an issue than a security exploit with gtk that was present on all Windows boxes.
This may be one of those issues where if you're not willing to do the leg work and test, then no one probably will.
Cheers, Josh
participants (3)
-
Josh Andler -
LucaDC -
Uwe Schöler