 |
Author |
Topic: size bug when exporting to applet in 65 (Read 201 times) |
|
hbarragan
|
size bug when exporting to applet in 65
« on: Oct 13th, 2003, 11:36pm » |
|
void setup() {
size(750, 75);
}
works but if people do something like this:
int SCREEN_HEIGHT = 75;
int SCREEN_WIDTH = 750;
void setup() {
size(SCREEN_WIDTH , SCREEN_HEIGHT);
}
will fail for applet exporting giving a message about size can not be determined from the code.
|
|
|
|
|
fry
|
Re: size bug when exporting to applet in 65
« Reply #1 on: Oct 14th, 2003, 10:34pm » |
|
right, unfortunately there's no way to magically figure out what size your code wants. there's no easy/consistent fix for this situation, so we're prolly not going to pursue one.
|
| « Last Edit: Oct 14th, 2003, 10:34pm by fry » |
|
|
|
|
Jerronimo
|
Re: size bug when exporting to applet in 65
« Reply #2 on: Oct 14th, 2003, 10:40pm » |
|
there could always be a process like, it checks to see the size of the window when you run it... Then instead of "i couldn't figure it out", it might say "I think it should be this: XXX, change it if I am wrong." kind of thing
this kind of thing can be added after release, when the source is out. I'd love to tackle something like this. 
|
|
|
|
|
fry
|
Re: size bug when exporting to applet in 65
« Reply #3 on: Oct 14th, 2003, 11:11pm » |
|
yeah, problem is that assumes that people run it before they export it, which is often not the case.
the best solution i've thought of is to have it keep track of the last window size used. and instead of the "fix the html yo damn self" error message that comes up, it includes a thing to type the new width/height, with the defaults set based on what was last used (similar to what you suggest).
but this will be post-beta.
|
| « Last Edit: Oct 14th, 2003, 11:13pm by fry » |
|
|
|
|
Jerronimo
|
Re: size bug when exporting to applet in 65
« Reply #4 on: Oct 14th, 2003, 11:27pm » |
|
Yup. That's actually one way that I was thinking about how it might be implemented.
|
|
|
|
|
|
