Dear list,
is there a fix already on this issue? https://github.com/umlaeute/Gem/issues/257
or i have to use [gemglfw3window] and we have to live with it.
Best,
Popesz
Am 30. November 2021 19:50:29 MEZ schrieb "Csaba Láng" langcsaba@gmail.com:
Dear list,
is there a fix already on this issue? https://github.com/umlaeute/Gem/issues/257
or i have to use [gemglfw3window] and we have to live with it.
What is wrong with [gemglfw3window]?
mfg.sfg.jfd IOhannes
Nothin at all, just have to replace all in my patches :)
On Tue, Nov 30, 2021 at 8:16 PM IOhannes m zmölnig zmoelnig@iem.at wrote:
Am 30. November 2021 19:50:29 MEZ schrieb "Csaba Láng" < langcsaba@gmail.com>:
Dear list,
is there a fix already on this issue? https://github.com/umlaeute/Gem/issues/257
or i have to use [gemglfw3window] and we have to live with it.
What is wrong with [gemglfw3window]?
mfg.sfg.jfd IOhannes
On 12/1/21 19:55, Csaba Láng wrote:
Nothin at all, just have to replace all in my patches :)
no. [gemgflw3window] is *not* a replacement for [gemwin].
it's a replacement for [gemcocoawindow]. both (and all the other [gem*window]) objects are one of the building blocks for [gemwin].
within the [gemwin] abstraction you find a [gemdefaultwindow] abstraction which is just holds a single object (the default [gem*window]).
so what you need to do is modify this [gemdefaultwindow] abstraction by replacing whatever window object you find in there with [gemglfw3window]. safe that new abstraction somewhere in a path that is searched *before* the Gem-path (or just overwrite the original gemdefaultwindow.pd).
restart Pd. your old patches should start working again...
gmfsae IOhannes
Am 30. November 2021 19:50:29 MEZ schrieb "Csaba Láng" langcsaba@gmail.com:
Dear list,
is there a fix already on this issue? https://github.com/umlaeute/Gem/issues/257
or i have to use [gemglfw3window] and we have to live with it.
What is wrong with [gemglfw3window]?
Gem Help patches might not work...