docb

hi, i further examined some problems with my node-gtk app and extended the drawing area example with moving the circle arround with the mouse where i detected increasing memory and...

yes sure it is better to fix it. i was not sure if it is a glib/gtk problem. These errors occur sporadically - i cannot narrow down to actions or...

here is one with the GSlice Error ***MEMORY-ERROR***: node[40442]: GSlice: assertion failed: sinfo->n_allocated > 0 Thread 1 "node" received signal SIGABRT, Aborted. __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 51 ../sysdeps/unix/sysv/linux/raise.c: No such...

it happens when the mouse pointer leaves the window. may be not all cases but this i could observe multiple times.

another observation: with G_SLICE=always-malloc set i have no sudden crashes anymore but suddenly the motion event frequency goes down to c.a 3 events per second which is either unusable. however...

https://github.com/docb/gtkosc i have pushed this one. call node index.js and play arround.

ok, i have tried something may be hacky which seem to work, however not tested and thought through in detail:  the only way i found to get the GridConnectionManager...

>but this only works if a monome module is loaded first, so some extra mechanisms have to be developed. when calling GridConnectionManager::get() in the init code of the monome plugin...

i forgot to some function, the code of the plugin looks like this: ```c static inline void* getSymbol(void* handle, const char* name) { if (!handle) return NULL; #if defined ARCH_WIN...

hi, thanks for your hint, it will be fixed in the next version.