Re: Upcoming 0.61.2 realease (was: call for patches)
Changes from 0.61.1 to 0.61.2: - added the ja_JP nls directory - general code cleanups - blackbox-nls.hh is always generated even if --disable-nls is used. This allows us to not have all of those hideous #ifdef NLS chunks. Nothing to worry about, if you do not want NLS this does not affect you - Workspace::placeWindow() cleanups. Also a speed bump from reducing the use of iterator-current() and changing the delta from 1 to 8 - cleanups to compile with g++ 3.0 - make distclean actually removes Translation.m and blackbox-nls.hh - fixed a desciptor leak in BScreen::parseMenuFile, seems opendir lacked a matching closedir. Is my current changelog. If anything in that list is not clear, please speak up. If something should be in that list, also speak up. Oh yeah, forgot this one: - transient window handling code in Workspace::removeWindow() so transients give focus back to their parents properly. The code originally handled sloppy focus then transient windows, so we just flopped the if/elsif. This is immediately noticable with web browsers and their open location windows.
Re: Upcoming 0.61.2 realease (was: call for patches)
On Tue, Dec11,01 09:01, Sean 'Shaleh' Perry wrote: Changes from 0.61.1 to 0.61.2: - added the ja_JP nls directory - general code cleanups - blackbox-nls.hh is always generated even if --disable-nls is used. This allows us to not have all of those hideous #ifdef NLS chunks. Nothing to worry about, if you do not want NLS this does not affect you - Workspace::placeWindow() cleanups. Also a speed bump from reducing the use of iterator-current() and changing the delta from 1 to 8 - cleanups to compile with g++ 3.0 - make distclean actually removes Translation.m and blackbox-nls.hh - fixed a desciptor leak in BScreen::parseMenuFile, seems opendir lacked a matching closedir. Is my current changelog. If anything in that list is not clear, please speak up. If something should be in that list, also speak up. Oh yeah, forgot this one: - transient window handling code in Workspace::removeWindow() so transients give focus back to their parents properly. The code originally handled sloppy focus then transient windows, so we just flopped the if/elsif. This is immediately noticable with web browsers and their open location windows. What about the workspace change bugs? And has there been any devel on the smart placement changes? DC -- Derek Cunningham [EMAIL PROTECTED] All men by nature desire to know. -- Aristotle. Registered Linux User Number 195825
Re: Upcoming 0.61.2 realease (was: call for patches)
What about the workspace change bugs? And has there been any devel on the smart placement changes? What workspace bugs? placeWindow() is the smart placement code. What else was supposed to happen there?
Re: Upcoming 0.61.2 realease (was: call for patches)
On Tue, Dec11,01 09:12, Sean 'Shaleh' Perry wrote: What about the workspace change bugs? And has there been any devel on the smart placement changes? What workspace bugs? placeWindow() is the smart placement code. What else was supposed to happen there? Well... I've never experienced it... and so in my mind it's more the fabled workspace change bug but there's been lots of discussion on it... *shrug* I was just wondering. :) DC -- Derek Cunningham [EMAIL PROTECTED] All men by nature desire to know. -- Aristotle. Registered Linux User Number 195825
Re: Upcoming 0.61.2 realease (was: call for patches)
On Tue, 2001-12-11 at 11:30, Derek Cunningham wrote: On Tue, Dec11,01 09:12, Sean 'Shaleh' Perry wrote: What workspace bugs? placeWindow() is the smart placement code. What else was supposed to happen there? Well... I've never experienced it... and so in my mind it's more the fabled workspace change bug but there's been lots of discussion on it... *shrug* I was just wondering. :) Well, I'll probably get flamed for this, but I don't see that this is a bug with Blackbox. There's a similar workspace changing patch for the mouse wheel when used on the root window. I tested this patch on one of my systems and regardless of how quickly workspaces are changed or what programs are running on them, Blackbox will not crash. This tells me that the problem most likely lies with BBKeys not with Blackbox. Jamin W. Collins
Re: Upcoming 0.61.2 realease (was: call for patches)
There's a flaw in LinkedList also xOr talked with Raven on July
28th about this one Pasting from his e-mail
I've found a problem in LinkedList.cc:
check out line 164:
__llist_node *nnode = new __llist_node, *inode =
_first-getNext();
how this function works is, if 0 is passed in as the index to insert to,
then the new item is added at the top of the list.
So, the highest in the list one can insert after the top is, of course,
at
index 1.
The above line sets inode to _first-getNext, the _second_ element in
the
linked list.
If an index of 1 is passed in, then inode is not modified and the new
node
is added after inode.
This makes the new node go into index 2, not index 1.
A simple fix for this is to change line 164 to:
__llist_node *nnode = new __llist_node, *inode = _first;
This probly affects most of the bbtools and maybe blackbox itself.. as
all
insertions into the linked list have been at (index+1).
On Tue, 2001-12-11 at 11:54, Sean 'Shaleh' Perry wrote:
Changes from 0.61.1 to 0.61.2:
- added the ja_JP nls directory
- general code cleanups
- blackbox-nls.hh is always generated even if --disable-nls is used.
This allows us to not have all of those hideous #ifdef NLS chunks.
Nothing to worry about, if you do not want NLS this does not affect you
- Workspace::placeWindow() cleanups. Also a speed bump from reducing the
use of iterator-current() and changing the delta from 1 to 8
- cleanups to compile with g++ 3.0
- make distclean actually removes Translation.m and blackbox-nls.hh
- fixed a desciptor leak in BScreen::parseMenuFile, seems opendir
lacked a matching closedir.
Is my current changelog. If anything in that list is not clear, please speak
up. If something should be in that list, also speak up.
--
%--%
Jason Kasper (vanRijn)
bash$ :(){ :|:};:
Numbers 6:24-26
Re: Upcoming 0.61.2 realease (was: call for patches)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Is there support for ALT+Click on windows to bring them forward regardless of Lock keys? (or is it considered a feature to not be able to ALT+click while either NUM/CAPS lock are on?) On Tuesday 11 December 2001 11:46, Jamin W. Collins wrote: On Tue, 2001-12-11 at 10:34, Sean 'Shaleh' Perry wrote: So, 0.61.2 is almost ready to be released screaming into the world. If anyone has a patch floating around that fixes some problem I would love to hear about it. The recent open file descriptor bug shows how much the community has depended on the memory of this list to find bugs. So, is there a list of what's planned to be fixed in the soon to be release 0.61.2? Jamin W. Collins - -- [scott] :: ein kalter Tod für den sprecher von Lügen -BEGIN PGP SIGNATURE- Version: PGP 6.5.8 iQA/AwUBPAzCwGkF5Bwr8hiXEQL+/ACguaZjVhRZX4LPt1dOxANa6FrbVw4AnRhV Mx+dtgVBJYEK8E6Wr0qPcbog =yAdf -END PGP SIGNATURE-
