Open GoogleCodeExporter opened 8 years ago
Oh a new config file with all new (wm_menu) implications would be cool too.
Original comment by kes...@gmail.com
on 6 Jun 2009 at 10:13
yes keshto,
tint2 doesn't depend on GTK. so we don't have the capability to open a menu.
will leave this request open (but don't expect change soon)...
Original comment by thilo...@gmail.com
on 7 Jun 2009 at 7:24
wm_menu implication
wm_menu = 1
tint2 forward all mouse event done in panel padding area to you window manager.
so panel's border (left/right/top/bottom) will act like the window manager.
it's useful when tint2 run on a small screen with maximized application :)
tint2 will not implement 'menu', but use menu's window manger (better
consistency).
wm_menu = 0
disabled this feature.
Original comment by thilo...@gmail.com
on 7 Jun 2009 at 7:38
[deleted comment]
Is it possible to have tint2 to just have a menu popup rather then poping up
the gtk
menu? Like a simple menu that has "maximize/restore, minimize, close" or
something
simple like that?
Original comment by kes...@gmail.com
on 21 Jun 2009 at 6:52
no, it's not the good way to do it because:
- to keep tint2 light we can't rewrite toolkit functionality
- if we show a menu, it's better to have consistency with current theme, ...
Original comment by thilo...@gmail.com
on 21 Jun 2009 at 8:22
A window-menu popup (maximize, restore, etc) would require a custom-coded
menu,and
require gtk I think? Are you going to add gtk dependency as a result of the
tint2conf work?
Otherwise, perhaps it would be possible to code a separate application that
runs a
window menu for a given window ID, and have tint2 just execute that?
Original comment by jackpip...@gmail.com
on 18 Jul 2009 at 4:16
@ jackp...@fastmail.fm
tint2conf will have gtk dependencies.
but it's not included in tint2 (it's another software).
Your idea to have another tint2menu is interresting.
It could be a first step, and later perhaps we can include this code in tint2.
If you want to do it, your are welcome.
Original comment by thilo...@gmail.com
on 18 Jul 2009 at 7:43
And isn't it possible to just invoke a window manager's menu? I don't think the
openbox's menu depends somehow on GTK.
Original comment by dmitry.medvinsky@gmail.com
on 19 Aug 2009 at 8:02
How about just a simple feature of allowing tint2 to fire up a external program
on a
certain mouse click. For example, on right click call lil menu program or on
right
click call xmessage "hello" or whatever?
@dmitry
"wm_menu = 1
tint2 forward all mouse event done in panel padding area to you window manager."
are you suggesting to this feature?
@jackp
Yea I think a simple external program wouldn't be that bad of an idea..
Original comment by kes...@gmail.com
on 19 Aug 2009 at 11:30
@keshto
Err, I'm not sure. Maybe I didn't understand it properly, but why use panel
padding
area? I meant a command just like the others (close, iconify, toggle, shade),
something like mentioned wm_menu, which triggers the window manager's menu.
Original comment by dmitry.medvinsky@gmail.com
on 20 Aug 2009 at 6:34
I do not know, if this was meant by the original author, but it would be also
nice,
if the menu could popup which pops up, when I right click on the title of a
window
(i.e. in openbox the menu "client-menu")
Original comment by Andreas.Fink85
on 27 Aug 2009 at 7:45
@Andreas.Fink85
That is EXACTLY what I mean :) you took the words out of my mouth ;)
Original comment by kes...@gmail.com
on 27 Aug 2009 at 9:03
dunno if that match with this thread (or I'll start a new on) but I think could
be
cool:
panel_rclick_command = (custom, "wm_menu", .. )
panel_mclick_command = ..
instead of "wm_menu = 0\1"
Original comment by ozz...@gmail.com
on 8 Apr 2010 at 12:47
I do not get your idea ozzolo?
Maybe you have the wrong idea of wm_menu (because the name of this property is
confusing). Basically wm_menu = 1 means that every click which is not handeled
by
tint2 will be forwarded to the root window (i.e. the window manager).
So it comes down to configure your window manager to react on right-click /
middle-click / wheel-events.
Showing the window-manager window-menu (i.e. where you can close / iconify /
what-ever) is not possible, so this issue cannot be solved at the moment (not
in a
way without building an own menu)
Original comment by Andreas.Fink85
on 9 Apr 2010 at 11:13
I know that it's not possibile to show the window-menu and I don't want to.
I would only customizable "mouse actions on panel", as
"clock_(l\r)click_command" in
the clock section, no only on tasks.
That could replace "wm_menu" (wm_menu could be an option for the
"panel_rclick_command")
Original comment by ozz...@gmail.com
on 9 Apr 2010 at 2:03
I think what some people (like me) would like would be more or less a
wm_menu-like "tweak" for mouse action over tasks (with the wm_menu on padding
staying right as it is).
Instead of forwarding a click as if it were on a blank desktop space, there
could be (or at least that's what we hope for) a wm_menu-like option to as if
the click was over the titlebar icon on openbox (client-menu, I guess), which
would open a "send to desktop, ... maximize, restore, close" menu. (But that
ultimately depends on how openbox is configured to handle the icon button on
the titlebar, if it's even there).
Sorry if I'm being redundant, if it was well understood, I got the impression
that it was what some people suggested and that some people where understanding
something else.
I guess that it all would be much easier to do if it was a taskbar/panel
embedded on openbox, like fluxbox', rather than something external. :-/
Original comment by extremof...@gmail.com
on 20 Jul 2010 at 10:21
Original comment by mrovi9...@gmail.com
on 1 Feb 2015 at 9:18
Original comment by mrovi9...@gmail.com
on 2 Feb 2015 at 12:15
Project moved to GitLab.
You can find this issue at: https://gitlab.com/o9000/tint2/issues/96
Original comment by mrovi9...@gmail.com
on 25 Apr 2015 at 11:22
Original issue reported on code.google.com by
kes...@gmail.com
on 6 Jun 2009 at 10:13