hi there,
i'm new to the pd and gem thing. so my first problem/question is, if it is possible to get the gem windows fullscreen on a second display? i tried some messages... but most of them didn't work. like "fullscreen 1" ,i also tried to move it with a "x offset -1024" on the other screen...
thanx,
ralf
Hey,
You have to send the (OSX only) message "secondscreen 1" to gemwin and it'll do the full-screen and the second screen stuff automatically.
Ben ----- Original Message ----- From: "Ralf Baecker" ralf@no-surprises.de To: pd-list@iem.at Sent: Sunday, October 26, 2003 6:37 AM Subject: [PD] os x gem fullscreen
hi there,
i'm new to the pd and gem thing. so my first problem/question is, if it is possible to get the gem windows fullscreen on a second display? i tried some messages... but most of them didn't work. like "fullscreen 1" ,i also tried to move it with a "x offset -1024" on the other screen...
thanx,
ralf
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
I have gotten the offset to work, and forced gem to make an 800/600 window and have my second monitor at that setting. if I offset it just right it seemed to work.
but using the second monitor flag and the fullscreen one would consitantly crash me. =(
its best to init the settings before you create and start rendering (with using the offset). otherwise it seems to get unstable for me =\
-dok
On Oct 26, 2003, at 6:37 AM, Ralf Baecker wrote:
hi there,
i'm new to the pd and gem thing. so my first problem/question is, if it is possible to get the gem windows fullscreen on a second display? i tried some messages... but most of them didn't work. like "fullscreen 1" ,i also tried to move it with a "x offset -1024" on the other screen...
thanx,
ralf
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
Hey all,
If you use "secondscreen 1" you can't use the full screen message, you just use the create message as normal.
Also for Gem you have to set most the window properties BEFORE you create the window! This goes for dimen, fullscreen, secondscreen, offset. I think color and rendering are the only things you can change after having created the window.
See if that helps with the crashes at all. I've never had gem crash when creating windows.
Ben
----- Original Message ----- From: "doktorp" doktorp@mac.com To: "Ralf Baecker" ralf@no-surprises.de Cc: pd-list@iem.at Sent: Sunday, October 26, 2003 9:53 AM Subject: Re: [PD] os x gem fullscreen
I have gotten the offset to work, and forced gem to make an 800/600 window and have my second monitor at that setting. if I offset it just right it seemed to work.
but using the second monitor flag and the fullscreen one would consitantly crash me. =(
its best to init the settings before you create and start rendering (with using the offset). otherwise it seems to get unstable for me =\
-dok
On Oct 26, 2003, at 6:37 AM, Ralf Baecker wrote:
hi there,
i'm new to the pd and gem thing. so my first problem/question is, if it is possible to get the gem windows fullscreen on a second display? i tried some messages... but most of them didn't work. like "fullscreen 1" ,i also tried to move it with a "x offset -1024" on the other screen...
thanx,
ralf
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
Quoting "B. Bogart" ben@ekran.org:
Hey all,
If you use "secondscreen 1" you can't use the full screen message, you just use the create message as normal.
Also for Gem you have to set most the window properties BEFORE you create the window! This goes for dimen, fullscreen, secondscreen, offset. I think color and rendering are the only things you can change after having created the window.
some more info about the 'secondscreen' message:
- it will attempt to resize the attached display to the size 'dimen x y' is set
to, but I have set the minimum/default to a 'safe' 640x480 since most displays will do VGA resolution.
- if you set something smaller than 640 on x or 480 on y it will use the default
- there is no checking done in GEM for valid display dimensions, but the OS
should handle bad dimensions gracefully.
- GEM will not set the refresh rate
- secondscreen is primarily designed for easy setup in performance environments.
both Jamie and I have powerbooks and regularly use them in that role.
It might be better to roll this functionality into the 'fullscreen' message by adding another argument for the display number. The message would look like this:
[fullscreen on/off display# (
So 'fullscreen 1 0' would display fullscreen on the main monitor (also omitting the arg for display would default to the main screen), and 'fullscreen 1 1' would use an atached monitor.
See if that helps with the crashes at all. I've never had gem crash when creating windows.
The code used for secondscreen is right out of the Apple docs, and I personally haven't had any problems with it after adding the checks for minimum display bounds. All other errors have been handled by the OS just fine.
cgc
Ben
----- Original Message ----- From: "doktorp" doktorp@mac.com To: "Ralf Baecker" ralf@no-surprises.de Cc: pd-list@iem.at Sent: Sunday, October 26, 2003 9:53 AM Subject: Re: [PD] os x gem fullscreen
I have gotten the offset to work, and forced gem to make an 800/600 window and have my second monitor at that setting. if I offset it
just
right it seemed to work.
but using the second monitor flag and the fullscreen one would consitantly crash me. =(
its best to init the settings before you create and start rendering (with using the offset). otherwise it seems to get unstable for me =\
-dok
On Oct 26, 2003, at 6:37 AM, Ralf Baecker wrote:
hi there,
i'm new to the pd and gem thing. so my first problem/question is,
if
it is possible to get the gem windows fullscreen on a second
display?
i tried some messages... but most of them didn't work. like "fullscreen 1" ,i also tried to move it with a "x offset -1024" on
the
other screen...
thanx,
ralf
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
Hey all,
I'm using os x 10.2.8 and the "secondscreen 1" message works very well for me. hmm
thanks, ralf
cgc@humboldtblvd.com wrote:
Quoting "B. Bogart" ben@ekran.org:
Hey all,
If you use "secondscreen 1" you can't use the full screen message, you just use the create message as normal.
Also for Gem you have to set most the window properties BEFORE you create the window! This goes for dimen, fullscreen, secondscreen, offset. I think color and rendering are the only things you can change after having created the window.
some more info about the 'secondscreen' message:
- it will attempt to resize the attached display to the size 'dimen x y' is set
to, but I have set the minimum/default to a 'safe' 640x480 since most displays will do VGA resolution.
- if you set something smaller than 640 on x or 480 on y it will use the default
- there is no checking done in GEM for valid display dimensions, but the OS
should handle bad dimensions gracefully.
- GEM will not set the refresh rate
- secondscreen is primarily designed for easy setup in performance environments.
both Jamie and I have powerbooks and regularly use them in that role.
It might be better to roll this functionality into the 'fullscreen' message by adding another argument for the display number. The message would look like this:
[fullscreen on/off display# (
So 'fullscreen 1 0' would display fullscreen on the main monitor (also omitting the arg for display would default to the main screen), and 'fullscreen 1 1' would use an atached monitor.
See if that helps with the crashes at all. I've never had gem crash when creating windows.
The code used for secondscreen is right out of the Apple docs, and I personally haven't had any problems with it after adding the checks for minimum display bounds. All other errors have been handled by the OS just fine.
cgc
Ben
----- Original Message ----- From: "doktorp" doktorp@mac.com To: "Ralf Baecker" ralf@no-surprises.de Cc: pd-list@iem.at Sent: Sunday, October 26, 2003 9:53 AM Subject: Re: [PD] os x gem fullscreen
I have gotten the offset to work, and forced gem to make an 800/600 window and have my second monitor at that setting. if I offset it
just
right it seemed to work.
but using the second monitor flag and the fullscreen one would consitantly crash me. =(
its best to init the settings before you create and start rendering (with using the offset). otherwise it seems to get unstable for me =\
-dok
On Oct 26, 2003, at 6:37 AM, Ralf Baecker wrote:
hi there,
i'm new to the pd and gem thing. so my first problem/question is,
if
it is possible to get the gem windows fullscreen on a second
display?
i tried some messages... but most of them didn't work. like "fullscreen 1" ,i also tried to move it with a "x offset -1024" on
the
other screen...
thanx,
ralf
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
Hmm
maybe its a panther thing? Ive been running 7b85 for a while. Id always set the toggle for secondscreen $1 and then hit 'create'
no joy, but I havent tried it for a while. ill try again later.
and btw, I tried the pix_separate to split the gem renderchain but nothing changed at all. same issue as before.
All I did however was replace the 'separate' object with pix_separate, in my patch..
is there any special 'architecture'/patch setup that needs to be done?
sorry for dragging this out but im a bit confused.
thanks for all the help again
-dok
On Oct 26, 2003, at 1:33 PM, cgc@humboldtblvd.com wrote:
Quoting "B. Bogart" ben@ekran.org:
Hey all,
If you use "secondscreen 1" you can't use the full screen message, you just use the create message as normal.
Also for Gem you have to set most the window properties BEFORE you create the window! This goes for dimen, fullscreen, secondscreen, offset. I think color and rendering are the only things you can change after having created the window.
some more info about the 'secondscreen' message:
- it will attempt to resize the attached display to the size 'dimen x
y' is set to, but I have set the minimum/default to a 'safe' 640x480 since most displays will do VGA resolution.
- if you set something smaller than 640 on x or 480 on y it will use
the default
- there is no checking done in GEM for valid display dimensions, but
the OS should handle bad dimensions gracefully.
- GEM will not set the refresh rate
- secondscreen is primarily designed for easy setup in performance
environments. both Jamie and I have powerbooks and regularly use them in that role.
It might be better to roll this functionality into the 'fullscreen' message by adding another argument for the display number. The message would look like this:
[fullscreen on/off display# (
So 'fullscreen 1 0' would display fullscreen on the main monitor (also omitting the arg for display would default to the main screen), and 'fullscreen 1 1' would use an atached monitor.
See if that helps with the crashes at all. I've never had gem crash when creating windows.
The code used for secondscreen is right out of the Apple docs, and I personally haven't had any problems with it after adding the checks for minimum display bounds. All other errors have been handled by the OS just fine.
cgc
Ben
----- Original Message ----- From: "doktorp" doktorp@mac.com To: "Ralf Baecker" ralf@no-surprises.de Cc: pd-list@iem.at Sent: Sunday, October 26, 2003 9:53 AM Subject: Re: [PD] os x gem fullscreen
I have gotten the offset to work, and forced gem to make an 800/600 window and have my second monitor at that setting. if I offset it
just
right it seemed to work.
but using the second monitor flag and the fullscreen one would consitantly crash me. =(
its best to init the settings before you create and start rendering (with using the offset). otherwise it seems to get unstable for me =\
-dok
On Oct 26, 2003, at 6:37 AM, Ralf Baecker wrote:
hi there,
i'm new to the pd and gem thing. so my first problem/question is,
if
it is possible to get the gem windows fullscreen on a second
display?
i tried some messages... but most of them didn't work. like "fullscreen 1" ,i also tried to move it with a "x offset -1024" on
the
other screen...
thanx,
ralf
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
Oh I think I see what's happening. On 7b85 creating the secondscreen won't allow you to get the focus back to the patcher window. I don't recall this happening in 7b74 and it definitely isn't the case in Jag. It's very likely tcl/tk is at fault here, but it could be a change in the windowmanager or GL code as well. I'll see what I can find out about this problem. Just to narrow things down - what hardware are you using?
It should be noted that OSX development is only focused on 10.2 right now although testing is ongoing with 10.3. This is the first problem (and it's very recent) that has cropped up with 10.3 since the very early seeds like 7a202.
Quoting doktorp doktorp@mac.com:
Hmm
maybe its a panther thing? Ive been running 7b85 for a while. Id always
set the toggle for secondscreen $1 and then hit 'create'
no joy, but I havent tried it for a while. ill try again later.
and btw, I tried the pix_separate to split the gem renderchain but nothing changed at all. same issue as before.
All I did however was replace the 'separate' object with pix_separate,
in my patch..
is there any special 'architecture'/patch setup that needs to be done?
sorry for dragging this out but im a bit confused.
thanks for all the help again
-dok
I really thought I was going insane here...
nice to know I still have my sanity hehe.
tiBook 800, 10.3 (7b85), 1gig ram
ati rage m7 (32 mb ram), 1280x854
ill send crash logs if you want.
so any ideas about the patch though? =X =X +X. sorry to be annoying!
-dok
On Oct 26, 2003, at 4:43 PM, cgc@humboldtblvd.com wrote:
Oh I think I see what's happening. On 7b85 creating the secondscreen won't allow you to get the focus back to the patcher window. I don't recall this happening in 7b74 and it definitely isn't the case in Jag. It's very likely tcl/tk is at fault here, but it could be a change in the windowmanager or GL code as well. I'll see what I can find out about this problem. Just to narrow things down - what hardware are you using?
It should be noted that OSX development is only focused on 10.2 right now although testing is ongoing with 10.3. This is the first problem (and it's very recent) that has cropped up with 10.3 since the very early seeds like 7a202.
Quoting doktorp doktorp@mac.com:
Hmm
maybe its a panther thing? Ive been running 7b85 for a while. Id always
set the toggle for secondscreen $1 and then hit 'create'
no joy, but I havent tried it for a while. ill try again later.
and btw, I tried the pix_separate to split the gem renderchain but nothing changed at all. same issue as before.
All I did however was replace the 'separate' object with pix_separate,
in my patch..
is there any special 'architecture'/patch setup that needs to be done?
sorry for dragging this out but im a bit confused.
thanks for all the help again
-dok
i kno wthis sounds funny but i just turn mirroring on and put all my patches on monitor2 and project monitor1 but maybe i am assuming you want to send 2 screens?
-----Original Message----- From: pd-list-admin@iem.at [mailto:pd-list-admin@iem.at]On Behalf Of doktorp Sent: Sunday, October 26, 2003 4:47 PM To: cgc@humboldtblvd.com Cc: PD-list@iem.at Subject: Re: [PD] os x gem fullscreen
I really thought I was going insane here...
nice to know I still have my sanity hehe.
tiBook 800, 10.3 (7b85), 1gig ram
ati rage m7 (32 mb ram), 1280x854
ill send crash logs if you want.
so any ideas about the patch though? =X =X +X. sorry to be annoying!
-dok
On Oct 26, 2003, at 4:43 PM, cgc@humboldtblvd.com wrote:
Oh I think I see what's happening. On 7b85 creating the secondscreen won't allow you to get the focus back to the patcher window. I don't recall this happening in 7b74 and it definitely isn't the case in Jag. It's very likely tcl/tk is at fault here, but it could be a change in the windowmanager or GL code as well. I'll see what I can find out about this problem. Just to narrow things down - what hardware are you using?
It should be noted that OSX development is only focused on 10.2 right now although testing is ongoing with 10.3. This is the first problem (and it's very recent) that has cropped up with 10.3 since the very early seeds like 7a202.
Quoting doktorp doktorp@mac.com:
Hmm
maybe its a panther thing? Ive been running 7b85 for a while. Id always
set the toggle for secondscreen $1 and then hit 'create'
no joy, but I havent tried it for a while. ill try again later.
and btw, I tried the pix_separate to split the gem renderchain but nothing changed at all. same issue as before.
All I did however was replace the 'separate' object with pix_separate,
in my patch..
is there any special 'architecture'/patch setup that needs to be done?
sorry for dragging this out but im a bit confused.
thanks for all the help again
-dok
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
It doesn't crash for me at all - I just can't register clicks in the patcher window. Does yours segfault? If so then send me crash logs.
cgc
Quoting doktorp doktorp@mac.com:
I really thought I was going insane here...
nice to know I still have my sanity hehe.
tiBook 800, 10.3 (7b85), 1gig ram
ati rage m7 (32 mb ram), 1280x854
ill send crash logs if you want.
so any ideas about the patch though? =X =X +X. sorry to be annoying!
-dok
On Oct 26, 2003, at 4:43 PM, cgc@humboldtblvd.com wrote:
Oh I think I see what's happening. On 7b85 creating the secondscreen
won't allow you to get the focus back to the patcher window. I don't recall
this happening in 7b74 and it definitely isn't the case in Jag. It's very
likely tcl/tk is at fault here, but it could be a change in the windowmanager
or GL code as well. I'll see what I can find out about this problem. Just
to narrow things down - what hardware are you using?
It should be noted that OSX development is only focused on 10.2 right
now although testing is ongoing with 10.3. This is the first problem (and
it's very recent) that has cropped up with 10.3 since the very early seeds like
7a202.
Quoting doktorp doktorp@mac.com:
Hmm
maybe its a panther thing? Ive been running 7b85 for a while. Id always
set the toggle for secondscreen $1 and then hit 'create'
no joy, but I havent tried it for a while. ill try again later.
and btw, I tried the pix_separate to split the gem renderchain but nothing changed at all. same issue as before.
All I did however was replace the 'separate' object with
pix_separate,
in my patch..
is there any special 'architecture'/patch setup that needs to be
done?
sorry for dragging this out but im a bit confused.
thanks for all the help again
-dok
Zitiere doktorp doktorp@mac.com:
I have gotten the offset to work, and forced gem to make an 800/600 window and have my second monitor at that setting. if I offset it just
right it seemed to work.
but using the second monitor flag and the fullscreen one would consitantly crash me. =(
which OS are you on ? "secondscreen" works only for macOS-X (as far as i know) however, how does "fullscreen" crashes you ? if you get a black-screen that forbids any access to you control patch, this is basically the behaviour you requested (depending on the window-manager you are using). if this is the case, make sure, you can somehow destroy the gemwin, either by remote-control (netsend) or midi or gemmouse.
mfg.a.sdr IOhannes
-
B. Bogart -
cgc＠humboldtblvd.com -
doktorp -
Ralf Baecker -
shreeswifty -
zmoelnig＠iem.at