If you buy the jump planner, on top of LongRangeScanner, When you use F6-F6 to display the Galactic Map choose a system out of 7 LY's. then press F5 to display longrangescanner menu. You must see an option to display "Display Target System Info". Select that and another menu must be displayed.
You have the option to make cheat jumps to the selected system.
If it does not work could you please look for scripting errors on your latest.log and inform me if you can find any.
When you use F6-F6 to display the Galactic Map choose a system out of 7 LY's. then press F5 to display longrangescanner menu. You must see an option to display "Display Target System Info". Select that and another menu must be displayed.
You have the option to make cheat jumps to the selected system.
that's excatly what I've done ...
I'll have a look at the logs and keep you updated.
[script.javaScript.warning.ooliteDefinedError]: ----- JavaScript warning (LongRangeScanner 0.1): Incorrect usage: System instance property “info” accessed on constructor instead of instance. Replace “System.info” with “system.info”. This warning will be removed and the script will fail in Oolite 1.75.1.
[script.javaScript.warning.ooliteDefinedError]: ----- JavaScript warning (LongRangeScanner 0.1): Incorrect usage: System instance property “info” accessed on constructor instead of instance. Replace “System.info” with “system.info”. This warning will be removed and the script will fail in Oolite 1.75.1.
[script.javaScript.exception.unexpectedType]: ***** JavaScript exception (LongRangeScanner 0.1): TypeError: ships is null
[script.javaScript.exception.unexpectedType]: /home/or/.Oolite/AddOns/LongRangeScanner v0.1.oxp/Config/script.js, line 47.
I am glad it works fine now. But I discovered a bug in 1.75.0.4324 about missionScreenEnded
event is not raised.
Can you please confirm me by pressing F6-F6 and then F5 to display the lr menu and select one of the options and then press F1 for forward view. If the TAF is not set to 1 than there must be bug in Ooolite. I have already reported that bug. But I may be wrong.
I simply installed the LRS update to see if it works. I yet have to find a reason to use it as I normally don't do any contracts - the cargo bay is always full of "bounty hunting leftovers"
But I discovered a bug in 1.75.0.4324 about missionScreenEnded event is not raised.
I don't think this is a bug. The main use of the missionScreenEnded was to signal other oxps that they can set up a page of their own. However, before 1.74 it was forbidden to create a mission screen when not docked. Therefor it was deliberate that the missionScreenEnded did not fire when flying to prevent other oxp to set up a page for their own when in flight. I wasn't even aware that we had mission screens in flight until I saw your oxp. It has probably changed with the new 1.74 mission screen code.
To reinforce what Eric said, missionScreenEnded() shouldn’t be used in new development. Use missionScreenOpportunity() to show new screens, and mission.runScreen() completion callbacks to handle the end of a screen. (To show a sequence of screens, start a new screen in the runScreen() callback.)
Is that true for mission screens displayed during flight?
The stuff about runScreen() should be. missionScreenOpportunity() won’t fire in flight.
…so, in fact, there’s no way to defer an in-flight mission screen while another one is in effect, other than starting a timer and polling guiScreen. *peers over his spectacles at the person who hacked in in-flight mission screens*
.
