superswitcher - Project Hosting on Google Code

Last 30 days Dec 23, 2009 issue 20 (segfault randomly) commented on by clarf.puppylinux - Hi, I was using superswitcher 0.6 in Puppy Linux 214X (Release Candidate) and I had the same segfault right after I killed any other running application. Anyway after I installed the latest SVN version (Revision 37) I didn´t get any segmentation fault in Puppy Linux, I can kill any app and superswitcher still works fine without errors. Puppy Linux uses JWM Windows Manager and Rox-Filer. It seems that you get few feedback about the latest Revisions and this segafault issue, In my opinion this is a mayor bug fixed in latest SVN. I suggest you to Release in your HomePage a new version (could be 0.65 or something between) with the latest SVN version, because few people try the latest SVN versions or search inside the google.code pages and as I said before this is a mayor bug that prevents Superswicther to be used in a wider range of Windos Managers. Than your for the attention pleased. I also want to wish you a very happy holiday and a great new year. Please keep this great project alive. clarf. Hi, I was using superswitcher 0.6 in Puppy Linux 214X (Release Candidate) and I had the same segfault right after I killed any other running application. Anyway after I installed the latest SVN version (Revision 37) I didn´t get any segmentation fault in Puppy Linux, I can kill any app and superswitcher still works fine without errors. Puppy Linux uses JWM Windows Manager and Rox-Filer. It seems that you get few feedback about the latest Revisions and this segafault issue, In my opinion this is a mayor bug fixed in latest SVN. I suggest you to Release in your HomePage a new version (could be 0.65 or something between) with the latest SVN version, because few people try the latest SVN versions or search inside the google.code pages and as I said before this is a mayor bug that prevents Superswicther to be used in a wider range of Windos Managers. Than your for the attention pleased. I also want to wish you a very happy holiday and a great new year. Please keep this great project alive. clarf. Dec 12, 2009 issue 9 (Feature Request: quick shortcuts) commented on by clarf.puppylinux - I was about to request the same thing, but I see the description of this issue... A .superswitcher configuration file could be great for that, then you could decide to use keypad or keyborad to select the right shortcut. Please don´t forget laptop users when you improve Superswitcher :). Thank you clarf I was about to request the same thing, but I see the description of this issue... A .superswitcher configuration file could be great for that, then you could decide to use keypad or keyborad to select the right shortcut. Please don´t forget laptop users when you improve Superswitcher :). Thank you clarf Older Nov 21, 2009 issue 45 (Allow "geometric" window picking) reported by thomas.j.johnson - It would be a great feature (IMHO) to allow the user to cycle windows by their screen coordinates. So for instance, using the numeric keypad for directions, Super-8 would go to the first window that was above the current window on the current desktop, Super-4 would go to the first window to the left of the current one, etc. This would create an even more intuitive window-switching interface. It would be a great feature (IMHO) to allow the user to cycle windows by their screen coordinates. So for instance, using the numeric keypad for directions, Super-8 would go to the first window that was above the current window on the current desktop, Super-4 would go to the first window to the left of the current one, etc. This would create an even more intuitive window-switching interface. Nov 21, 2009 issue 44 (Bind arbitrary meta keys) reported by thomas.j.johnson - Allow super-switcher to use arbitrary meta keys (Especially, say, "Alt" so that it can replace Alt-Tab completely) Allow super-switcher to use arbitrary meta keys (Especially, say, "Alt" so that it can replace Alt-Tab completely) Nov 12, 2009 issue 10 (Sticky windows only show up on Desktop 1) commented on by jurgo.boemo - when i sticky pidgin window, superswichter end to run. I'm using unbuntu 9.04 with 8 workspaces when i sticky pidgin window, superswichter end to run. I'm using unbuntu 9.04 with 8 workspaces Sep 15, 2009 issue 43 (New shortcut - send window to workspace without switching) commented on by alex.baibarin - It's a feature request, of course. Don't see obvious way to set issue type, sorry. It's a feature request, of course. Don't see obvious way to set issue type, sorry. Sep 15, 2009 issue 43 (New shortcut - send window to workspace without switching) reported by alex.baibarin - Would like to see it. Default XFCE window manager lacks this hotkey. Just send window to another workspace without switching to that workspace, so app could run a kind of "background" from main flow Perhaps, setting in config file changing default behaviour of Super+Fn+Shift ? It could detail if we switch workspace or not Would like to see it. Default XFCE window manager lacks this hotkey. Just send window to another workspace without switching to that workspace, so app could run a kind of "background" from main flow Perhaps, setting in config file changing default behaviour of Super+Fn+Shift ? It could detail if we switch workspace or not Sep 15, 2009 issue 32 (Doesn't run on xfce4) commented on by alex.baibarin - Just tested in Zenwalk 6.2 (XFCE 4.6.1) Built from last stable release (not svn) Gives error message when starting from terminal, but otherwise works as expected. Excellent Just tested in Zenwalk 6.2 (XFCE 4.6.1) Built from last stable release (not svn) Gives error message when starting from terminal, but otherwise works as expected. Excellent Sep 03, 2009 issue 42 (Avant window navigator (awn)'s last.fm applet crashes supers...) commented on by g...@prettycircus.org - Did you build superswitcher yourself or did you get a binary from somewhere? -- I grabbed a binary from the Arch repositories. If self-built, did you build from latest trunk, or did you build from the 0.6 .tar.gz file? -- Also, are you using metacity, compiz, or a different window manager? -- I'm using xfwm4 ! You're welcome! Did you build superswitcher yourself or did you get a binary from somewhere? -- I grabbed a binary from the Arch repositories. If self-built, did you build from latest trunk, or did you build from the 0.6 .tar.gz file? -- Also, are you using metacity, compiz, or a different window manager? -- I'm using xfwm4 ! You're welcome! Sep 03, 2009 issue 42 (Avant window navigator (awn)'s last.fm applet crashes supers...) commented on by nigel.tao.gnome - Did you build superswitcher yourself or did you get a binary from somewhere? If self-built, did you build from latest trunk, or did you build from the 0.6 .tar.gz file? Also, are you using metacity, compiz, or a different window manager? Thanks! Did you build superswitcher yourself or did you get a binary from somewhere? If self-built, did you build from latest trunk, or did you build from the 0.6 .tar.gz file? Also, are you using metacity, compiz, or a different window manager? Thanks! Sep 02, 2009 issue 42 (Avant window navigator (awn)'s last.fm applet crashes supers...) reported by g...@prettycircus.org - What steps will reproduce the problem? 1. ensure superswitcher is running, yo 2. ensure awn is running with the last.fm applet in its box, yo 3. click the last.fm fella, recieve bugz report What is the expected output? What do you see instead? I, in fact, expect nothing to happen on supersswitcher's side. I simply expect the gentleman to keep busy doing what he's good at. Instead I see a kind of a beetle fellow on GNOME's bug reporting tool. What version of the product are you using? On what operating system? SuperSwitcher version 0.6 Archlinux (if you are rms, that linux is their operating system name, i normally write gnu/linux, I promis.) Please provide any additional information below. I'm attaching a few of bug reports. What steps will reproduce the problem? 1. ensure superswitcher is running, yo 2. ensure awn is running with the last.fm applet in its box, yo 3. click the last.fm fella, recieve bugz report What is the expected output? What do you see instead? I, in fact, expect nothing to happen on supersswitcher's side. I simply expect the gentleman to keep busy doing what he's good at. Instead I see a kind of a beetle fellow on GNOME's bug reporting tool. What version of the product are you using? On what operating system? SuperSwitcher version 0.6 Archlinux (if you are rms, that linux is their operating system name, i normally write gnu/linux, I promis.) Please provide any additional information below. I'm attaching a few of bug reports. Aug 17, 2009 issue 10 (Sticky windows only show up on Desktop 1) commented on by sean.pringle - For me -- on Ubuntu Intrepid, libwnck22 2.24.1-0ubuntu1 -- Superswitcher's add_window_to_screen() triggers this same assertion failure when wnck_window_get_workspace returns NULL, which apparently is the case for all sticky windows. I changed add_window_to_screen() to just ignore the window in this case, and no more crash. This is a nasty hack, but I don't care about sticky windows appearing in SS... Diff is attached for those who care! cheers For me -- on Ubuntu Intrepid, libwnck22 2.24.1-0ubuntu1 -- Superswitcher's add_window_to_screen() triggers this same assertion failure when wnck_window_get_workspace returns NULL, which apparently is the case for all sticky windows. I changed add_window_to_screen() to just ignore the window in this case, and no more crash. This is a nasty hack, but I don't care about sticky windows appearing in SS... Diff is attached for those who care! cheers Aug 11, 2009 issue 28 (Too much RAM needed) commented on by ape3000 - Superswitcher uses 1.9 MB RAM on my 64-bit Ubuntu 9.04. That's not too much, so I'd close this bug as fixed or invalid. Superswitcher uses 1.9 MB RAM on my 64-bit Ubuntu 9.04. That's not too much, so I'd close this bug as fixed or invalid. Jul 12, 2009 issue 25 (Caps Lock does not work even after Superswitcher process is ...) commented on by s.bhooshi - hmm, this isn't nice. Why doesn't superswitcher exit in an expected fashion? hmm, this isn't nice. Why doesn't superswitcher exit in an expected fashion? Jul 02, 2009 issue 41 (Superswitcher segfaults by random) commented on by basakj - I used Fluxbox 1.1.1 , arch linux OS. pacman -Q \| grep wnck libwnck 2.26.1-1 I used Fluxbox 1.1.1 , arch linux OS. pacman -Q \| grep wnck libwnck 2.26.1-1 Jul 02, 2009 issue 41 (Superswitcher segfaults by random) commented on by nigel.tao.gnome - Hi, I'm the project owner. > It seems the project owner abandoned the project Yeah, I'm still alive, but I've been pretty busy with other stuff for a long time now. Sorry. One thing re segfaults -- are you running metacity or compiz (or something even more exotic)? I've had many problems with compiz, in the past. I can believe that it's broken on Jaunty (I'm still on Intrepid, having no compelling reason to upgrade). The libwnck library doesn't promise API compatability across releases, and they could easily have changed something that broke superswitcher. Oh, patches welcome, by the way. Hi, I'm the project owner. > It seems the project owner abandoned the project Yeah, I'm still alive, but I've been pretty busy with other stuff for a long time now. Sorry. One thing re segfaults -- are you running metacity or compiz (or something even more exotic)? I've had many problems with compiz, in the past. I can believe that it's broken on Jaunty (I'm still on Intrepid, having no compelling reason to upgrade). The libwnck library doesn't promise API compatability across releases, and they could easily have changed something that broke superswitcher. Oh, patches welcome, by the way. Jul 02, 2009 issue 41 (Superswitcher segfaults by random) commented on by timmygee - Appreciated! Please message back when done :) Tim Appreciated! Please message back when done :) Tim Jul 02, 2009 issue 41 (Superswitcher segfaults by random) commented on by honorshark - It seems the project owner abandoned the project, but I'll try to fix this error in the source code and make a 0.5 release with other fixes. It seems the project owner abandoned the project, but I'll try to fix this error in the source code and make a 0.5 release with other fixes. Jul 02, 2009 issue 41 (Superswitcher segfaults by random) commented on by timmygee - This is what I got from debug: $ gdb superswitcher GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu"... (gdb) run Starting program: /usr/local/bin/superswitcher [Thread debugging using libthread_db enabled] [New Thread 0xb72f5970 (LWP 8393)] (superswitcher:8393): Wnck-CRITICAL : wnck_workspace_get_number: assertion `WNCK_IS_WORKSPACE (space)' failed Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb72f5970 (LWP 8393)] 0x0804fc1f in ss_window_new (workspace=0x0, wnck_window=0x8819aa0) at window.c:345 345 gtk_label_set_max_width_chars (GTK_LABEL (label), workspace->screen->label_max_width_chars); This is what I got from debug: $ gdb superswitcher GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu"... (gdb) run Starting program: /usr/local/bin/superswitcher [Thread debugging using libthread_db enabled] [New Thread 0xb72f5970 (LWP 8393)] (superswitcher:8393): Wnck-CRITICAL : wnck_workspace_get_number: assertion `WNCK_IS_WORKSPACE (space)' failed Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb72f5970 (LWP 8393)] 0x0804fc1f in ss_window_new (workspace=0x0, wnck_window=0x8819aa0) at window.c:345 345 gtk_label_set_max_width_chars (GTK_LABEL (label), workspace->screen->label_max_width_chars); Jul 02, 2009 issue 41 (Superswitcher segfaults by random) commented on by timmygee - I'm also having this problem I built superswitcher from source on Ubuntu Jaunty. Not random at all, it just won't run. Full error output: (superswitcher:8154): Wnck-CRITICAL : wnck_workspace_get_number: assertion `WNCK_IS_WORKSPACE (space)' failed Segmentation fault Tim I'm also having this problem I built superswitcher from source on Ubuntu Jaunty. Not random at all, it just won't run. Full error output: (superswitcher:8154): Wnck-CRITICAL : wnck_workspace_get_number: assertion `WNCK_IS_WORKSPACE (space)' failed Segmentation fault Tim Jun 28, 2009 issue 41 (Superswitcher segfaults by random) reported by honorshark - What steps will reproduce the problem? 1. Using superswitcher.. I only get this into 'dmesg': superswitcher[2244]: segfault at 30 ip 000000000040a1be sp 00007fff0b83b130 error 4 in superswitcher[400000+d000] Version: 0.6 What steps will reproduce the problem? 1. Using superswitcher.. I only get this into 'dmesg': superswitcher[2244]: segfault at 30 ip 000000000040a1be sp 00007fff0b83b130 error 4 in superswitcher[400000+d000] Version: 0.6 Jun 21, 2009 issue 40 (Add functionality: ability to close windows from superswitch...) Status changed by nigel.tao.gnome - Status: WontFix Status: WontFix Jun 18, 2009 issue 40 (Add functionality: ability to close windows from superswitch...) commented on by jackrussell3000 - Oh dog. Just found the Super-Escape combo - pls ignore this one! Oh dog. Just found the Super-Escape combo - pls ignore this one! Jun 18, 2009 issue 40 (Add functionality: ability to close windows from superswitch...) reported by jackrussell3000 - Add ability to close/kill(politely) a window when that window is highlighted in superswitcher. As well as gaining the benefit of closing windows when needed, it will also allow us to empty a workspace so that the workspace itself can be deleted via the Super-Delete combo. Since the alphabet keys are used to filter on the available windows we can rule out x (a la vim) or d (as in delete) to go with the super/caps key. Maybe the minus key? Add ability to close/kill(politely) a window when that window is highlighted in superswitcher. As well as gaining the benefit of closing windows when needed, it will also allow us to empty a workspace so that the workspace itself can be deleted via the Super-Delete combo. Since the alphabet keys are used to filter on the available windows we can rule out x (a la vim) or d (as in delete) to go with the super/caps key. Maybe the minus key? May 17, 2009 issue 39 (Windows are focused while passing through) commented on by chatziko - I'm sorry, I meant issue #24 (Super+TAB does not act like ALT+TAB) might be related, even though I'm not sure. I'm sorry, I meant issue #24 (Super+TAB does not act like ALT+TAB) might be related, even though I'm not sure. May 16, 2009 issue 39 (Windows are focused while passing through) commented on by nigel.tao.gnome - Yeah, I've noticed this too. I think you're right -- somebody just has to write the patch. Incidentally, I think that issue #25 is a separate issue. Yeah, I've noticed this too. I think you're right -- somebody just has to write the patch. Incidentally, I think that issue #25 is a separate issue. May 01, 2009 issue 39 (Windows are focused while passing through) reported by chatziko - I like this tool a lot, however there is an issue that makes its use quite difficult. When I traverse the list of windows to find the one I want to see, the ones I simply pass through are actually focused. This has three undesired effects: 1. If starting from a window A, I select a window C passing through B, the "last visited" window will be set to B. In other words, if I press Super-Tab again once, I will see B, not A. But I don't care at all about B, I just passed through it to find C. I believe this is the problem mentioned in issue #25. 2. After finished selecting a window, the Z-order of all windows are passed through is affected. I only wanted to raise one window and leave all others unaffected. Instead, the windows I passed through have now higher Z-order than the window I started from. 3. If some window I pass through is minimized, it will be raised. What steps will reproduce the problem? 1. Open 5 windows, say A to E. The top one is E and the bottom one is A. 2. Keep Super pressed and press Tab 4 times. Now A is on top but below is B,C,D and E is last. This is really counter-intuitive behavior. I only wanted to select A, not bring B,C,D up. Moreover, if B,C,D are minimized, they will be raised. I think the best would be to "highlight" the window while passing through and only focus to it when Super is released. This is exactly what metacity does. Raising all other windows is counter-intuitive. I'm using superswitcher 0.6 (deb package) on ubuntu 9.04. I like this tool a lot, however there is an issue that makes its use quite difficult. When I traverse the list of windows to find the one I want to see, the ones I simply pass through are actually focused. This has three undesired effects: 1. If starting from a window A, I select a window C passing through B, the "last visited" window will be set to B. In other words, if I press Super-Tab again once, I will see B, not A. But I don't care at all about B, I just passed through it to find C. I believe this is the problem mentioned in issue #25. 2. After finished selecting a window, the Z-order of all windows are passed through is affected. I only wanted to raise one window and leave all others unaffected. Instead, the windows I passed through have now higher Z-order than the window I started from. 3. If some window I pass through is minimized, it will be raised. What steps will reproduce the problem? 1. Open 5 windows, say A to E. The top one is E and the bottom one is A. 2. Keep Super pressed and press Tab 4 times. Now A is on top but below is B,C,D and E is last. This is really counter-intuitive behavior. I only wanted to select A, not bring B,C,D up. Moreover, if B,C,D are minimized, they will be raised. I think the best would be to "highlight" the window while passing through and only focus to it when Super is released. This is exactly what metacity does. Raising all other windows is counter-intuitive. I'm using superswitcher 0.6 (deb package) on ubuntu 9.04. Apr 08, 2009 issue 38 (Segfault at startup within enlightenment (e16)) commented on by yuzisee - About those Xlib warnings: Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". I actually get them whenever I run any GUI program. It's harmless and well-documented: http://bbs.archlinux.org/viewtopic.php?id=65403 So they can be safely ignored, ie. they are most likely not the cause of the subsequent: (superswitcher:10741): GLib-CRITICAL : g_ascii_strcasecmp: assertion `s1 != NULL' failed (superswitcher:10741): Wnck-CRITICAL : wnck_workspace_get_number: assertion `WNCK_IS_WORKSPACE (space)' failed Segmentation fault About those Xlib warnings: Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". I actually get them whenever I run any GUI program. It's harmless and well-documented: http://bbs.archlinux.org/viewtopic.php?id=65403 So they can be safely ignored, ie. they are most likely not the cause of the subsequent: (superswitcher:10741): GLib-CRITICAL : g_ascii_strcasecmp: assertion `s1 != NULL' failed (superswitcher:10741): Wnck-CRITICAL : wnck_workspace_get_number: assertion `WNCK_IS_WORKSPACE (space)' failed Segmentation fault Apr 08, 2009 issue 38 (Segfault at startup within enlightenment (e16)) reported by yuzisee - What steps will reproduce the problem? 1. configure xinitrc to exec e16 at startup 2. $startx 3. open a terminal (I use urxvt) 4. $superswitcher What is the expected output? What do you see instead? $ superswitcher Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". (superswitcher:10741): GLib-CRITICAL : g_ascii_strcasecmp: assertion `s1 != NULL' failed (superswitcher:10741): Wnck-CRITICAL : wnck_workspace_get_number: assertion `WNCK_IS_WORKSPACE (space)' failed Segmentation fault What version of the product are you using? On what operating system? Superswitcher 0.6 Archlinux Enlightenment 0.16.8.15 (Composite enabled) gconf 2.24.0 libwnck 2.26.0 dbus-glib 0.78 Please provide any additional information below. What steps will reproduce the problem? 1. configure xinitrc to exec e16 at startup 2. $startx 3. open a terminal (I use urxvt) 4. $superswitcher What is the expected output? What do you see instead? $ superswitcher Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". (superswitcher:10741): GLib-CRITICAL : g_ascii_strcasecmp: assertion `s1 != NULL' failed (superswitcher:10741): Wnck-CRITICAL : wnck_workspace_get_number: assertion `WNCK_IS_WORKSPACE (space)' failed Segmentation fault What version of the product are you using? On what operating system? Superswitcher 0.6 Archlinux Enlightenment 0.16.8.15 (Composite enabled) gconf 2.24.0 libwnck 2.26.0 dbus-glib 0.78 Please provide any additional information below. Apr 07, 2009 issue 21 (Feature request: sticky superswitcher) commented on by fransdejonge - Ok, I hadn't tested that change sufficiently. smacks forehead It interferes with other shortcuts involving alt when used that way. I'd still like to use SuperSwitcher with alt, but that should probably be a separate issue. Ok, I hadn't tested that change sufficiently. smacks forehead It interferes with other shortcuts involving alt when used that way. I'd still like to use SuperSwitcher with alt, but that should probably be a separate issue. Apr 07, 2009 issue 21 (Feature request: sticky superswitcher) commented on by fransdejonge - Ok, for my personal desires I've simply added the XK_Alt_L line to superswitcher.c on line 217. While it's not a visibility toggle, it does presumably remove the need to caps lock+tab. I suppose that have to disable the default Metacity alt+tab handlers, or maybe this overwrites them. I really have no idea. I disabled them before I added this, but if you don't have to do that, all the better. if (!only_trigger_on_caps_lock) { grab (XK_Super_L); grab (XK_Super_R); //include alt grab (XK_Alt_L); } Ok, for my personal desires I've simply added the XK_Alt_L line to superswitcher.c on line 217. While it's not a visibility toggle, it does presumably remove the need to caps lock+tab. I suppose that have to disable the default Metacity alt+tab handlers, or maybe this overwrites them. I really have no idea. I disabled them before I added this, but if you don't have to do that, all the better. if (!only_trigger_on_caps_lock) { grab (XK_Super_L); grab (XK_Super_R); //include alt grab (XK_Alt_L); } Apr 07, 2009 issue 21 (Feature request: sticky superswitcher) commented on by fransdejonge - http://bugzilla.gnome.org/show_bug.cgi?id=570079#c5 "If you want superswitcher you only have to disable Metacity's alt+tab option and make alt-tab load superswitcher; it's pretty trivial. Could be done with a script." Sadly I have no idea how to do that, because I'd really like to. Metacity's alt-tab isn't very useful and getting used to super-tab instead of alt-tab just makes me less compatible with other computers/Windows/Live CDs/etc. http://bugzilla.gnome.org/show_bug.cgi?id=570079#c5 "If you want superswitcher you only have to disable Metacity's alt+tab option and make alt-tab load superswitcher; it's pretty trivial. Could be done with a script." Sadly I have no idea how to do that, because I'd really like to. Metacity's alt-tab isn't very useful and getting used to super-tab instead of alt-tab just makes me less compatible with other computers/Windows/Live CDs/etc. Apr 06, 2009 issue 37 (Typo in autogen.sh) reported by fransdejonge - Not quite sure if this is really the right place for a lousy typo, but I noticed this while building from source. What steps will reproduce the problem? 1. Run autoget.sh without glib-gettext What is the expected output? What do you see instead? Expected: checking for glib-gettext >= 2.2.0... testing glib-gettextize... not found. *Error: You must have glib-gettext >= 2.2.0 installed to build superswitcher. Download the appropriate package for from your distribution or get the source tarball at ftp://ftp.gtk.org/pub/gtk/v2.2/glib-2.2.0.tar.gz Instead: checking for glib-gettext >= 2.2.0... testing glib-gettextize... not found. Error: You must have glib-gettext >= 2.2.0 installed to build superswticher. Download the appropriate package for from your distribution or get the source tarball at ftp://ftp.gtk.org/pub/gtk/v2.2/glib-2.2.0.tar.gz What version of the product are you using? On what operating system? Latest version from SVN (at the time of writing). Not quite sure if this is really the right place for a lousy typo, but I noticed this while building from source. What steps will reproduce the problem? 1. Run autoget.sh without glib-gettext What is the expected output? What do you see instead? Expected: checking for glib-gettext >= 2.2.0... testing glib-gettextize... not found. Error: You must have glib-gettext >= 2.2.0 installed to build superswitcher. Download the appropriate package for from your distribution or get the source tarball at ftp://ftp.gtk.org/pub/gtk/v2.2/glib-2.2.0.tar.gz Instead: checking for glib-gettext >= 2.2.0... testing glib-gettextize... not found. Error: You must have glib-gettext >= 2.2.0 installed to build superswticher. Download the appropriate package for from your distribution or get the source tarball at ftp://ftp.gtk.org/pub/gtk/v2.2/glib-2.2.0.tar.gz What version of the product are you using? On what operating system? Latest version from SVN (at the time of writing). Mar 30, 2009 issue 36 (superswitcher: error while loading shared libraries: libwnck...) Status changed by nigel.tao.gnome - That's odd, it works for me, on Ubuntu Hardy 8.04. Step 2 should have failed if you didn't have libwnck-dev. Perhaps you (or your desktop environment) are overriding a pkg-config or LD_LIBRARY_PATH related environment variable? I'm going to close this issue as WontFix, since I am unable to reproduce it (and hence can't "fix" it). Status: WontFix That's odd, it works for me, on Ubuntu Hardy 8.04. Step 2 should have failed if you didn't have libwnck-dev. Perhaps you (or your desktop environment) are overriding a pkg-config or LD_LIBRARY_PATH related environment variable? I'm going to close this issue as WontFix, since I am unable to reproduce it (and hence can't "fix" it). Status: WontFix Mar 24, 2009 issue 36 (superswitcher: error while loading shared libraries: libwnck...) reported by hemant.egroups - What steps will reproduce the problem? 1. Download tar.gz source on ubuntu Hardy 8 2. ./configure, make and sudo make install 3. run superswitcher. 4. Error for missing libwnck 5. Download and install libwnck and libwnck-dev. 6. Make clean and rebuild superswitcher. 7. Same error as step 4. What is the expected output? What do you see instead? Superswitcher should start. Instead I see the error "superswitcher: error while loading shared libraries: libwnck-1.so.18" What version of the product are you using? On what operating system? 0.6 on Ubuntu Hardy. (using fluxbox WM) Please provide any additional information below. the .deb package works properly, but I need the source to rebuild, since I want to change it for the popup to appear only after hitting alt+tab. What steps will reproduce the problem? 1. Download tar.gz source on ubuntu Hardy 8 2. ./configure, make and sudo make install 3. run superswitcher. 4. Error for missing libwnck 5. Download and install libwnck and libwnck-dev. 6. Make clean and rebuild superswitcher. 7. Same error as step 4. What is the expected output? What do you see instead? Superswitcher should start. Instead I see the error "superswitcher: error while loading shared libraries: libwnck-1.so.18" What version of the product are you using? On what operating system? 0.6 on Ubuntu Hardy. (using fluxbox WM) Please provide any additional information below. the .deb package works properly, but I need the source to rebuild, since I want to change it for the popup to appear only after hitting alt+tab. Mar 08, 2009 issue 35 (Feature: work with mouse (customize)) commented on by nigel.tao.gnome - It's not discoverable, but you can roll around workspaces by mouse-wheel'ing over the column headers (the workspace thumbnails that say F1, F2, etc). It's not discoverable, but you can roll around workspaces by mouse-wheel'ing over the column headers (the workspace thumbnails that say F1, F2, etc). Mar 05, 2009 issue 35 (Feature: work with mouse (customize)) reported by da.mi.spirit - so far the Super-Tab and Super-MouseWheel does the same thing but I'm looking into that maybe could customize what key combination or mouse wheel does what job ? that i could roll around the workspaces without having to use the other hand for arrow keys. so far the Super-Tab and Super-MouseWheel does the same thing but I'm looking into that maybe could customize what key combination or mouse wheel does what job ? that i could roll around the workspaces without having to use the other hand for arrow keys. Feb 19, 2009 issue 28 (Too much RAM needed) commented on by robert.sevcik - PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 14390 robajz 20 0 20060 11m 7284 S 0 1.1 0:01.02 superswitcher PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 14390 robajz 20 0 20060 11m 7284 S 0 1.1 0:01.02 superswitcher Feb 19, 2009 issue 20 (segfault randomly) commented on by robert.sevcik - Hey I think the randomness is caused by windows that have "Always on visible workspace" option set - as commented here http://code.google.com/p/superswitcher/issues/detail?id=10 Hey I think the randomness is caused by windows that have "Always on visible workspace" option set - as commented here http://code.google.com/p/superswitcher/issues/detail?id=10 Feb 19, 2009 issue 10 (Sticky windows only show up on Desktop 1) commented on by robert.sevcik - Hi, I've set my pidgin roster to be on the visible workspace and this crashed the superswitcher: (superswitcher:14363): Wnck-CRITICAL : wnck_workspace_get_number: assertion `WNCK_IS_WORKSPACE (space)' failed Segmentation fault SuperSwitcher version 0.6 on Ubuntu Hardy I should say I have two screens set up LVDS and AVG of the same card Cheers. Hi, I've set my pidgin roster to be on the visible workspace and this crashed the superswitcher: (superswitcher:14363): Wnck-CRITICAL : wnck_workspace_get_number: assertion `WNCK_IS_WORKSPACE (space)' failed Segmentation fault SuperSwitcher version 0.6 on Ubuntu Hardy I should say I have two screens set up LVDS and AVG of the same card Cheers. Feb 08, 2009 issue 34 (Switch to application by mouseover) reported by moritz_k...@web.de - Now you have to click to switch to an application of the list. But it would be better if the behaviour would be similar to TaskSwitchXP (http://www.ntwind.com/software/taskswitchxp.html). With TaskSwitchXP switching applications is possible by mouseover. Now you have to click to switch to an application of the list. But it would be better if the behaviour would be similar to TaskSwitchXP (http://www.ntwind.com/software/taskswitchxp.html). With TaskSwitchXP switching applications is possible by mouseover. Dec 14, 2008 issue 24 (Super+TAB does not act like ALT+TAB) commented on by nigel.tao.gnome - I use metacity. Superswitcher is known to crash relatively frequently on Compiz. I'm told that superswitcher works with KDE 3's default window manager (I forget what it's called). I'm not sure about the less common WMs. I use metacity. Superswitcher is known to crash relatively frequently on Compiz. I'm told that superswitcher works with KDE 3's default window manager (I forget what it's called). I'm not sure about the less common WMs. Dec 11, 2008 issue 24 (Super+TAB does not act like ALT+TAB) commented on by phillip.c.warner - What Window Manager are y'all testing Super Switcher on? When I get a chance I will test Super Switcher on fluxbox again. What Window Manager are y'all testing Super Switcher on? When I get a chance I will test Super Switcher on fluxbox again. Dec 11, 2008 issue 24 (Super+TAB does not act like ALT+TAB) commented on by nigel.tao.gnome - Super-Up and Super-Down is supposed to go through the windows in list order, but Super-Tab is supposed to be in most-recently-used order, like Alt-Tab. Still, as I mentioned earlier, I'm unable to reproduce phillip.c.warner's observed behavior. Super-Up and Super-Down is supposed to go through the windows in list order, but Super-Tab is supposed to be in most-recently-used order, like Alt-Tab. Still, as I mentioned earlier, I'm unable to reproduce phillip.c.warner's observed behavior. Dec 10, 2008 issue 24 (Super+TAB does not act like ALT+TAB) commented on by lambchop468 - this behavior is supposed to be expected I think. Super switcher is supposed to go through your windows in a list instead of last focused order. this behavior is supposed to be expected I think. Super switcher is supposed to go through your windows in a list instead of last focused order. Nov 07, 2008 issue 32 (Doesn't run on xfce4) commented on by slackorama - Thanks for reply and sorry for lack of details. I'm running: Xfce 4 Desktop Environment version 4.4.1 (Xfce 4.4) on Ubuntu 7.10 Didn't build xfce from source, used the repos version. Superswitcher works fine with kde on this box. Thanks for reply and sorry for lack of details. I'm running: Xfce 4 Desktop Environment version 4.4.1 (Xfce 4.4) on Ubuntu 7.10 Didn't build xfce from source, used the repos version. Superswitcher works fine with kde on this box. Nov 07, 2008 issue 32 (Doesn't run on xfce4) commented on by nigel.tao.gnome - Can you give more specific information about what version of XFCE you're running, and what distro you're using (or did you build XFCE from source)? Can you give more specific information about what version of XFCE you're running, and what distro you're using (or did you build XFCE from source)? Nov 05, 2008 issue 32 (Doesn't run on xfce4) reported by slackorama - What steps will reproduce the problem? 1. run autogen and make per instructions 2. start up superswitcher Running superswitcher while on xfce4 I get the following error: % superswitcher (superswitcher:5448): Wnck-WARNING : Property _NET_WM_NAME contained invalid UTF-8 (superswitcher:5448): GLib-CRITICAL : g_ascii_strcasecmp: assertion `s1 != NULL' failed Super-Tab doesn't work at this point. What steps will reproduce the problem? 1. run autogen and make per instructions 2. start up superswitcher Running superswitcher while on xfce4 I get the following error: % superswitcher (superswitcher:5448): Wnck-WARNING : Property _NET_WM_NAME contained invalid UTF-8 (superswitcher:5448): GLib-CRITICAL *: g_ascii_strcasecmp: assertion `s1 != NULL' failed Super-Tab doesn't work at this point. Sep 30, 2008 issue 9 (Feature Request: quick shortcuts) commented on by phairland - I think that's a really good idea. What about making shortcuts like this: super + 1 = firefox super + 2 = console or in consecutive order like: super + 1 = opened window number 1 super + 2 = opened window number 2 I think that's a really good idea. What about making shortcuts like this: super + 1 = firefox super + 2 = console or in consecutive order like: super + 1 = opened window number 1 super + 2 = opened window number 2 Sep 07, 2008 issue 31 (Compiz : only one desktop is shown) commented on by achrafcherti - Thanks for the reply ! I'll test the latest version to see ^_^ Thanks for the reply ! I'll test the latest version to see ^_^

