• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

Errors when I switch data sets

Erich

Well-known member
Hi,
I seem to be having a problem when I try to load a data set that is not the Space 1889 set I'm working on.

I'm getting the error messages
Code:
Attempt to access non-live child pick 'trStatus' from script
Location: 'eval' script for Thing 'MechStFlrC' (Eval Script '#2') near line 1

Attempt to access non-live child pick 'trStatus' from script
Location: 'eval' script for Thing 'MechStFlrC' (Eval Script '#1') near line 2

The program still works fine, but I keep having to click through the error dialog.

Any ideas?

-Erich
 
What is the data set? Presumably it's a problem with the "MechStFlrC" thing in that new dataset. Also, do you move your 1889 .user file someplace else before trying to load the one or do you just have all your .user files in the data directory all at once? (The latter is not necessarily a problem as long as you manage your sources well enough and there are no duplicate names.)
 
I was trying to load my Hellfrost data, but I have seen the same errors when just trying to load the vanilla Savage Worlds stuff.
All of my data sets are in the same folder. I just make sure to use unique names for stuff.

-Erich
 
Unique names helps in part, but it's also possible if things don't get sourced right that you could run into conflicts as well, not that I think that error is necessarily one of those, mind you. I'm guessing the problem is on the Mechanic tab (although I would normally expect the name for that to be with a lower-case "mech" and if they are following the 2-letter convention it must be in something that fist "St" in the setting name. Maybe even "StFlrC"? Is there something like that in any of those .user files?

If it helps any I like to use a program called Windows Grep for doing searches in files. It lets you search whole directories and even sub-directories for text and if you weren't sure where that might be in you could search for it using a program like that. Then you'll know which .user file it's in and can either pull it up in the Editor or in something like Notepad++ (since Grep will even tell you what line number it found the text on.)
 
OK, adding the 89 to the names (and sourcing to the 1889 file) fixed the problem.
I THOUGHT I had sourced everything :rolleyes:.
Oh well, everything works now.

Thanks

-Erich
 
Believe me, I know that problem all too well. For making sure you have sources I find it easiest to try to just, fairly quickly, scroll through each tab and item in the Editor looking at the "Source" button to make sure it has the "x1" next to it. If it has more than x1 then you probably need to fix something there, but it's not always easy to notice the number depending on how quickly you scroll through. So I follow that up with opening the .user file in Notepad++, setting the Language to XML and then hitting Ctrl-F to search for:

source="

That way I can just keep hitting "Next" and eyeball each of the sources I have in the file to find any that aren't what my source should be. The cool thing about Notepad++ is either I can change it there or, what I normally do, is if I change it in the Editor and then save the file Notepad++ will notice the change, ask if I want to reload the file (to which I say Yes) and then it still remembers exactly where you were in the file so you can just keep on truckin' right where you left off.

Hope that helps!
 
Yeah, notepad++ is a favorite of mine, I discovered it when I was taking web design classes in collage.
This Grep file though, I've heard of it but never used it.
I should probably look into that...

-Erich
 
Back
Top