-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2014-08-19 18:11, Cyrille Henry wrote:
hello,
i just tested the current Gem git. (i'm still using on ubuntu linux 14.04, intel hd4000)
gemwin did not create. Gem/gemdefaultwindow can be created. it use gemglxwindow. (i have both gemglutwindow.pd_linux and gemglxwindow.pd_linux in /usr/local/lib/pd/extra/Gem)
sending the create message on this object did create an empty window. but sending "1" did not enable rendering, i only get : gemglxwindow: no method for 'float'
so : why did gemdefaultwindow is not named gemwin?
that's by design.
(sould i just make a symlink?)
no. [gemwin] and [gem*window] are *not* the same.
more important : how can i enable rendering?
the design is obviously different from what you expect.
[gemdefaultwindow] (or rather it's underlying implementations like [gemglxwindow] or [gemglutwindow]) is really just a very thin wrapper around an openGL-context. all it can do is to create/destroy an openGL-context (aka window), and make that context the "current" one (so any openGL commands are exectuted within this context).
it does a lot less than [gemwin], which handles viewpoints, rendering,...
short overview:
starting with Gem-0.94 (that is: current git), [gemwin] is now an abstraction (found in abstractions/). internally it uses [gemdefaultwindow] to create/destroy/switch-to windows/contexts, which is just another abstraction that wraps the actual implementation (e.g. [gemglfw3window]), but you really need the entire [gemwin] abstraction to use Gem as you used to.
apart from separating platform-independent code (as found in the [gemwin] abstraction) and platfrom-dependent code (the actual [gem*window] backend), this also allows the user to change the behaviour of [gemwin] without needing a compiler.
conclusion: add abstractions/ to your path, so you have a proper [gemwin].
fgmasdr IOhannes