issue 39 (Windows are focused while passing through) reported by chatziko - I like this tool a lot, however there is an issue that makes its use quite difficult. When I traverse the list of windows to find the one I want to see, the ones I simply pass through are actually focused. This has three undesired effects: 1. If starting from a window A, I select a window C passing through B, the "last visited" window will be set to B. In other words, if I press Super-Tab again once, I will see B, not A. But I don't care at all about B, I just passed through it to find C. I believe this is the problem mentioned in issue #25. 2. After finished selecting a window, the Z-order of all windows are passed through is affected. I only wanted to raise *one* window and leave all others unaffected. Instead, the windows I passed through have now higher Z-order than the window I started from. 3. If some window I pass through is minimized, it will be raised. What steps will reproduce the problem? 1. Open 5 windows, say A to E. The top one is E and the bottom one is A. 2. Keep Super pressed and press Tab 4 times. Now A is on top but below is B,C,D and E is last. This is really counter-intuitive behavior. I only wanted to select A, not bring B,C,D up. Moreover, if B,C,D are minimized, they will be raised. I think the best would be to "highlight" the window while passing through and only focus to it when Super is released. This is exactly what metacity does. Raising all other windows is counter-intuitive. I'm using superswitcher 0.6 (deb package) on ubuntu 9.04.

I like this tool a lot, however there is an issue that makes its use quite difficult. When I traverse the list of windows to find the one I want to see, the ones I simply pass through are actually focused. This has three undesired effects: 1. If starting from a window A, I select a window C passing through B, the "last visited" window will be set to B. In other words, if I press Super-Tab again once, I will see B, not A. But I don't care at all about B, I just passed through it to find C. I believe this is the problem mentioned in issue #25. 2. After finished selecting a window, the Z-order of all windows are passed through is affected. I only wanted to raise *one* window and leave all others unaffected. Instead, the windows I passed through have now higher Z-order than the window I started from. 3. If some window I pass through is minimized, it will be raised. What steps will reproduce the problem? 1. Open 5 windows, say A to E. The top one is E and the bottom one is A. 2. Keep Super pressed and press Tab 4 times. Now A is on top but below is B,C,D and E is last. This is really counter-intuitive behavior. I only wanted to select A, not bring B,C,D up. Moreover, if B,C,D are minimized, they will be raised. I think the best would be to "highlight" the window while passing through and only focus to it when Super is released. This is exactly what metacity does. Raising all other windows is counter-intuitive. I'm using superswitcher 0.6 (deb package) on ubuntu 9.04.

Last 30 days

Older