Re: [Flightgear-devel] view options
Hi Dave, same here. But it is ok, if I start with 4:3 window and maximize it when fg runs (my normal start procedure). Maik dave perry schrieb am 06.01.2008 05:08: Maik Justus wrote: Hi, Maik Justus schrieb am 26.12.2007 20:38: Hi Syd, what's about an algorithm, which checks the ratio of the screen and sets fow to 55 for 4:3 screens and 70 for 16:9 screens? (55 / 70 = (4/3) / (16/9) ) Maik P.S.: for non-physicists: (55 / 73,333 = (4/3) / (16/9) ) Meanwhile I have a new computer wit 16:9 screen and the same problem. I've modified the calculation in viewer.cxx as mentioned above. Syd, please check, if this would work for you. Then we can think about, how to implement that in a clean way (maybe we need an FG_SCALING_HEIGHT case?). The patch is for the osg-branch, but it works with the plib branch, too (maybe some lines offset). Hi Maik, I have had a 16:9 flat pannel for some time. For the first time in several months, I built fgfs for osg from fresh svn and fresh cvs. What I noticed right away that has changed is that osg fgfs does not handle the --geometry=1680x1050 correctly anymore. The height of the image is too small for the width. The gages are not round. The plib branch still handles this correctly. Are you seeing what I am seeing or have I missed a patch? When I adjusted the width of the window until round objects are round and then measure the aspect ratio of the adjusted window, the aspect ratio is 4/3. Here is what comparing the plib to the osg response to changing the value of /sim/current-view/aspect-ratio-multiplier tells me: In plib, it adjusts the displayed aspect ratio. I can get the same distortion in plib fgfs as in osg fgfs by changing this value to ~1.2 instead of 1. But if I try to fix the view in osg fgfs by adjusting this value from 1 to 0.8333, all it does is scale the distorted image. i.e. it is adjusting the effective fov, not the aspect ratio. - Dave Perry - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] view options
Hi Dave, I checked again, if I start with a 4:3 resolution the gages remain round when maximizing to 1680*1050 by clicking the square in the upper right corner. I am running win xp, compiled on msvc-express. The same, if I start with --resolution=800x600. If I start with --resolution=1680x1050 the gages are not round, but the property browser seem to show the same values in sim/current-view. Maik dave perry schrieb am 06.01.2008 16:55: Hi Maik, If I use the command line to launch with the default 800x600 window and then use the gnome window maximize (i.e. click the square in upper right corner of the window), I get the distorted-aspect-ratio image filling the screen. I am running Fedora 7 with nvidia graphics, gnome window manager. What is your environment? -Dave Maik Justus wrote: Hi Dave, same here. But it is ok, if I start with 4:3 window and maximize it when fg runs (my normal start procedure). Maik dave perry schrieb am 06.01.2008 05:08: Maik Justus wrote: Hi, Maik Justus schrieb am 26.12.2007 20:38: Hi Syd, what's about an algorithm, which checks the ratio of the screen and sets fow to 55 for 4:3 screens and 70 for 16:9 screens? (55 / 70 = (4/3) / (16/9) ) Maik P.S.: for non-physicists: (55 / 73,333 = (4/3) / (16/9) ) Meanwhile I have a new computer wit 16:9 screen and the same problem. I've modified the calculation in viewer.cxx as mentioned above. Syd, please check, if this would work for you. Then we can think about, how to implement that in a clean way (maybe we need an FG_SCALING_HEIGHT case?). The patch is for the osg-branch, but it works with the plib branch, too (maybe some lines offset). Hi Maik, I have had a 16:9 flat pannel for some time. For the first time in several months, I built fgfs for osg from fresh svn and fresh cvs. What I noticed right away that has changed is that osg fgfs does not handle the --geometry=1680x1050 correctly anymore. The height of the image is too small for the width. The gages are not round. The plib branch still handles this correctly. Are you seeing what I am seeing or have I missed a patch? When I adjusted the width of the window until round objects are round and then measure the aspect ratio of the adjusted window, the aspect ratio is 4/3. Here is what comparing the plib to the osg response to changing the value of /sim/current-view/aspect-ratio-multiplier tells me: In plib, it adjusts the displayed aspect ratio. I can get the same distortion in plib fgfs as in osg fgfs by changing this value to ~1.2 instead of 1. But if I try to fix the view in osg fgfs by adjusting this value from 1 to 0.8333, all it does is scale the distorted image. i.e. it is adjusting the effective fov, not the aspect ratio. - Dave Perry - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] view options
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Maik Justus wrote: Hi Arvid, AnMaster schrieb am 04.01.2008 23:13: My resoltion is 1400x1280, not 4:3 nor 16:9 ? 20 1400x1280 TFT. I got no idea what format it is, but the monitor works well for me. The screen area of the monitor is about 30.5 cm high and 41 cm wide (+/- a few millimeters). but you also have to consider window borders. Not sure how large they are, however the screenshots I took at www.flightgear.org (A10-KNID-01 for example), were in maximized window. Should be possible to calculate from that. I think the borders have only very small effect to the calculation. Just try a fov of 47.5 (if your resolution is 1400x1280). Will try that. Regards, Arvid Norlander -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.7 (GNU/Linux) iD8DBQFHf16yWmK6ng/aMNkRCpB3AKC1T7k0jRgCUM/DwB7bqJDnt6IeZACfQyXE Sq8oyfTGeHGv2xiyuOh/rhA= =6nKA -END PGP SIGNATURE- - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] view options
Hi Arvid, maybe your pixels are not of square size? If yes: can you look to /sim/current-view/aspect-ratio-multiplier? If it is not 1, then we need to scale 47.5 with this factor (to get a larger fov). Thank you very much, Maik AnMaster schrieb am 05.01.2008 11:40: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Maik Justus wrote: Hi Arvid, AnMaster schrieb am 04.01.2008 23:13: My resoltion is 1400x1280, not 4:3 nor 16:9 ? 20 1400x1280 TFT. I got no idea what format it is, but the monitor works well for me. The screen area of the monitor is about 30.5 cm high and 41 cm wide (+/- a few millimeters). but you also have to consider window borders. Not sure how large they are, however the screenshots I took at www.flightgear.org (A10-KNID-01 for example), were in maximized window. Should be possible to calculate from that. I think the borders have only very small effect to the calculation. Just try a fov of 47.5 (if your resolution is 1400x1280). Will try that. Regards, Arvid Norlander -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.7 (GNU/Linux) iD8DBQFHf16yWmK6ng/aMNkRCpB3AKC1T7k0jRgCUM/DwB7bqJDnt6IeZACfQyXE Sq8oyfTGeHGv2xiyuOh/rhA= =6nKA -END PGP SIGNATURE- - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] view options
Hi Arvid, AnMaster schrieb am 05.01.2008 14:48: it is 1400x1050. ok (4:3). Try 58.6. Thank you, Maik - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] view options
Maik Justus wrote: Hi, Maik Justus schrieb am 26.12.2007 20:38: Hi Syd, what's about an algorithm, which checks the ratio of the screen and sets fow to 55 for 4:3 screens and 70 for 16:9 screens? (55 / 70 = (4/3) / (16/9) ) Maik P.S.: for non-physicists: (55 / 73,333 = (4/3) / (16/9) ) Meanwhile I have a new computer wit 16:9 screen and the same problem. I've modified the calculation in viewer.cxx as mentioned above. Syd, please check, if this would work for you. Then we can think about, how to implement that in a clean way (maybe we need an FG_SCALING_HEIGHT case?). The patch is for the osg-branch, but it works with the plib branch, too (maybe some lines offset). Hi Maik, I have had a 16:9 flat pannel for some time. For the first time in several months, I built fgfs for osg from fresh svn and fresh cvs. What I noticed right away that has changed is that osg fgfs does not handle the --geometry=1680x1050 correctly anymore. The height of the image is too small for the width. The gages are not round. The plib branch still handles this correctly. Are you seeing what I am seeing or have I missed a patch? When I adjusted the width of the window until round objects are round and then measure the aspect ratio of the adjusted window, the aspect ratio is 4/3. Here is what comparing the plib to the osg response to changing the value of /sim/current-view/aspect-ratio-multiplier tells me: In plib, it adjusts the displayed aspect ratio. I can get the same distortion in plib fgfs as in osg fgfs by changing this value to ~1.2 instead of 1. But if I try to fix the view in osg fgfs by adjusting this value from 1 to 0.8333, all it does is scale the distorted image. i.e. it is adjusting the effective fov, not the aspect ratio. - Dave Perry - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] view options
Hi,
Maik Justus schrieb am 26.12.2007 20:38:
Hi Syd,
what's about an algorithm, which checks the ratio of the screen and sets
fow to 55 for 4:3 screens and 70 for 16:9 screens? (55 / 70 = (4/3) /
(16/9) )
Maik
P.S.:
for non-physicists:
(55 / 73,333 = (4/3) / (16/9) )
Meanwhile I have a new computer wit 16:9 screen and the same problem.
I've modified the calculation in viewer.cxx as mentioned above. Syd,
please check, if this would work for you. Then we can think about, how
to implement that in a clean way (maybe we need an FG_SCALING_HEIGHT
case?). The patch is for the osg-branch, but it works with the plib
branch, too (maybe some lines offset).
Maik
Index: viewer.cxx
===
RCS file: /var/cvs/FlightGear-0.9/source/src/Main/viewer.cxx,v
retrieving revision 1.27
diff -u -p -r1.27 viewer.cxx
--- viewer.cxx 5 Nov 2007 22:19:39 - 1.27
+++ viewer.cxx 4 Jan 2008 19:54:11 -
@@ -640,15 +640,15 @@ FGViewer::get_h_fov()
{
switch (_scaling_type) {
case FG_SCALING_WIDTH: // h_fov == fov
- return _fov_deg;
+ return _fov_deg/_aspect_ratio/4*3;
case FG_SCALING_MAX:
if (_aspect_ratio 1.0) {
// h_fov == fov
- return _fov_deg;
+ return _fov_deg/_aspect_ratio/4*3;
} else {
// v_fov == fov
return
-atan(tan(_fov_deg/2 * SG_DEGREES_TO_RADIANS)
+atan(tan(_fov_deg/_aspect_ratio/4*3/2 * SG_DEGREES_TO_RADIANS)
/ (_aspect_ratio*_aspect_ratio_multiplier))
* SG_RADIANS_TO_DEGREES * 2;
}
@@ -666,19 +666,19 @@ FGViewer::get_v_fov()
switch (_scaling_type) {
case FG_SCALING_WIDTH: // h_fov == fov
return
-atan(tan(_fov_deg/2 * SG_DEGREES_TO_RADIANS)
+atan(tan(_fov_deg/_aspect_ratio/4*3/2 * SG_DEGREES_TO_RADIANS)
* (_aspect_ratio*_aspect_ratio_multiplier))
* SG_RADIANS_TO_DEGREES * 2;
case FG_SCALING_MAX:
if (_aspect_ratio 1.0) {
// h_fov == fov
return
-atan(tan(_fov_deg/2 * SG_DEGREES_TO_RADIANS)
+atan(tan(_fov_deg/_aspect_ratio/4*3/2 * SG_DEGREES_TO_RADIANS)
* (_aspect_ratio*_aspect_ratio_multiplier))
* SG_RADIANS_TO_DEGREES * 2;
} else {
// v_fov == fov
- return _fov_deg;
+ return _fov_deg/_aspect_ratio/4*3;
}
default:
assert(false);
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] view options
On Fri, 04 Jan 2008 21:01:15 +0100 Maik Justus [EMAIL PROTECTED] wrote: Hi, Maik Justus schrieb am 26.12.2007 20:38: Hi Syd, what's about an algorithm, which checks the ratio of the screen and sets fow to 55 for 4:3 screens and 70 for 16:9 screens? (55 / 70 = (4/3) / (16/9) ) Maik P.S.: for non-physicists: (55 / 73,333 = (4/3) / (16/9) ) Meanwhile I have a new computer wit 16:9 screen and the same problem. I've modified the calculation in viewer.cxx as mentioned above. Syd, please check, if this would work for you. Then we can think about, how to implement that in a clean way (maybe we need an FG_SCALING_HEIGHT case?). The patch is for the osg-branch, but it works with the plib branch, too (maybe some lines offset). Maik Hi Maik , I'll try it out after work ... Currently I've added --prop:/sim/current-view/field-of-view=70 to my fgfsrc file , and that works great but Ive noticed that the fov height changes when going from windowed to maximized window ... so yeah it would be nice to at least keep that the same But I better stay out of this , I tend to jinx things ;) Cheers -- SydSandy [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] view options
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 How does this work with windowed mode (that I always use, as maximized window, still showing the 64 pixels high KDE taskbar at the bottom, and window edges). My monitor is 4:3, but the window isn't. Regards, Arvid Norlander Maik Justus wrote: Hi, Maik Justus schrieb am 26.12.2007 20:38: Hi Syd, what's about an algorithm, which checks the ratio of the screen and sets fow to 55 for 4:3 screens and 70 for 16:9 screens? (55 / 70 = (4/3) / (16/9) ) Maik P.S.: for non-physicists: (55 / 73,333 = (4/3) / (16/9) ) Meanwhile I have a new computer wit 16:9 screen and the same problem. I've modified the calculation in viewer.cxx as mentioned above. Syd, please check, if this would work for you. Then we can think about, how to implement that in a clean way (maybe we need an FG_SCALING_HEIGHT case?). The patch is for the osg-branch, but it works with the plib branch, too (maybe some lines offset). Maik -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.7 (GNU/Linux) iD8DBQFHfpstWmK6ng/aMNkRCjUYAJ9I/h1lTEzVwsVkBfMc1YXJbDfW+wCZAbiE ff1ucoiecbrPDlqzMLErIng= =5D9E -END PGP SIGNATURE- - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] view options
AnMaster wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 How does this work with windowed mode (that I always use, as maximized window, still showing the 64 pixels high KDE taskbar at the bottom, and window edges). My monitor is 4:3, but the window isn't. AnMaster, same problem here: I guess 55° is horizontal, when the ration changes, fgfs or wich evre subsys crops the images at the top and the botom so the horizontal field is still 55°. If I'm right, I would say that with generalized wide formats, we should keep the legacy fixed field (55° * 3:4) in the vertical axis and increase the field on the horizontal axis. Alexis - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] view options
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 My resoltion is 1400x1280, but you also have to consider window borders. Not sure how large they are, however the screenshots I took at www.flightgear.org (A10-KNID-01 for example), were in maximized window. Should be possible to calculate from that. Other than that I think Alex Bory's suggestion was very good. Regards, Arvid Norlander Maik Justus wrote: Hi, it takes into account the aspect ratio of the window. If it is 4:3 everything is unchanged. If it is larger (e.g. 1024:704) you will get a higher field of view. Maybe you can try the patch (or set fov to 55/(4/3)*(1024/704) = 60 in the property tree: /sim/current-view/field-of-view) and check, if it is noticeable, and if yes: if it is better or worse than the 55. (replace 1024 and 704=768-64 with your resolution) Maik -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.7 (GNU/Linux) iD8DBQFHfq98WmK6ng/aMNkRCtS4AJ9GTpU7v/2DeBa/DlKtod72mtjwowCfVwHl tCl63sZB5A7zfgLyEuoGH+A= =ZuoK -END PGP SIGNATURE- - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] view options
Hi Arvid, AnMaster schrieb am 04.01.2008 23:13: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 My resoltion is 1400x1280, not 4:3 nor 16:9 ? but you also have to consider window borders. Not sure how large they are, however the screenshots I took at www.flightgear.org (A10-KNID-01 for example), were in maximized window. Should be possible to calculate from that. I think the borders have only very small effect to the calculation. Just try a fov of 47.5 (if your resolution is 1400x1280). Other than that I think Alex Bory's suggestion was very good. That's what the patch is doing. Regards, Arvid Norlander regards, Maik - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] view options : new idea
Hi All I love the new changes Stuart did, the reset button is great. Is there still anyway to add a text field? EG When I try to adjust fwd/back. Move the slider 1/2 a degree and you move 1m is distance. Anyway to fine tune that. Where you can enter the value 1.005m instead of 1.004m ??? Thanks guys Barry Stuart Buchanan wrote: --- SydSandy [EMAIL PROTECTED] wrote: On mer 26 décembre 2007, SydSandy wrote: Hi all... Just had another thought ... Maybe a simpler idea would be to have the sim/view/config/field-of-view property added to the autosave function ? This way it could be set per aircraft but that still means editing the properties in the property browser ... just thinking out loud :) Cheers I see in view.nas there IS this... # Saves/restores/moves the view point (position, orientation, field-of-view). # Moves are interpolated with sinusoidal characteristic. There's only one # instance of this class, available as view.point. # # Usage: #view.point.save();... save current view and return reference to # saved values in the form of a props.Node # #view.point.restore(); ... restore saved view parameters # #view.point.move(prop [, time]); # ... set view parameters from a props.Node with # optional move time in seconds. prop may be # nil, in which case nothing happens. # # A parameter set as expected by set() and returned by save() is a props.Node # object containing any (or none) of these children: # ..so , as usual , Melchoir seems to have already added this option ... now I just have to figure out how to use it :) Well, to save you some time, try the patch included below.. It adds the FoV to the Adjust View Distance dialog, and adds a Reset button for when you've messed up. Melchior/other committers - if you're happy with it, I'll commit it. -Stuart Index: pilot_offset.xml === RCS file: /var/cvs/FlightGear-0.9/data/gui/dialogs/pilot_offset.xml,v retrieving revision 1.4 diff -u -r1.4 pilot_offset.xml --- pilot_offset.xml 5 Nov 2005 18:42:29 - 1.4 +++ pilot_offset.xml 26 Dec 2007 21:44:50 - @@ -69,6 +69,27 @@ property/sim/current-view/z-offset-m/property /text /group + + group + layoutvbox/layout + + textlabelFoV/label/text + dial +wrapfalse/wrap +min1/min +max120/max +stretchtrue/stretch +property/sim/current-view/field-of-view/property +bindingcommanddialog-apply/command/binding + /dial + + text +label100.00 deg/label +format%-0.2f deg/format +livetrue/live +property/sim/current-view/field-of-view/property + /text + /group /group group @@ -79,9 +100,19 @@ equaltrue/equal defaulttrue/default keyEsc/key - bindingcommanddialog-apply/command/binding bindingcommanddialog-close/command/binding /button + button + legendReset/legend + binding + commandnasal/command + script + view.resetFOV(); + view.resetViewPos(); + /script +/binding +bindingcommanddialog-update/command/binding + /button emptystretchtrue/stretch/empty /group /PropertyList __ Sent from Yahoo! Mail - a smarter inbox http://uk.mail.yahoo.com - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] view options : new idea
I Don't know if it my changes I simply applies Stuarts and Syd When I adjust Up/Down The dial rotates but the value always stays the same 1.84m (using 737-300) ?? Thanks Barry Barry Fawthrop wrote: Hi All I love the new changes Stuart did, the reset button is great. Is there still anyway to add a text field? EG When I try to adjust fwd/back. Move the slider 1/2 a degree and you move 1m is distance. Anyway to fine tune that. Where you can enter the value 1.005m instead of 1.004m ??? Thanks guys Barry Stuart Buchanan wrote: --- SydSandy [EMAIL PROTECTED] wrote: On mer 26 décembre 2007, SydSandy wrote: Hi all... Just had another thought ... Maybe a simpler idea would be to have the sim/view/config/field-of-view property added to the autosave function ? This way it could be set per aircraft but that still means editing the properties in the property browser ... just thinking out loud :) Cheers I see in view.nas there IS this... # Saves/restores/moves the view point (position, orientation, field-of-view). # Moves are interpolated with sinusoidal characteristic. There's only one # instance of this class, available as view.point. # # Usage: #view.point.save();... save current view and return reference to # saved values in the form of a props.Node # #view.point.restore(); ... restore saved view parameters # #view.point.move(prop [, time]); # ... set view parameters from a props.Node with # optional move time in seconds. prop may be # nil, in which case nothing happens. # # A parameter set as expected by set() and returned by save() is a props.Node # object containing any (or none) of these children: # ..so , as usual , Melchoir seems to have already added this option ... now I just have to figure out how to use it :) Well, to save you some time, try the patch included below.. It adds the FoV to the Adjust View Distance dialog, and adds a Reset button for when you've messed up. Melchior/other committers - if you're happy with it, I'll commit it. -Stuart Index: pilot_offset.xml === RCS file: /var/cvs/FlightGear-0.9/data/gui/dialogs/pilot_offset.xml,v retrieving revision 1.4 diff -u -r1.4 pilot_offset.xml --- pilot_offset.xml 5 Nov 2005 18:42:29 - 1.4 +++ pilot_offset.xml 26 Dec 2007 21:44:50 - @@ -69,6 +69,27 @@ property/sim/current-view/z-offset-m/property /text /group + + group + layoutvbox/layout + + textlabelFoV/label/text + dial +wrapfalse/wrap +min1/min +max120/max +stretchtrue/stretch +property/sim/current-view/field-of-view/property +bindingcommanddialog-apply/command/binding + /dial + + text +label100.00 deg/label +format%-0.2f deg/format +livetrue/live +property/sim/current-view/field-of-view/property + /text + /group /group group @@ -79,9 +100,19 @@ equaltrue/equal defaulttrue/default keyEsc/key - bindingcommanddialog-apply/command/binding bindingcommanddialog-close/command/binding /button + button + legendReset/legend + binding + commandnasal/command + script + view.resetFOV(); + view.resetViewPos(); + /script +/binding +bindingcommanddialog-update/command/binding + /button emptystretchtrue/stretch/empty /group /PropertyList __ Sent from Yahoo! Mail - a smarter inbox http://uk.mail.yahoo.com - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net
Re: [Flightgear-devel] view options : new idea
On Fri, 28 Dec 2007 08:11:05 -0500 Barry Fawthrop [EMAIL PROTECTED] wrote: I Don't know if it my changes I simply applies Stuarts and Syd When I adjust Up/Down The dial rotates but the value always stays the same 1.84m (using 737-300) ?? Thanks Barry Barry Fawthrop wrote: Hi All I love the new changes Stuart did, the reset button is great. Is there still anyway to add a text field? EG When I try to adjust fwd/back. Move the slider 1/2 a degree and you move 1m is distance. Anyway to fine tune that. Where you can enter the value 1.005m instead of 1.004m ??? Thanks guys Barry Hi Barry , You can enter a value by hand in the property browser ... the property is sim/current-view/field-of-view... Cheers -- SydSandy [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] view options
On mer 26 décembre 2007, SydSandy wrote: Hi everyone , and merry christmas... I'm busy playing with my new 1440x900 flat - panel monitor ...wow what a difference in FG ! Which gave me an idea maybe others would appreciate too Before this , a default field 0f view of 55 was about right ... now I need to set it to 70 for a good view . Rather than modifying my set files and possibly ruining someone else's setup ... maybe a field-of-view slider in the view options would be an idea ? Im poking around in view.xml now but might take a bit to figure it out :) Cheers I agree with the wow what a difference in FG I do use since ( more ) than two years a 1800 or 1920 x 1440 or 1350 format and i do use field of view 70 That is the best, to me, field of view. We have the x and X key to tune it Cheers -- Gérard http://pagesperso-orange.fr/GRTux/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] view options
Sounds very smart. I haven't gotten my giant flatscreen yet. :-) Rather than modifying my set files and possibly ruining someone else's setup ... maybe a field-of-view slider in the view options would be an idea ? Im poking around in view.xml now but might take a bit to figure it out :) Cheers -- SydSandy [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel www.GlobalBoiling.com for daily images about hurricanes, globalwarming and the melting poles. www.ElectricQuakes.com daily solar and earthquake images. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] view options
Hi All I would Agree and like to suggest that the View Distance also have an edit field to type in the number. Trying to move the dials is far to excessive for a minute change. Thanks Barry gerard robin wrote: On mer 26 décembre 2007, SydSandy wrote: Hi everyone , and merry christmas... I'm busy playing with my new 1440x900 flat - panel monitor ...wow what a difference in FG ! Which gave me an idea maybe others would appreciate too Before this , a default field 0f view of 55 was about right ... now I need to set it to 70 for a good view . Rather than modifying my set files and possibly ruining someone else's setup ... maybe a field-of-view slider in the view options would be an idea ? Im poking around in view.xml now but might take a bit to figure it out :) Cheers I agree with the wow what a difference in FG I do use since ( more ) than two years a 1800 or 1920 x 1440 or 1350 format and i do use field of view 70 That is the best, to me, field of view. We have the x and X key to tune it Cheers - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] view options
On Wed, 26 Dec 2007 18:50:26 +0100 alexis bory [EMAIL PROTECTED] wrote: gerard robin wrote: We have the x and X key to tune it Yes, but I (and probably others) use often view.resetView(), which is triggered by a button on my joystick, to recenter the view and in this case using x/X to change the FoV is not sufficient. Also, I'd like to add a question: should a slider in the View Options change the FoV of all views ? Alexis... and Merry Christmas ! yes the reset view is the problem , why I suggested it ... but i was thinking of a slider for each view , or maybe a toggle button to step it a certain amount each click ... Just another one of my half baked ideas :) Cheers -- SydSandy [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] view options
Hi Syd, what's about an algorithm, which checks the ratio of the screen and sets fow to 55 for 4:3 screens and 70 for 16:9 screens? (55 / 70 = (4/3) / (16/9) ) Maik P.S.: for non-physicists: (55 / 73,333 = (4/3) / (16/9) ) SydSandy schrieb am 26.12.2007 06:25: Hi everyone , and merry christmas... I'm busy playing with my new 1440x900 flat - panel monitor ...wow what a difference in FG ! Which gave me an idea maybe others would appreciate too Before this , a default field 0f view of 55 was about right ... now I need to set it to 70 for a good view . Rather than modifying my set files and possibly ruining someone else's setup ... maybe a field-of-view slider in the view options would be an idea ? Im poking around in view.xml now but might take a bit to figure it out :) Cheers - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] view options
On Wed, 26 Dec 2007 20:38:22 +0100 Maik Justus [EMAIL PROTECTED] wrote: Hi Syd, what's about an algorithm, which checks the ratio of the screen and sets fow to 55 for 4:3 screens and 70 for 16:9 screens? (55 / 70 = (4/3) / (16/9) ) Maik P.S.: for non-physicists: (55 / 73,333 = (4/3) / (16/9) ) Hi Maik , sounds like an idea ... I feel like that would take away from user control , though, unless I'm misunderstanding.. but I also agree with Barry that sliders are too clumsy , hard to set accurately ( like the fuel sliders ) ... -- SydSandy [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] view options
On mer 26 décembre 2007, SydSandy wrote: On Wed, 26 Dec 2007 20:38:22 +0100 Maik Justus [EMAIL PROTECTED] wrote: Hi Syd, what's about an algorithm, which checks the ratio of the screen and sets fow to 55 for 4:3 screens and 70 for 16:9 screens? (55 / 70 = (4/3) / (16/9) ) Maik P.S.: for non-physicists: (55 / 73,333 = (4/3) / (16/9) ) Hi Maik , sounds like an idea ... I feel like that would take away from user control , though, unless I'm misunderstanding.. but I also agree with Barry that sliders are too clumsy , hard to set accurately ( like the fuel sliders ) ... Yes if we keep the manual command from x X any automatic solution is not welcome. -- Gérard http://pagesperso-orange.fr/GRTux/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] view options : new idea
On mer 26 décembre 2007, SydSandy wrote: Hi all... Just had another thought ... Maybe a simpler idea would be to have the sim/view/config/field-of-view property added to the autosave function ? This way it could be set per aircraft but that still means editing the properties in the property browser ... just thinking out loud :) Cheers Would be good, because we have more or less that customized per Aircraft, with the value of the field of view within -set.xml file for instance i have ===an aircraft (noratlas) with view internal archive=ytrue/internal config the -set.xml default-field-of-view-deg type=double72.0/default-field-of-view-deg and current-view field-of-view type=double72.0/field-of-view /current-view OR an other (blackbird) view internal archive=ytrue/internal config default-field-of-view-degtype=double64.0/default-field-of-view-deg -- Gérard http://pagesperso-orange.fr/GRTux/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] view options : new idea
On Wed, 26 Dec 2007 21:19:30 +0100 gerard robin [EMAIL PROTECTED] wrote: On mer 26 décembre 2007, SydSandy wrote: Hi all... Just had another thought ... Maybe a simpler idea would be to have the sim/view/config/field-of-view property added to the autosave function ? This way it could be set per aircraft but that still means editing the properties in the property browser ... just thinking out loud :) Cheers Would be good, because we have more or less that customized per Aircraft, with the value of the field of view within -set.xml file for instance i have ===an aircraft (noratlas) with view internal archive=ytrue/internal config the -set.xml default-field-of-view-deg type=double72.0/default-field-of-view-deg and current-view field-of-view type=double72.0/field-of-view /current-view OR an other (blackbird) view internal archive=ytrue/internal config default-field-of-view-degtype=double64.0/default-field-of-view-deg -- Gérard http://pagesperso-orange.fr/GRTux/ I see in view.nas there IS this... # Saves/restores/moves the view point (position, orientation, field-of-view). # Moves are interpolated with sinusoidal characteristic. There's only one # instance of this class, available as view.point. # # Usage: #view.point.save();... save current view and return reference to # saved values in the form of a props.Node # #view.point.restore(); ... restore saved view parameters # #view.point.move(prop [, time]); # ... set view parameters from a props.Node with # optional move time in seconds. prop may be # nil, in which case nothing happens. # # A parameter set as expected by set() and returned by save() is a props.Node # object containing any (or none) of these children: # ..so , as usual , Melchoir seems to have already added this option ... now I just have to figure out how to use it :) -- SydSandy [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] view options : new idea
--- SydSandy [EMAIL PROTECTED] wrote: On mer 26 décembre 2007, SydSandy wrote: Hi all... Just had another thought ... Maybe a simpler idea would be to have the sim/view/config/field-of-view property added to the autosave function ? This way it could be set per aircraft but that still means editing the properties in the property browser ... just thinking out loud :) Cheers I see in view.nas there IS this... # Saves/restores/moves the view point (position, orientation, field-of-view). # Moves are interpolated with sinusoidal characteristic. There's only one # instance of this class, available as view.point. # # Usage: #view.point.save();... save current view and return reference to # saved values in the form of a props.Node # #view.point.restore(); ... restore saved view parameters # #view.point.move(prop [, time]); # ... set view parameters from a props.Node with # optional move time in seconds. prop may be # nil, in which case nothing happens. # # A parameter set as expected by set() and returned by save() is a props.Node # object containing any (or none) of these children: # ..so , as usual , Melchoir seems to have already added this option ... now I just have to figure out how to use it :) Well, to save you some time, try the patch included below.. It adds the FoV to the Adjust View Distance dialog, and adds a Reset button for when you've messed up. Melchior/other committers - if you're happy with it, I'll commit it. -Stuart Index: pilot_offset.xml === RCS file: /var/cvs/FlightGear-0.9/data/gui/dialogs/pilot_offset.xml,v retrieving revision 1.4 diff -u -r1.4 pilot_offset.xml --- pilot_offset.xml5 Nov 2005 18:42:29 - 1.4 +++ pilot_offset.xml26 Dec 2007 21:44:50 - @@ -69,6 +69,27 @@ property/sim/current-view/z-offset-m/property /text /group + + group + layoutvbox/layout + + textlabelFoV/label/text + dial +wrapfalse/wrap +min1/min +max120/max +stretchtrue/stretch +property/sim/current-view/field-of-view/property +bindingcommanddialog-apply/command/binding + /dial + + text +label100.00 deg/label +format%-0.2f deg/format +livetrue/live +property/sim/current-view/field-of-view/property + /text + /group /group group @@ -79,9 +100,19 @@ equaltrue/equal defaulttrue/default keyEsc/key - bindingcommanddialog-apply/command/binding bindingcommanddialog-close/command/binding /button + button + legendReset/legend + binding + commandnasal/command + script + view.resetFOV(); + view.resetViewPos(); + /script +/binding +bindingcommanddialog-update/command/binding + /button emptystretchtrue/stretch/empty /group /PropertyList __ Sent from Yahoo! Mail - a smarter inbox http://uk.mail.yahoo.com - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] view options : new idea
On Wed, 26 Dec 2007 21:49:19 + (GMT) Stuart Buchanan [EMAIL PROTECTED] wrote: --- SydSandy [EMAIL PROTECTED] wrote: On mer 26 décembre 2007, SydSandy wrote: Hi all... Just had another thought ... Maybe a simpler idea would be to have the sim/view/config/field-of-view property added to the autosave function ? This way it could be set per aircraft but that still means editing the properties in the property browser ... just thinking out loud :) Cheers I see in view.nas there IS this... # Saves/restores/moves the view point (position, orientation, field-of-view). # Moves are interpolated with sinusoidal characteristic. There's only one # instance of this class, available as view.point. # # Usage: #view.point.save();... save current view and return reference to # saved values in the form of a props.Node # #view.point.restore(); ... restore saved view parameters # #view.point.move(prop [, time]); # ... set view parameters from a props.Node with # optional move time in seconds. prop may be # nil, in which case nothing happens. # # A parameter set as expected by set() and returned by save() is a props.Node # object containing any (or none) of these children: # ..so , as usual , Melchoir seems to have already added this option ... now I just have to figure out how to use it :) Well, to save you some time, try the patch included below.. It adds the FoV to the Adjust View Distance dialog, and adds a Reset button for when you've messed up. Melchior/other committers - if you're happy with it, I'll commit it. -Stuart Index: pilot_offset.xml === RCS file: /var/cvs/FlightGear-0.9/data/gui/dialogs/pilot_offset.xml,v retrieving revision 1.4 diff -u -r1.4 pilot_offset.xml --- pilot_offset.xml 5 Nov 2005 18:42:29 - 1.4 +++ pilot_offset.xml 26 Dec 2007 21:44:50 - @@ -69,6 +69,27 @@ property/sim/current-view/z-offset-m/property /text /group + + group + layoutvbox/layout + + textlabelFoV/label/text + dial +wrapfalse/wrap +min1/min +max120/max +stretchtrue/stretch +property/sim/current-view/field-of-view/property +bindingcommanddialog-apply/command/binding + /dial + + text +label100.00 deg/label +format%-0.2f deg/format +livetrue/live +property/sim/current-view/field-of-view/property + /text + /group /group group @@ -79,9 +100,19 @@ equaltrue/equal defaulttrue/default keyEsc/key - bindingcommanddialog-apply/command/binding bindingcommanddialog-close/command/binding /button + button + legendReset/legend + binding + commandnasal/command + script + view.resetFOV(); + view.resetViewPos(); + /script +/binding +bindingcommanddialog-update/command/binding + /button emptystretchtrue/stretch/empty /group /PropertyList Thanks Stuart , I'll try it ... I haven't had any luck yet adding it to veiw.nas yet :) -- SydSandy [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] view options : new idea
On Wed, 26 Dec 2007 21:49:19 + (GMT) Stuart Buchanan [EMAIL PROTECTED] wrote: --- SydSandy [EMAIL PROTECTED] wrote: On mer 26 décembre 2007, SydSandy wrote: Hi all... Just had another thought ... Maybe a simpler idea would be to have the sim/view/config/field-of-view property added to the autosave function ? This way it could be set per aircraft but that still means editing the properties in the property browser ... just thinking out loud :) Cheers I see in view.nas there IS this... # Saves/restores/moves the view point (position, orientation, field-of-view). # Moves are interpolated with sinusoidal characteristic. There's only one # instance of this class, available as view.point. # # Usage: #view.point.save();... save current view and return reference to # saved values in the form of a props.Node # #view.point.restore(); ... restore saved view parameters # #view.point.move(prop [, time]); # ... set view parameters from a props.Node with # optional move time in seconds. prop may be # nil, in which case nothing happens. # # A parameter set as expected by set() and returned by save() is a props.Node # object containing any (or none) of these children: # ..so , as usual , Melchoir seems to have already added this option ... now I just have to figure out how to use it :) Well, to save you some time, try the patch included below.. It adds the FoV to the Adjust View Distance dialog, and adds a Reset button for when you've messed up. Melchior/other committers - if you're happy with it, I'll commit it. -Stuart Index: pilot_offset.xml === RCS file: /var/cvs/FlightGear-0.9/data/gui/dialogs/pilot_offset.xml,v retrieving revision 1.4 diff -u -r1.4 pilot_offset.xml --- pilot_offset.xml 5 Nov 2005 18:42:29 - 1.4 +++ pilot_offset.xml 26 Dec 2007 21:44:50 - @@ -69,6 +69,27 @@ property/sim/current-view/z-offset-m/property /text /group + + group + layoutvbox/layout + + textlabelFoV/label/text + dial +wrapfalse/wrap +min1/min +max120/max +stretchtrue/stretch +property/sim/current-view/field-of-view/property +bindingcommanddialog-apply/command/binding + /dial + + text +label100.00 deg/label +format%-0.2f deg/format +livetrue/live +property/sim/current-view/field-of-view/property + /text + /group /group group @@ -79,9 +100,19 @@ equaltrue/equal defaulttrue/default keyEsc/key - bindingcommanddialog-apply/command/binding bindingcommanddialog-close/command/binding /button + button + legendReset/legend + binding + commandnasal/command + script + view.resetFOV(); + view.resetViewPos(); + /script +/binding +bindingcommanddialog-update/command/binding + /button emptystretchtrue/stretch/empty /group /PropertyList Hi Stuart , kind of what I had in mind , now all we need is a SAVE button to copy sim/current-view/field-of view to sim/view[number]/config/default-field-of-view-deg once the user is happy with it :) Cheers -- SydSandy [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
