Patch for bbpager 0.3.0
This is against the Debian-packaged bbpager 0.3.0... it adds support for an
'-r[cfile]' option to tell bbpager where to find the window manager's rc
file.
This allows bbpager to deal with the fact that all the blackbox forks don't
keep their rc files in the same place. As long as this bbtool has to
actually go out and figure out what style file you're using, this will be a
problem.
With some people using blackbox, and some using openbox, and others using
gods only know what, this might be useful.
--
Marc Wilson
[EMAIL PROTECTED]
diff -urN bbpager-0.3.0/Baseresource.cc bbpager-0.3.0-new/Baseresource.cc
--- bbpager-0.3.0/Baseresource.cc Tue Oct 3 12:05:18 2000
+++ bbpager-0.3.0-new/Baseresource.cc Mon Jun 3 19:14:07 2002
@@ -38,7 +38,11 @@
} else {
char *homedir = getenv(HOME);
bbtool-config_filename = new char[strlen(homedir) + 32];
-sprintf(bbtool-config_filename, %s/.blackboxrc, homedir);
+if (bbtool-norc_file) {
+sprintf(bbtool-config_filename, %s/.blackboxrc, homedir);
+} else {
+sprintf(bbtool-config_filename, %s/%s, homedir, bbtool-rc_file);
+}
if ((resource_db = XrmGetFileDatabase(bbtool-config_filename))!=NULL) {
ReadBlackboxResource();
ResourceType=BLACKBOX;
diff -urN bbpager-0.3.0/Basewindow.cc bbpager-0.3.0-new/Basewindow.cc
--- bbpager-0.3.0/Basewindow.cc Tue Oct 3 12:05:39 2000
+++ bbpager-0.3.0-new/Basewindow.cc Mon Jun 3 19:09:02 2002
@@ -51,6 +51,8 @@
decorated=options-decorated;
config_file=options-config_file;
nobb_config=options-nobb_config;
+ rc_file=options-rc_file;
+ norc_file=options-norc_file;
current_screen_info = getScreenInfo(DefaultScreen(getXDisplay()));
XSetErrorHandler((XErrorHandler) handleXErrors);
diff -urN bbpager-0.3.0/Basewindow.hh bbpager-0.3.0-new/Basewindow.hh
--- bbpager-0.3.0/Basewindow.hh Tue Oct 3 12:05:50 2000
+++ bbpager-0.3.0-new/Basewindow.hh Mon Jun 3 19:09:32 2002
@@ -68,6 +68,8 @@
char *style_file;
char *spooldir;
bool nobb_config;
+ char *rc_file;
+ bool norc_file;
bool withdrawn;
bool shape;
bool decorated;
diff -urN bbpager-0.3.0/debian/changelog bbpager-0.3.0-new/debian/changelog
--- bbpager-0.3.0/debian/changelog Tue Jun 4 00:54:27 2002
+++ bbpager-0.3.0-new/debian/changelog Mon Jun 3 19:22:19 2002
@@ -1,3 +1,9 @@
+bbpager (0.3.0-1.1.1) unstable; urgency=low
+
+ * add -r[cfile] option to allow use with openbox
+
+ -- Marc Wilson [EMAIL PROTECTED] Mon, 3 Jun 2002 19:22:02 -0800
+
bbpager (0.3.0-1.1) unstable; urgency=low
* NMU
diff -urN bbpager-0.3.0/main.cc bbpager-0.3.0-new/main.cc
--- bbpager-0.3.0/main.cc Tue Oct 3 12:07:09 2000
+++ bbpager-0.3.0-new/main.cc Mon Jun 3 19:07:15 2002
@@ -25,16 +25,17 @@
void Usage()
{
fprintf(stderr,\n%s version %s \n,BBTOOL,BBTOOL_VERSION);
- fprintf(stderr,Usage: %s [options]\n,BBTOOL);
+ fprintf(stderr,Usage: %s [options]\n,BBTOOL);
fprintf(stderr,Options:\n);
- fprintf(stderr,-display display name X server to connect to\n);
+ fprintf(stderr,-display display name X server to connect to\n);
fprintf(stderr,-c[onfig] filenameAlternate config file\n);
+ fprintf(stderr,-r[cfile] filenamewindow manager rc file\n);
fprintf(stderr,-n[obb] Fall back on default
configuration\n);
fprintf(stderr,-v[ersion] Display version number\n);
fprintf(stderr,-h[elp] Display this help\n);
fprintf(stderr,-geom[etry] geometry Set geometry of window\n);
- fprintf(stderr,-d[ecorated] Show 'normal' decorated
window\n);
- fprintf(stderr,-w[withdrawn] Place bbtool in the Slit\n);
+ fprintf(stderr,-d[ecorated]Show 'normal' decorated window\n);
+ fprintf(stderr,-w[withdrawn] Place bbtool in the Slit\n);
fprintf(stderr,-s[hape]Don't display groundplate\n\n);
}
@@ -49,6 +50,8 @@
options.shape=False;
options.config_file=NULL;
options.nobb_config=False;
+ options.rc_file=NULL;
+ options.norc_file=True;
options.decorated=False;
@@ -61,6 +64,11 @@
else if ((!strcmp(argv[i],-config))|(!strcmp(argv[i],-c))) {
if(++i==argc) { Usage(); exit(2); };
options.config_file=argv[i];
+}
+else if ((!strcmp(argv[i],-rcfile))|(!strcmp(argv[i],-r))) {
+ if(++i==argc) { Usage(); exit(2); };
+ options.norc_file=False;
+ options.rc_file=argv[i];
}
else if ((!strcmp(argv[i],-nobb))|(!strcmp(argv[i],-n))) {
options.nobb_config=True;
diff -urN bbpager-0.3.0/main.hh bbpager-0.3.0-new/main.hh
--- bbpager-0.3.0/main.hh Tue Oct 3 12:07:20 2000
+++ bbpager-0.3.0-new/main.hh Mon Jun 3 19:04:21 2002
@@ -27,6 +27,8 @@
char *geometry;
char *config_file;
bool nobb_config;
+ char *rc_file;
+ bool norc_file;
char *display_name;
bool
Re: BBConf and Meta keys
er. So, I was just going to ask for a patch. =:) But it looks like
bbconf is working correctly?
On Mon, 2002-06-03 at 15:01, Jamin W.Collins wrote:
On Mon, 03 Jun 2002 10:02:06 -0700 (PDT)
Sean 'Shaleh' Perry [EMAIL PROTECTED] wrote:
I just played around with bbconf and it does read my meta key. Dunno
why Jamin is having problems.
Looks like the problem was due to my XF86Config-4 file (carry over from
Red Hat configuration). The keyboard was set to pc101 instead of pc104.
It's strange though that xev was seeing things correctly when I assigned
the keys via xmodmap, but bbconf wasn't.
--
Jamin W. Collins
--
,-//
| Jason 'vanRijn' Kasper :: Numbers 6:24-26
`
| All brontosauruses are thin at one end, much MUCH thicker
| in the middle, and then thin again at the far end. That is
| the theory that I have and which is mine, and what it is too.
,
| bash$ :(){ :|:};:
`--//
Re: BBConf and Meta keys
On 04 Jun 2002 07:49:55 -0400 Jason 'vanRijn' Kasper [EMAIL PROTECTED] wrote: er. So, I was just going to ask for a patch. =:) But it looks like bbconf is working correctly? Well, yea. But, any ideas why it wouldn't see keys (assigned via xmodmap) that xev does? -- Jamin W. Collins
Re: BBConf and Meta keys
Nope. =:) The keygrabber widget is one I snarfed from kde's tree and I
had to modify it slightly to get it to work, being that it isn't running
in a KApplication. Chances are, I missed something that's otherwise
there in a running KDE environment.
Patches accepted here. =:)
On Tue, 2002-06-04 at 08:11, Jamin W.Collins wrote:
On 04 Jun 2002 07:49:55 -0400
Jason 'vanRijn' Kasper [EMAIL PROTECTED] wrote:
er. So, I was just going to ask for a patch. =:) But it looks like
bbconf is working correctly?
Well, yea. But, any ideas why it wouldn't see keys (assigned via xmodmap)
that xev does?
--
Jamin W. Collins
--
,-//
| Jason 'vanRijn' Kasper :: Numbers 6:24-26
`
| All brontosauruses are thin at one end, much MUCH thicker
| in the middle, and then thin again at the far end. That is
| the theory that I have and which is mine, and what it is too.
,
| bash$ :(){ :|:};:
`--//
Fwd: From Argentina..
-- Forwarded Message -- Subject: From Argentina.. Date: 04 Jun 2002 09:31:08 -0300 From: rkc stan [EMAIL PROTECTED] To: [EMAIL PROTECTED] Hello, im the most fanatic user of bb! Im the spanish webmaster of XFree86, im help MandrakeSoft with some translations, also i translated for Gnu. I want to help you. I can help, translating to the Spanish, any type of documents, or what you wish. I writing help texts in Spanish, about blackbox (configuration, styles, etc etc). Best regards, Roman, from Argentina.. _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com --- -- Bradley T. Hughes - bhughes at trolltech.com Trolltech AS - Waldemar Thranes gt. 98 N-0175 Oslo, Norway
Re: BBConf and Meta keys
On 04-Jun-2002 Jason 'vanRijn' Kasper wrote: Nope. =:) The keygrabber widget is one I snarfed from kde's tree and I had to modify it slightly to get it to work, being that it isn't running in a KApplication. Chances are, I missed something that's otherwise there in a running KDE environment. Patches accepted here. =:) Jamin, if you try out an app like 'kate' it has a very similar key grabber. That would help track down the problem.
alpha8 released
After the recent bug squashes we figured it was time for a new alpha. Please see the release for details. As always http://sf.net/projects/blackboxwm
Blackbox alpha8
Hi. Would someone correct this problem: alpha8 identifies itself as alpha7. It took me 15min to track the problem down, to the blackbox binary file: #./blackbox-0.65.0alpha8/src/blackbox --help Blackbox 0.65.0alpha7 : (c) 2001 - 2002 Sean 'Shaleh' Perry 1997 - 2000, 2002 Brad Hughes ... Martin -- Jeg har det med min rumlige frihed som jeg har lagt mærke til at mænd har det med deres testikler. Jeg vugger den som et spædbarn, og tilbeder den som en gudinde. Smilla Jaspersen
Re: Blackbox alpha8
On 04-Jun-2002 Martin Ehmsen wrote: Hi. Would someone correct this problem: alpha8 identifies itself as alpha7. It took me 15min to track the problem down, to the blackbox binary file: #./blackbox-0.65.0alpha8/src/blackbox --help Blackbox 0.65.0alpha7 : (c) 2001 - 2002 Sean 'Shaleh' Perry 1997 - 2000, 2002 Brad Hughes ... dammit, silly me. I even ran autoconf but forgot to change the number. Doh! The answer is edit configure.in, change the version at the top, run autoconf. The run configure and build as usual.
Re: BBConf and Meta keys
On Tue, 04 Jun 2002 07:45:46 -0700 (PDT) Sean 'Shaleh' Perry [EMAIL PROTECTED] wrote: Jamin, if you try out an app like 'kate' it has a very similar key grabber. That would help track down the problem. Same exact problem exists in 'kate'. If the keyboard is set to pc-101 then regardless of whether the keys are defined and seen by 'xev' properly, they are not seen by 'kate'. -- Jamin W. Collins
Re: BBConf and Meta keys
Yay! Inherited bug! =:D
On Tue, 2002-06-04 at 18:04, Jamin W.Collins wrote:
On Tue, 04 Jun 2002 07:45:46 -0700 (PDT)
Sean 'Shaleh' Perry [EMAIL PROTECTED] wrote:
Jamin, if you try out an app like 'kate' it has a very similar key
grabber. That would help track down the problem.
Same exact problem exists in 'kate'. If the keyboard is set to pc-101
then regardless of whether the keys are defined and seen by 'xev'
properly, they are not seen by 'kate'.
--
Jamin W. Collins
--
,-//
| Jason 'vanRijn' Kasper :: Numbers 6:24-26
`
| All brontosauruses are thin at one end, much MUCH thicker
| in the middle, and then thin again at the far end. That is
| the theory that I have and which is mine, and what it is too.
,
| bash$ :(){ :|:};:
`--//
alpha8 window placement problem
i've noticed with alpha8 that new windows are placed over shaded windows. i'm using right to left and top to bottom window placement. on an empty workspace i open a new window. it's placed in the correct position. i shade it and open another new window, and it's placed right on top of the shaded one. pervious releases would place the new window directly below the shaded window. is this intended? dan
Re: BBConf and Meta keys
On Tue, Jun 04, 2002 at 06:18:46PM -0400, Jason 'vanRijn' Kasper wrote:
Yay! Inherited bug! =:D
I don't think this is a bug at all. If X doesn't recognise the
keypresses how are the applications supposed to get a key press event
(hint: they dont). xev uses some underneath magic, but just cuz it shows
the key doesn't mean its modmapped (i.e. mapped to something other than
a keycode, i.e. usable). I think that if you have your X server set up
to not use those keys yo shouldn't expect it to use them..
On Tue, 2002-06-04 at 18:04, Jamin W.Collins wrote:
On Tue, 04 Jun 2002 07:45:46 -0700 (PDT)
Sean 'Shaleh' Perry [EMAIL PROTECTED] wrote:
Jamin, if you try out an app like 'kate' it has a very similar key
grabber. That would help track down the problem.
Same exact problem exists in 'kate'. If the keyboard is set to pc-101
then regardless of whether the keys are defined and seen by 'xev'
properly, they are not seen by 'kate'.
--
Jamin W. Collins
--
,-//
| Jason 'vanRijn' Kasper :: Numbers 6:24-26
`
| All brontosauruses are thin at one end, much MUCH thicker
| in the middle, and then thin again at the far end. That is
| the theory that I have and which is mine, and what it is too.
,
| bash$ :(){ :|:};:
`--//
xOr
--
I am damn unsatisfied to be killed in this way.
msg07242/pgp0.pgp
Description: PGP signature
Re: alpha8 window placement problem
On Tue, Jun 04, 2002 at 09:21:52PM -0700, Sean 'Shaleh' Perry wrote: yep, it was discussed on this list about a week ago and has been in cvs since. The idea is according to the ICCCM and other standards a shaded window is in the iconic state. Most window managers ignore icons. From my own experience and talking to users people like shaded windows but find they do not help much because new window placement considered them. So they still wanted iconification. The hope is that allowing people to shade a window and have it act like an icon and thus be ignored may reduce the desire for different icon access. I use shaded windows as a medium-state between full and iconified windows. I can still cycle to them, I can _see_ them on the screen, and they can still accepts keyboard input. I do not like the new behaviour, as shaded windows now lose their visual indication of the window's presence. If one wants to hide a window completely, shouldn't one jsut iconify it? The window placement only considers the title bar of the shaded window, so the difference is only minimal (visually, that is), is it not? Cheers, Tim
Re: BBConf and Meta keys
On Wed, 2002-06-05 at 16:01, xOr wrote: On Tue, Jun 04, 2002 at 06:18:46PM -0400, Jason 'vanRijn' Kasper wrote: Yay! Inherited bug! =:D I don't think this is a bug at all. If X doesn't recognise the keypresses how are the applications supposed to get a key press event (hint: they dont). xev uses some underneath magic, but just cuz it shows the key doesn't mean its modmapped (i.e. mapped to something other than a keycode, i.e. usable). I think that if you have your X server set up to not use those keys yo shouldn't expect it to use them.. I have my win keys mapped to mod3 - they work fine with bbkeys, but bbconf still won't pick them up. I've tried just about every different keyboard map in my XF86Config, and pc104 doesn't actually make it work either. I just manually modify my bbkeysrc, so it works fine with meta keys, menu key, etc, but bbconf still won't recognise them. Matt
Re: alpha8 window placement problem
I looked through my blackbox mboxes, and didn't see the thread, but I did see it in the ChangeLog. I fthis now means that shaded windows are iconified, whouldn't it appear in the workspaces Icons menu? I often find myself shading a window that I'm working in, opening another term and then going back to my first term. if the windows happen to be the same size (which my terms are) then i have to close the unshaded one, or alt + tab through everything on the workspace. dan * Sean 'Shaleh' Perry ([EMAIL PROTECTED]) wrote: On 05-Jun-2002 dan radom wrote: i've noticed with alpha8 that new windows are placed over shaded windows. i'm using right to left and top to bottom window placement. on an empty workspace i open a new window. it's placed in the correct position. i shade it and open another new window, and it's placed right on top of the shaded one. pervious releases would place the new window directly below the shaded window. is this intended? yep, it was discussed on this list about a week ago and has been in cvs since. The idea is according to the ICCCM and other standards a shaded window is in the iconic state. Most window managers ignore icons. From my own experience and talking to users people like shaded windows but find they do not help much because new window placement considered them. So they still wanted iconification. The hope is that allowing people to shade a window and have it act like an icon and thus be ignored may reduce the desire for different icon access. Again in my own use and experience this patch simple means that the new windows do not cascade (tile) as fast as they used to.
Re: alpha8 window placement problem
On Tue, Jun 04, 2002 at 09:53:34PM -0700, Sean 'Shaleh' Perry wrote: I use shaded windows as a medium-state between full and iconified windows. I can still cycle to them, I can _see_ them on the screen, and they can still accepts keyboard input. I do not like the new behaviour, as shaded windows now lose their visual indication of the window's presence. If one wants to hide a window completely, shouldn't one jsut iconify it? The window placement only considers the title bar of the shaded window, so the difference is only minimal (visually, that is), is it not? My usage pattern is one workspace without about 4 or 5 browsers shaded at various web sites. Due to the window size opening any new window will hit the tiled placement code. Let's use this for a bit and see what happens. It is literally one line of code, so if the decision is not in favour of it it is easily removed. Could always add another 9 lines and make it an option in the Window Placement menu.. :) Ignore Sticky Windows would go well beside Ignore Full-Maximized Windows. you'll actually have a patch for this coming your way in the next few days.. =] xOr -- I am damn unsatisfied to be killed in this way. msg07248/pgp0.pgp Description: PGP signature
Re: alpha8 window placement problem
Could always add another 9 lines and make it an option in the Window Placement menu.. :) Ignore Sticky Windows would go well beside Ignore Full-Maximized Windows. you'll actually have a patch for this coming your way in the next few days.. =] I will remove it before it becomes an option. Let me repeat -- the rc format will not change at this time. And it is more like 20 lines once you implement rc reading and writing.
