Strange problem when using the "F" keys in key shortcuts, what is wrong?

--===============4066467629926451776==
Content-Type: multipart/alternative; boundary="000000000000cb307b05dd5871fd"

--000000000000cb307b05dd5871fd
Content-Type: text/plain; charset="UTF-8"

Hello, I have rather unusual problem with keybindings in Fluxbox that
started since I decided to use more F keys on my desktop. It is related as
after removing these bindings things go back to normal - yet, I think it
shouldn't happen.

Using stable 1.3.7 Fluxbox version and keyboard layout is set to "pl, pl".

Here are my F keys related bindings:

F1 Escape :RootMenu
F1 Return :Exec urxvt
F1 H :Exec xmessage -fn -*-fixed-*-*-*-*-18-*-*-*-*-*-*-* -bg gray15 -fg
gray -center -file ~/.fluxbox/keys

F2 Left :PrevWorkspace
F2 Right :NextWorkspace
F2 Escape Left :SendToWorkspace 1
F2 Escape Right :SendToWorkspace 2
F2 Shift Left :TakeToPrevWorkspace
F2 Shift Right :TakeToNextWorkspace

F3 C :Close
F3 M :Maximize
F3 N :Minimize
F3 F11 :Fullscreen
F3 Up             :MacroCmd {SetDecor NORMAL} {ShadeOn}
F3 Down           :MacroCmd {ShadeOff} {SetDecor BORDER}

F4 Right :MacroCmd {ResizeTo 50% 100%} {MoveTo 00 00 Right}
F4 Left :MacroCmd {ResizeTo 50% 100%} {MoveTo 00 00 Left}
F4 Up :MacroCmd {ResizeTo 100% 50%} {MoveTo 00 00 Top}
F4 Down :MacroCmd {ResizeTo 100% 50%} {MoveTo 00 00 Bottom}

F4 Prior :MacroCmd {ResizeTo 50% 50%} {MoveTo 00 00 TopRight}
F4 Insert :MacroCmd {ResizeTo 50% 50%} {MoveTo 00 00 TopLeft}
F4 Next :MacroCmd {ResizeTo 50% 50%} {MoveTo 00 00 BottomRight}
F4 Delete :MacroCmd {ResizeTo 50% 50%} {MoveTo 00 00 BottomLeft}

Now, what is wrong: when I press F1-F4 keys on my desktop with no windows
open and after that I try to for example use right mouse button to open the
root menu it does not open - there is no reaction. When I press the F1-F4
key again(does not matter, I can press F1 to make it happen and later F3 to
fix it) - all works. It seems like because of these keys are being in key
bindings they got some kind of "function"? Cannot explain it better, they
just put desktop in some kind of "state" when pressed and release that
"state" when pressed again. Like some kind of layer is being put on top of
the desktop, I dunno how to properly explain it.

I was totally surprised when I found out that these keys being used in keys
file are the reason for my desktop strange behaviour and I am very curious
where is the problem. Hope someone will be able to help me understand what
is actually going on.

--000000000000cb307b05dd5871fd
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello, I have rather unusual problem with keybindings in F=
luxbox that started since I decided to use more F keys on my desktop. It is=
 related as after removing these bindings things go back to normal - yet, I=
 think it shouldn&#39;t happen.<br><br>Using stable 1.3.7 Fluxbox version a=
nd keyboard layout is set to &quot;pl, pl&quot;.<br><br>Here are my F keys =
related bindings:<br><br>F1 Escape :RootMenu<br>F1 Return			:Exec urxvt<br>=
F1 H				:Exec xmessage -fn -*-fixed-*-*-*-*-18-*-*-*-*-*-*-* -bg gray15 -fg=
 gray -center -file ~/.fluxbox/keys<br><br>F2 Left				:PrevWorkspace<br>F2 =
Right			:NextWorkspace<br>F2 Escape Left		:SendToWorkspace 1<br>F2 Escape R=
ight		:SendToWorkspace 2<br>F2 Shift Left		:TakeToPrevWorkspace<br>F2 Shift=
 Right		:TakeToNextWorkspace<br><br>F3 C				:Close<br>F3 M				:Maximize<br>=
F3 N				:Minimize<br>F3 F11				:Fullscreen<br>F3 Up =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0	:MacroCmd {SetDecor NORMAL} {ShadeOn}<br>F3 Down =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0	:MacroCmd {ShadeOff} {SetDecor BORDER}<br><=
br>F4 Right			:MacroCmd {ResizeTo 50% 100%} {MoveTo 00 00 Right}<br>F4 Left=
				:MacroCmd {ResizeTo 50% 100%} {MoveTo 00 00 Left}<br>F4 Up				:MacroCmd=
 {ResizeTo 100% 50%} {MoveTo 00 00 Top}<br>F4 Down				:MacroCmd {ResizeTo 1=
00% 50%} {MoveTo 00 00 Bottom}<br><br>F4 Prior			:MacroCmd {ResizeTo 50% 50=
%} {MoveTo 00 00 TopRight}<br>F4 Insert			:MacroCmd {ResizeTo 50% 50%} {Mov=
eTo 00 00 TopLeft}<br>F4 Next				:MacroCmd {ResizeTo 50% 50%} {MoveTo 00 00=
 BottomRight}<br>F4 Delete			:MacroCmd {ResizeTo 50% 50%} {MoveTo 00 00 Bot=
tomLeft}<br><br>Now, what is wrong: when I press F1-F4 keys on my desktop w=
ith no windows open and after that I try to for example use right mouse but=
ton to open the root menu it does not open - there is no reaction. When I p=
ress the F1-F4 key again(does not matter, I can press F1 to make it happen =
and later F3 to fix it) - all works. It seems like because of these keys ar=
e being in key bindings they got some kind of &quot;function&quot;? Cannot =
explain it better, they just put desktop in some kind of &quot;state&quot; =
when pressed and release that &quot;state&quot; when pressed again. Like so=
me kind of layer is being put on top of the desktop, I dunno how to properl=
y explain it.<br><br>I was totally surprised when I found out that these ke=
ys being used in keys file are the reason for my desktop strange behaviour =
and I am very curious where is the problem. Hope someone will be able to he=
lp me understand what is actually going on.</div>

--000000000000cb307b05dd5871fd--


--===============4066467629926451776==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============4066467629926451776==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Fluxbox-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fluxbox-users

--===============4066467629926451776==--