[clfswm-devel] Some news: new Exposé mode, new toolbar system.

[Philippe Brochard]

Valentin Plechinger writes:

>> Please can you attach the full backtrace? Which lisp and clx are you
>> using? Do you try to remove the toolbar before its creation? If this is
>> the case, this will be corrected on the next commit.
>>
>> Philippe
>
> Lisp is clisp 2.49 (Ubuntu Package), clx is the clisp-module-clx ubuntu package.
>
> Creation of the toolbar works with your function if I put it in rc file like
> (create-my-toolbar)
> Removing the toolbar works, but leaves and empty part on the screen
> which makes it useless.
>
I haven't yet implemented the original root recovery. Thanks for the
report. 

> Recreating doesn't work as well.
> Backtrace soon.
>
Yes, please report in detailed mode.

> Some other things bother me as well.
> Is it possible to open function that query input, like run-program,
> lisp-eval etc., on top of the toolbar and not below it? (in case of a
> top toolbar)
>
Yes, use a different with-placement than the original one. If you don't
find one write it or ask for it (top-left-placement comes in mind but
this may needs some tweaks if you want it on top of your second
screen).

> Also, if there is a copy-paste possibility for the above mentioned
> input fields, I can't seem to find them (would be useful).
>
No. Needs to be implemented. Patch welcome!

> In the expose mode, the last time I used clfswm, pressing the right
> key focused the child, now I need to press return. Why was this
> changed? (and how can I revert to the old behaviour)
>
Because with the previous version, you can't access more than 26
children. With the new one there is no limit. It's important because
with a dual screen, at start up, you already have 4 children accessible
and the 26 children limit is pretty small. 

BTW, you can implement the previous behaviour with four lines in
clfswm-expose-mode.lisp and let the user choose the behaviour it likes:

--------------------------------------------------
+(defconfig *expose-direct-select* t
+  'Expose-mode "Immediately select child if they can be directly accessed")

(defun expose-query-key-press-hook (code state)
  (declare (ignore code state))
  (expose-draw-letter)
+  (when (and *expose-direct-select* (<= (length *expose-windows-list*) 26))
+    (leave-query-mode :return)))
--------------------------------------------------

It's in the last commit (3361fc5).

And remember that you can also use the jump or bind method to very
quickly change your current children.

> Overall nice improvements, but still very buggy.
>
Please, please, *REPORT* them. I use clfswm intensively and try to test
it with different lisp implementations and different clx versions (I
write it with a different version (sbcl) than the one I use daily (clisp)).
But I don't see what you mean by buggy. Does it crash, it doesn't react
as you think, what...???

Report all things that bother you. It's the only way to make CLFSWM
better as I can't spot all bugs myself (I can't test all lisp/clx/xorg
versions...)

For example, with the last Debian sid upgrade, I got an unimplemented
event X error. CLFSWM breaks and reports it. I haven't this bug with
clisp/new-clx but with all others lisp/clx versions and all works well
with another X version. And even a very old version of CLFSWM breaks on
the same event error but works well with other X versions too.
So what? I add some code to prevent the break (works in progress) but I
think the problem is not in CLFSWM, nor in the XLib but it comes from
Xorg itself (I need to verify this). BTW, CLFSWM *must not* break on
this error type.

> Or I'm too much of an casual user.
>
In any case, thanks for your perseverance!

> Valentin
>
Cheers,

Philippe