Indeed, such behavior doesn't happen on my linux box,
where the GEM is installed with the debian-multimedia package
(damned I have to compile GEM because this package is really obsolete).
I've always encountered this behavior with gem dll's since the 0.90 version.
patco
IOhannes m zmoelnig <zmoelnig@iem.at> a écrit :
patco wrote:
> Hi,
> A little example patch for feeding the GEM text3d with typing on the keyboard, see now
> how the cpu don't like an high amount of characters,
> the string of characters MUST be separated into several text3d object to not eat the cpu.
>
i am interested in this, since i never experienced such behaviour.
additionally i cannot reproduce it with your test path: a string of 1
character makes pd eat 2% on my machine; a string of 100 characters
makes pd eat 2% on my machine.
mfg.aDR
ioHANNES