https://bugzilla.novell.com/show_bug.cgi?id=345506 User rpmcruz@alunos.dcc.fc.up.pt added comment https://bugzilla.novell.com/show_bug.cgi?id=345506#c10 --- Comment #10 from Ricardo Cruz <rpmcruz@alunos.dcc.fc.up.pt> 2007-12-03 13:47:37 MST --- I read this on the mailing list. This is a pretty trivial feature. What about other effects like gray, btw? I won't implement this on yast-gtk because it doesn't even work against recent versions of libyui. But sure, this can be done. We even have code for this from the find entry icons on the help dialog. I'll point that out on a comment on our YImage implementation. Something is wrong about the libyui attachment, right? Or have you just added those fallback hooks for now? Btw, I'd use a more generic name like UI::HasImageEffectsSupport(). Whats important is whether the UI code can do pixel manipulation. Qt and GTK+ can. Wt can't. (needless to say, ncurses doesn't even support images, so it would return false too.) How do you intend to enable this feature from the code? If you add an `opt option at the widget constructor, then of course will have to construct several widgets, which means using ReplacePoints. Maybe we could add a UI::ImageApplyEffect(image, `dim|`grey...) ? The UI could even optimize this by keeping the several transformations in memory, as demanded, until the image is destructed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.