XML question

[DanKH]

OK... I have the autopilot in its own window in the panel.cfg

How do I secure that the autopilot is activated even if the Autopilot window is not visible/closed ....

[JimCooper]

The 'Z' key on the keyboard??

[DanKH]

:-)

Well not exactly ....

Say I open the AP-window and activate the Autopilot ....

when I reach Cruise altitude, and have stabilized, I want to "clean up" and thus closes the overlay AP-window. But as I do so the Autopilot disengage ... how can i adjust my XML code to prevent this...

[DaveB]

This is gonna sound like a ridiculous question Dan but why are you making windows appear and disappear using XML?? You seem to be going to extremes in order to make FSX work like FS9 did. Why the hell don't you go back to FS9?? Is it the challenge or do you like wasting your time

ATB

DaveB

[DanKH]

OK, this is getting a bit out of hand :-) or maybe I'm not that good at explaining my problem....

I do NOT want to make windows appear and disappear through XML ....

I have a perfect good working XML code behind my AP.... well almost

In the flightdeck I open the AP-window ... click on the AP and everything is bliss ... until the moment I close the window again ... the AP disengage if I do that ...

I do NOT want the AP to disengage until I deliberately click it ....

[Garry Russell]

I think I understand you Dan

You open the AP window and the AP is on, then you close the window and the AP is turning off as well instead of continuing to run in the background.

So for some reason the AP turning off is directly linked to closing the window and all you want is to seperate the two so that the window opens and closes independantly of the AP fuction turning on and off.

Garry

[DanKH]

Apart from the fact that initially the AP isn't turned on, until I do it .... (the normal way)

Actually I think the only link there is, is that the AP turns off when closing the window .... it doesn't turn on by opening ....

[DaveB]

Yes.. even I understand you now

I can't tell you how to fix it but I get similar happen in FS9 on certain models IF I have clicked on my second monitor to see what FSNav is doing. Fortunately, I hear a 'click' and know what has happened as it's happened before. I can qualify this further by saying that it definitely ONLY happens if I am in spot view and I've clicked on the second monitor. It does NOT happen if I am 'on the flightdeck' in monitor 1 and fiddle with FSNav on monitor 2. However, IF I click on the second monitor for whatever reason.. I have to 'click' again on monitor 1 (anywhere will do) in order to ensure that monitor 1 is the 'active' monitor. For example.. if I didn't do that, I could sit there till the cows come home trying to use the mousewheel to adjust a setting on the AP (as an example) and nothing would happen. If I 'click' on the same switch/knob.. it makes that monitor 'live' again.

It probably has nothing at all to do with your problem but there might be something there that a clever chap like you can suss out

ATB

DaveB

[DanKH]

Thanks for the input ... yes I was thinking about something like it being the active window or something .....

Well half-way is to understand the problem ... now I only need to fix it

[DaveB]

Hi Dan..

If you're running FSX fullscreen, perhaps you could try windowed (or vice versa) to see if it still happens

ATB

DaveB