DOE: Locations Extension

[zeracool2k]

Hello,
the "nil" error when typing any character occurs when you create a <<new something>> and then create <<another something>> without naming the first.

It has happened consitently when I change tabs with an unnamed element, but I said nothing because it had already been posted in earlier pages.

[damned]

Hello,
the "nil" error when typing any character occurs when you create a <<new something>> and then create <<another something>> without naming the first.

It has happened consitently when I change tabs with an unnamed element, but I said nothing because it had already been posted in earlier pages.

zeracool2k Im almost positive that this matches my scenario. im pretty sure that I did create 2 new entries before editing the first.
And - confirmed - I have just confirmed that is exactly what is happening and it continue to happen as long as you have on or more of these <<new somethings>>

[dulux-oz]

Hi Guys,

OK, for the life of me I cannot reproduce this error (the 348 one) - I've tried (or think I've tried) every combination you guys have told me about, but I can't do it!

Would someone please be able to list (in excruciating detail) exactly what they did to get this error - thanks.

[damned]

here you go.



Create a new location.
Dont touch it.
Create another new location.
Attempt to edit the Location name.

[dulux-oz]

Nope, can't reproduce it (or should that be )

[damned]

I just tested it with Organisations and same thing.
One other thing Ive just remembered - Im on 3.1.6 as Im testing some other stuff.

[zeracool2k]

Dulux-Oz, maybe the irreproducibility of the error is due to the configuration of your programming environment? The error is an "attempt to index a nil value", which means it may not show for you given that all your "path" variables are set as they should.

Perhaps if you tried it on another device?

By the way, I'm using FG 3.1.5, so I don't think the error is related to the FG version... oh, and here is a video of the error (will be removed shortly).

[dulux-oz]

Right, I've determined what the issue is, now I've got to relove it - so we're making progress.

It appears to be a db save issue ie the system is trying to access information from the database that doesn't yet exist in the database, only in the memory copy of the database which is yet to be written to disk - could someone try this:

In a virgin campaign, create two new Locations, issue a /save command in the chat window, and then try to change the name of one of the new locations - thanks

[damned]

i dont think FG ever reads from the disk version of the DB once the session has loaded?
either way - it didnt make any difference - same behaviour using the /save

the work around from a user perspective is of course to label both or only create one at a time so its not a show stopper by any means.

[dulux-oz]

Yeah, it does - if you explicitly request it (and the DOEs do) - or at least it appears to. Bottom line is that there are times when data isn't where its supposed to be and a /save always resolves those times - so I then write code to handle the situation and everythings OK from that point on.

So that was with a brand new campaign? Damn! There goes a potential solution - back to the drawing board!

Thanks mate