Oolite Bulletins

Switeck wrote:

I wish the newsflashes weren't just 1-time events. All too often I forget to check "F8" when I get a notice.
Could these be made to remain until you read them...and then disappear?
I feel like I'm missing important news.

Yes, seconded!

maik wrote:

Switeck wrote:

I wish the newsflashes weren't just 1-time events. All too often I forget to check "F8" when I get a notice.
Could these be made to remain until you read them...and then disappear?
I feel like I'm missing important news.

Yes, seconded!

It's nice to think people consider my four line throwaway witticisms "important" - gives me a nice warm glow inside.

Just proves that I'm a news junkie. If refreshing the OO board way too frequently doesn't already...

maik wrote:

Just proves that I'm a news junkie. If refreshing the OO board way too frequently doesn't already...

Well another 50 for chart 3 is on my to do list. I've spotted some trends in the descriptions so I'm hoping for good things.

Then I guess I haven't even seen yours yet, I'm currently in G7...

From memory there's some generic ones I did that appear everywhere (derived from the ones I did for Local Hero2) and then there's 50 chart 1 specific ones and 50 chart 2 specific ones, plus the ones that others inject (such as UPS) - eventually I'll do 50 for every chart.

I think I 'm through with Assassins Guild, so I can move on to G8, play Iron Raven (looking forward to that a lot!) and then swing round to G1 again and get the news

maik wrote:

I think I 'm through with Assassins Guild, so I can move on to G8, play Iron Raven (looking forward to that a lot!) and then swing round to G1 again and get the news

Iron Raven is a very good mission to play, being a test pilot I can tell that, when you finish that G5 may be interesting.

Okti wrote:

G5 may be interesting.

G5 has always been the most interesting sector.

maik wrote:

Switeck wrote:

I wish the newsflashes weren't just 1-time events. All too often I forget to check "F8" when I get a notice.
Could these be made to remain until you read them...and then disappear?
I feel like I'm missing important news.

Yes, seconded!

Indeed, you are missing important news then .-)

And OXPs like BlOomberg, Hyperradio or Missions like UPS-Courier or Vector are using newsflashes as well...
...and in these cases you are missing all these additional nice features and valuable infos.

Not sure, though, why you don't read them in the first place .-)

Will think about a way to keep the activation until player jumps.

Snoopers2.1.1 is online.

Changes:
- new property "Ori" for the model.
- keeps activation now until player jumps.
- new script_info key snoopersNews for non-main stations, not necessary for stations with hasNPCTraffic set to true.
- Documentation: http://wiki.alioth.net/index.php/Category:OXPDoc.

Thanks to Eric for the .hasNPCTraffic suggestion .-)

Hi, I had a crash and found this line about 100 times so I thought I would report it.

11:32:41.881 [script.javaScript.exception.unexpectedType]: ../AddOns/Snoopers2.1.1.oxp/Scripts/snoopers_modelview.js, line 50.
11:32:49.883 [script.javaScript.exception.unexpectedType]: ***** JavaScript exception (snoopers_modelview 2.1.1): TypeError: this.s is undefined


Hope it helps.

Fatleaf wrote:

Hi, I had a crash and found this line about 100 times so I thought I would report it.

11:32:41.881 [script.javaScript.exception.unexpectedType]: ../AddOns/Snoopers2.1.1.oxp/Scripts/snoopers_modelview.js, line 50.
11:32:49.883 [script.javaScript.exception.unexpectedType]: ***** JavaScript exception (snoopers_modelview 2.1.1): TypeError: this.s is undefined.

Its a but in Coyote run. So I assume you are playing the mission at the moment. It is Coyote run that is overwriting a snoopers mission screen. This results in an undefined variable in snoopers. Both authors are already aware of the problem. I assume Svengali will add a test to detect that his mission page was corrupted and probably will offer the scheduled message on a next docking.

Eric Walch wrote:

Fatleaf wrote:

Hi, I had a crash and found this line about 100 times so I thought I would report it.

11:32:41.881 [script.javaScript.exception.unexpectedType]: ../AddOns/Snoopers2.1.1.oxp/Scripts/snoopers_modelview.js, line 50.
11:32:49.883 [script.javaScript.exception.unexpectedType]: ***** JavaScript exception (snoopers_modelview 2.1.1): TypeError: this.s is undefined.

Its a but in Coyote run. So I assume you are playing the mission at the moment. It is Coyote run that is overwriting a snoopers mission screen. This results in an undefined variable in snoopers. Both authors are already aware of the problem. I assume Svengali will add a test to detect that his mission page was corrupted and probably will offer the scheduled message on a next docking.

Yep. The way I'm going now is a bit different. Snoopers will get a replay feature in case another OXP is overriding a Snoopers screen. I'm not sure though if Snoopers should try another callback in case of OXP inserted news and the inserting OXP expects a callback, because the callback has been done the first time already. Probably I'll add another property to give OXPs control about this handling.

Thanks Fatleaf and Eric!

Snoopers2.1.2 is online.

Changes:
- New property "Recall" added. If set and another OXPs overrides a Snoopers screen, the callback will be send again when the screen gets displayed again.
- Doc updated.