On 22-Feb-2002 Andy Kopciuch wrote: >> >> note it is a warning, not an error. What is actually happening is the >> bblaunch code is rather sloppy. The fix is easy. >> >> The reason it is complaining is because it tries to read its own window >> which does not have all of the hints set. >> >> The message is spurious anyways. What is actually happening is the string >> bblaunch is looking for does not exist, but the function it calls returns 0 >> for any failure so it thinks it is out of memory. > > > I realize now I forgot to mention, the application does start, but in the > wrong workspace. That doesn't seem to work on some applications. >
Yes, bblaunch is a 'hack'. What it does is launch a program, then listen for blackbox new window messages. When one comes in bblaunch checks if the wmcommand on the new window matches the command line of the program it just launched. If they match it works. If you want to see why it is failing add some print statements so you can see what programs it is passing up. You may also consider increasing its delay before exiting.
