fullscreen jit.window issues.

Jun 8, 2006 at 5:30pm

fullscreen jit.window issues.

i’m encountering strange problems trying to set a window to 1024×768 on a 2nd screen. If I set the rect and even the size of the jit.window to specific values, the window doesn’t always end up at these values (sometimes there are gaps around the edges of the window, showing desktop), and “getrect” and “getsize” show values that are different than what I set.

winXP, AMD 2.0Ghz, XFX nVidia 6800GS 256MB, latest drivers from nVidia.

thanks,

Peter.

#P toggle 237 384 15 0;
#P window setfont “Sans Serif” 9.;
#P window linecount 1;
#P message 247 405 62 9109513 fullscreen $1;
#P window linecount 2;
#P comment 234 494 216 9109513 windows XP , . XGA nVidia 6800GS 256mb , AMD 2.0Ghz dual core processor (socket 939);
#P window linecount 3;
#P comment 591 382 181 9109513 then press this msg box. check the status window: the size and coords don’t match up with what I set!;
#P window linecount 1;
#P comment 591 361 181 9109513 then , hit esc. to go into fullscreen;
#P newex 665 521 48 9109513 print size;
#P newex 615 520 47 9109513 print rect;
#P newex 616 490 70 9109513 route rect size;
#P newex 341 341 78 9109513 print to_jitwindow;
#P newex 714 242 83 9109513 print fullsizeCoord;
#P newex 315 198 38 9109513 del 500;
#P message 471 264 47 9109513 floating 0;
#P message 329 242 65 9109513 size 1024 768;
#P newex 641 225 31 9109513 zl join;
#P message 680 176 46 9109513 1024 768;
#P newex 647 145 27 9109513 t l b;
#P newex 667 201 70 9109513 vexpr $i1 + $i2;
#P newex 647 121 44 9109513 zl slice 2;
#P newex 387 288 67 9109513 r doublebuffer;
#P newex 385 313 100 9109513 prepend doublebuffer;
#P newex 384 170 45 9109513 loadbang;
#P newex 341 454 330 9109513 jit.window @floating 0 @fsaa 1 @visible 1 @floating 0 @rect 10 100 330 340;
#P newex 620 55 72 9109513 r fullscreenon;
#P newex 503 228 27 9109513 t 0 b;
#P newex 590 128 19 9109513 t 1;
#P newex 593 104 49 9109513 deferlow;
#P newex 503 197 75 9109513 r fullscreenoff;
#P newex 619 77 52 9109513 route bang;
#P message 519 265 131 9109513 border 1 , rect 10 100 330 340;
#P message 561 287 161 9109513 floating 1 , border 0 , rect $1 $2 $3 $4;
#P newex 518 293 16 9109513 t l;
#P newex 334 169 41 9109513 sel 1 0;
#P message 355 212 70 9109513 size 320 240;
#P toggle 334 141 15 0;
#P newex 328 300 16 9109513 t l;
#P message 508 387 83 9109513 getrect , getsize;
#P newex 102 69 38 9109513 sel 27;
#P newex 103 45 40 9109513 key;
#P user ubumenu 36 48 38 9109513 0 1 1 0;
#X setrgb 157 166 183 58 62 64 0 0 0 58 62 64 141 141 141 112 112 112;
#X add 1;
#X add 2;
#X prefix_set 0 0 0;
#X pattrmode 1;
#P newex 25 227 66 9109513 t 1 b b b 0;
#P newex 111 282 50 9109513 deferlow;
#P message 111 303 77 9109513 draw_onoff $1;
#P newex 111 325 64 9109513 s commands;
#P newex 111 209 40 9109513 t 1 b 0;
#P newex 111 234 74 9109513 s fullscreenoff;
#P newex 25 201 40 9109513 sel 1 0;
#P toggle 104 99 15 0;
#P newex 73 165 49 9109513 zl slice 1;
#P newex 45 296 34 9109513 zl reg;
#P newex 25 325 71 9109513 s fullscreenon;
#P newex 74 146 65 9109513 route coords;
#P message 36 79 53 9109513 coords $1;
#P newex 34 100 59 9109513 jit.displays;
#B color 7;
#P objectname displays;
#P comment 25 343 53 9109513 fullscreen;
#P comment 123 100 100 9109513 full screen on/off;
#P comment 591 343 181 9109513 first , select a moinitor to go fullscreen on;
#P user panel 502 333 280 101;
#X brgb 191 191 191;
#X frgb 0 0 0;
#X border 1;
#X rounded 0;
#X shadow 0;
#X done;
#P connect 42 0 40 1;
#P connect 43 0 27 0;
#P connect 43 0 47 0;
#P connect 41 1 42 0;
#P connect 41 0 43 0;
#P connect 41 0 40 0;
#P connect 49 1 51 0;
#P connect 40 0 43 1;
#P connect 39 0 41 0;
#P connect 29 1 39 0;
#P connect 34 0 29 0;
#P connect 35 1 49 0;
#P connect 49 0 50 0;
#P connect 29 0 31 0;
#P connect 31 0 32 0;
#P connect 33 1 45 0;
#P connect 33 1 28 0;
#P connect 27 0 26 0;
#P connect 28 0 26 0;
#P connect 30 0 33 0;
#P connect 38 0 37 0;
#P connect 25 1 24 0;
#P connect 36 0 24 0;
#P connect 22 0 48 0;
#P connect 22 0 35 0;
#P connect 21 0 35 0;
#P connect 37 0 35 0;
#P connect 45 0 35 0;
#P connect 55 0 35 0;
#P connect 23 0 25 0;
#P connect 32 0 23 0;
#P connect 33 0 23 0;
#P connect 46 0 44 0;
#P connect 44 0 22 0;
#P connect 26 0 22 0;
#P connect 24 0 22 0;
#P connect 25 0 46 0;
#P connect 56 0 55 0;
#P connect 15 0 14 0;
#P connect 13 2 15 0;
#P connect 16 0 15 0;
#P connect 13 0 16 0;
#P connect 13 1 12 0;
#P connect 11 1 13 0;
#P connect 20 0 10 0;
#P connect 19 0 20 0;
#P fasten 4 0 6 0 39 140 79 140;
#P connect 6 0 9 0;
#P connect 9 1 8 1;
#P connect 17 1 7 0;
#P connect 17 1 8 0;
#P connect 17 2 5 0;
#P connect 18 0 5 0;
#P connect 5 0 4 0;
#P connect 8 0 7 0;
#P connect 11 0 17 0;
#P connect 10 0 11 0;
#P window clipboard copycount 57;

#26343
Jun 8, 2006 at 7:44pm

silly answer but, why don’t you use the fullscreen message to jit.window ?

#78640
Jun 9, 2006 at 12:02am

I should have specified…
because I need to render GL contexts into textures/matrices. In order to do that you need to specify the screensize to be the same as the texture dim, otherwise GL complains. So if i do all the stuff in that patch, then send the message fullscreen 1, I can nolonger render to a texture.

P.

#78641
Jun 9, 2006 at 12:26am

FWIW, this fixed in next version.

In the meantime, what happens if you use the @size @pos attributes
instead of rect?

-Joshua

#78642
Jun 9, 2006 at 12:28pm

same problem with @size and @pos. I sent msgs pos -800 0 and size 800 600 but the window is placed, well, not at those coordinates. getrect, getpos, and getsize report:
print: rect -798 20 0 609
print: size 798 589
print: pos -798 20

#78643
Jun 9, 2006 at 12:37pm

however, even with those coordinates as reported, with some fussing, i can get the texture readback functioning

#78644

You must be logged in to reply to this topic.