Hi, it would be very helpful to change the behaviour of gemmouse a little bit (to get similar results to the translation of objects in the gemwindow). [gemmouse 8] should normalize to the height (like gemwin) and not to the width. given a rectangular gemwin any aspect ratio (no difference between 2:1 and 1:2...) always normalizes to the height and sets (with the default view) the top and bottom borders to +4 and -4 gemmouse 8 on the other hand normalizes to the width. this makes it very difficult (unpossible?) to build mouse interaction with variable window sizes. another feature wish: to be able to tell the dimensions of the gemwin. esp. after resizing by mousedrawing. thanks, marius.
Why not do [gemmouse 8 4] for 2:1 window?
Of course you have to keep track of your own window size and alter the coords in responce, but that is largely the PD way anyhow, to keep track of what your doing yourself.
You could just normalize from 0 to 1 and rescale based on your window size?
As far as I know most platforms don't even allow mouse resizing of gemwindows...
.b.
marius schebella wrote:
Hi, it would be very helpful to change the behaviour of gemmouse a little bit (to get similar results to the translation of objects in the gemwindow). [gemmouse 8] should normalize to the height (like gemwin) and not to the width. given a rectangular gemwin any aspect ratio (no difference between 2:1 and 1:2...) always normalizes to the height and sets (with the default view) the top and bottom borders to +4 and -4 gemmouse 8 on the other hand normalizes to the width. this makes it very difficult (unpossible?) to build mouse interaction with variable window sizes. another feature wish: to be able to tell the dimensions of the gemwin. esp. after resizing by mousedrawing. thanks, marius.
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
B. Bogart wrote:
Why not do [gemmouse 8 4] for 2:1 window?
but then the window must have an aspect ratio of in 2:1 (which is ok if you do know it beforehand)
generally i agree with marius, that it makes more sense if giving only one arg to [gemmouse] it should normalize to y.
Of course you have to keep track of your own window size and alter the coords in responce, but that is largely the PD way anyhow, to keep track of what your doing yourself.
You could just normalize from 0 to 1 and rescale based on your window size?
As far as I know most platforms don't even allow mouse resizing of gemwindows...
at least there is one...
mfga.sdr IOhannes
Hi IOhannes, is this still on your todo list? it would make interface building in gem a lot easier. marius.
IOhannes m zmoelnig wrote:
B. Bogart wrote:
Why not do [gemmouse 8 4] for 2:1 window?
but then the window must have an aspect ratio of in 2:1 (which is ok if you do know it beforehand)
generally i agree with marius, that it makes more sense if giving only one arg to [gemmouse] it should normalize to y.
Of course you have to keep track of your own window size and alter the coords in responce, but that is largely the PD way anyhow, to keep track of what your doing yourself.
You could just normalize from 0 to 1 and rescale based on your window size?
As far as I know most platforms don't even allow mouse resizing of gemwindows...
at least there is one...
mfga.sdr IOhannes
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
marius schebella wrote:
Hi IOhannes, is this still on your todo list? it would make interface building in gem a lot easier.
in theory it was still on my todo list, in practice i have forgotten it... i have changed the behaviour in CVS now.
if this breaks somebodies patches, we might have to reconsider and introduce yet another syntax (otoh, i guess the [gemmouse <scale>] (with only one argument) was so unknown/unusable that chances are high that the current behaviour will not be challenged....
fgasdrm. IOhannes
thanks! marius.
IOhannes m zmoelnig wrote:
marius schebella wrote:
Hi IOhannes, is this still on your todo list? it would make interface building in gem a lot easier.
in theory it was still on my todo list, in practice i have forgotten it... i have changed the behaviour in CVS now.
if this breaks somebodies patches, we might have to reconsider and introduce yet another syntax (otoh, i guess the [gemmouse <scale>] (with only one argument) was so unknown/unusable that chances are high that the current behaviour will not be challenged....
fgasdrm. IOhannes
You can try gems/mouse in combination with gems/win from the Pdmtl Abstractions to get the mouse behavior you are looking for. Get a recent snapshot of the Pdmtl Abstractions here: http://wiki.dataflow.ws/PdMtlAbstractions
-
B. Bogart -
IOhannes m zmoelnig -
marius schebella -
Thomas O Fredericks