Feature request warning: This post contains a feature request which may be hazardous to the BYOND release date. Please make a note to come back and read it after the public release.
It would be very useful if we could gather some information about the Dream Seeker display settings like map mode and DS window location and size (OS and screen resolution would be handy too, though they are available through javascript) of attached clients, perhaps with a program hook to notify the game when the settings change.
One use (the idea that prompted this request) would be to create popup html windows at particular locations. You could even obscure the the often reviled buttons in the upper right corner of the DS client. (It would also be a lot easier if we could control the window placement in the browse() options instead of falling back on javascript.)
ID:137059
 Feb 27 2002, 7:06 am
|
|
I think it's safe to bump this post. It didn't recieve any comment from Dantom at the time of the post.
In addition, my experiments to control the screen location of popup browser windows have failed miserably. Javascipt moveto() commands offset the window within it's frame, but do not move the frame on the screen. Could you please add a new paramenter to browse() options to control where the window opens on screen? | |
I would like to do the same, although I know zilch about Java. I know in HTML, you can control some things about window size and location, but does the browse(something,"window=something") override any HTML which controls that?
A good, two and a half year bump, this. =$= | |
well since java is not used (nor mentioned), then it should not be a problem for you! :p javascript is different from java in many many ways, the most notable difference is the name. :D
now then, while bumping 2-year-old posts is considered bad-form and usually a no-no, this seems to fall under the "let's poke the developers again to politely remind them"-case. keep in mind that Dan, Tom, and company do work on things when they can, and sometimes there are other priorites to deal with first. but i agree, this level of control would be nice to have - assuming it hasn't been implemented already and no-one noticed. :) | |
Sorry for the delayed response :)
I hate to defer to the long-awaited BYOND 4.0 (since it's been in pre-alpha for about three years now), but I think its feature set should help resolve this issue. The main new command in 4.0 is "window()", which allows you to display UI components with some options. The idea behind 4.0 is to allow the designer to control the interface (both intitially and at runtime), so that games are no longer viewed as being played in a browser. That should probably make the need for other UI feedback less important (since games will just set the mode instead of allowing the user to control it). | |
I like this!