Open GoogleCodeExporter opened 9 years ago
Original comment by thilo...@gmail.com
on 2 Apr 2010 at 8:20
Original comment by thilo...@gmail.com
on 2 Apr 2010 at 8:21
added in SVN.
according to task's vertical padding and size of font, tint2 will used
multi-line
when possible.
Original comment by thilo...@gmail.com
on 19 Apr 2010 at 9:46
An option to forcibly turn this behavior off is also needed, I guess.
Thank you but this is not what I actually meant. I wanted *task buttons* to be
placed
in multi-line, not text on them. Consider this:
http://goodies.xfce.org/_media/projects/panel-plugins/xfce4-quicklauncher-plugin
.png
Original comment by baltazar...@gmail.com
on 20 Apr 2010 at 5:56
Original comment by thilo...@gmail.com
on 20 Apr 2010 at 7:49
After upgrading form Debian squeeze to wheezy, my usual theme now has two lines
of text on each task label. However, some other themes I've tried (like the
default) use the old method of cutting off the name and appending an ellipsis (
'...' ) to the end on tasks with long names.
What is controlling this behavior? How can I disable it?
Original comment by DanielBa...@gmail.com
on 22 Feb 2011 at 3:36
I think setting a task_padding will solve your problems... The area's height
will shrink, and with it the possibility to put multiple lines of text there.
Original comment by Andreas.Fink85
on 22 Feb 2011 at 7:33
yes, you can
- increase font height
- or in task_padding = x y, you can increase y parameter until tint2 draw one
line
Original comment by thilo...@gmail.com
on 22 Feb 2011 at 8:24
Was it removed from the SVN or was only the "text in multiple lines" feature
added?
I think baltazar explained it perfectly by sending link to:
http://goodies.xfce.org/_media/projects/panel-plugins/xfce4-quicklauncher-plugin
.png
Right now tray icons are split up in 2 or more lines but not the tasks.
Original comment by janho...@gmail.com
on 3 Jan 2012 at 6:08
Original comment by mrovi9...@gmail.com
on 1 Feb 2015 at 10:26
Original comment by mrovi9...@gmail.com
on 2 Feb 2015 at 12:07
Original issue reported on code.google.com by
baltazar...@gmail.com
on 2 Apr 2010 at 4:50