I have had issues similar to this, I found it was solved by switching off
compositing, as compiz was grabbing various sets of keystrokes before they
could get to the application.
Cheers,
Matt H
On 28 Jul 2015 09:44, Roman Haefeli reduz...@gmail.com wrote:
On Tue, 2015-07-28 at 01:09 +0200, s p
I've had this on Raspberry Pi. On the Pi it's a keyboard config issue. So
if the suggestions above don't work you could try mucking around with a
different keyboard config or even better actually identify what you
keyboard is and configure for that. Good luck, these kinds of basic issues
tend to
Hello list,
I am trying to compile objects for pd for the first time. Running
pd-extended 43.4 on OS 10.9.5. I just tried to compile the dummy objects in
/6.externs. I navigated to /6.externs in Terminal and typed
make pd_darwin
I got error in the Pd console when I tried to load these externals
Hi Reed -
I think the one in vanilla s up to date... it has teh i386 flag in two
spots, thus:
pd_darwin: obj1.pd_darwin obj2.pd_darwin \
obj3.pd_darwin obj4.pd_darwin obj5.pd_darwin dspobj~.pd_darwin
.SUFFIXES: .pd_darwin
DARWINCFLAGS = -DPD -O2 -Wall -W -Wshadow -Wstrict-prototypes \
On Tue, 2015-07-28 at 10:45 +0100, Matte wrote:
I have had issues similar to this, I found it was solved by switching
off compositing, as compiz was grabbing various sets of keystrokes
before they could get to the application.
Thanks for the hint.
In my case, it is not compiz grabbing
On 07/27/2015 01:28 PM, Charles Z Henry wrote:
On Mon, Jul 27, 2015 at 12:08 PM, Jonathan Wilkes via Pd-list
pd-list@lists.iem.at wrote:
Background info: Pd-l2ork has an extra member at the _end_ of the
t_widgetbehavior struct. This member is used to do accelerated displacing
of a selection
Probably right. The indented lines have to start with true tabs (easiest
done by changing the lines appropriately in the original makefile).
Or just download Pd vanilla and copy the makefile wholesale.
cheers
Miller
On Tue, Jul 28, 2015 at 12:56:15PM -0600, Reed Perkins wrote:
I copy and
Ok, so we have:
1) default widgetbehavior external: binary compatible
2) custom widgetbehavior external, compiled against Pd-l2ork and used in
Vanilla: big problems when external tries to initialize extra member of
struct
3) custom widgetbehavior external, compiled against Vanilla and used
