Pure Data Computer Music System

as ed kelly has demonstrated so beautifully at the pd~con07, this is
really a feature and not a bug:
it gives you the possibility to add hidden guiobjects that control the
behaviour of the visible ones.
e.g. you can create a symbol-box where you can select the symbols by
click-n-drag (just like you are used to do it with numberboxes)

see attached patch for examples
File Added: backguis-rule.pd

Hi, I tried tried to make a slider-based virtual clavier and this bug kept
all of the black keys from working. The workaround would have been to
surround the black keys with 3 white sliders of various sizes, then cover
discontinuities with a 1-pixel white canvas, all to ensure a single-layer
of GUI elements. I definitely said the hell with it. So I agree it's
terribly annoying! Maybe I'll have a look at the source sometime, but it
would be a miracle if I found it.

> Isn't it intended to let access GUI elements which are on the bottom of
> stack, thus taking them to the top (in rotation)? Because if

The bottom element is not taken to the top. It remains on the bottom, and
it keeps receiving the events; the front-most element never receives the
event.
Furthermore, I am concerned especially about non-edit mode, and I don't
think that anything should rotate when not editing.

Have a look at the attached patch (depth_bug.pd).
By the way, sorry for not attaching an example before.

It just makes no sense that you are clicking on what is hidden rather than
on what is visible.
File Added: depth_bug.pd

> However, the opposite happens: the gui element which is behind is the
one that you move.

Isn't it intended to let access GUI elements which are on the bottom of
stack, thus taking them to the top (in rotation)? Because if

> the correct behaviour was that the front-most element "receive" the
mouse click

then the front-most element would be the only one that receives while the
others stayed intact.