On 09-Jun-2002 Robert wrote:
> Observation:
>
> Perusing the blackbox code I see that in
> BColor &BColor::operator=(const BColor &c)
> there's no coping with the consequences of a self-assignment - it may be
> that that's impossible, but if it were then the code in that member
> function looks
On Sat, Jun 08, 2002 at 01:32:38PM -0400, [EMAIL PROTECTED] wrote:
> I'm running a transparent aterm window, and want it borderless as
> well. I downloaded bbappconf, edited bbappconf.bb so that class =
> XTerm, name = aterm, and decorless = true. Still no decorless window.
> I've tried to make
Observation:
Perusing the blackbox code I see that in
BColor &BColor::operator=(const BColor &c)
there's no coping with the consequences of a self-assignment - it may be
that that's impossible, but if it were then the code in that member
function looks pretty terminal!
The old style to avoid s
Hi there, (xOr)
I have applied two different key-bindings for "NextWindow"
manually in the .bbkeysrc, but this is not possible using
bbconf, and now I'm a little "afraid" what will happen if I
actually do anything with bbconf and keybindings?
How about supporting multiple keybindings?
Regards
On Sunday 09 June 2002 08:54, paco wrote:
> If I want to program blackbox apps, what api should I use?? gtk? qt??,
> or there's one for making apps/programs??
You may use gtk or qt, as you like.
Blackbox will soon (in few weeks/months ?) split into a program and a shared
library. This shared libr
On Sat, 08 Jun 2002 13:32:38 -0400
[EMAIL PROTECTED] wrote:
> I'm running a transparent aterm window, and want it borderless as well.
I downloaded bbappconf, edited bbappconf.bb so that class = XTerm, name
= aterm, and decorless = true. Still no decorless window. I've tried
to make this happ
