TrailMyx's Next Generation File System (TM_NGFS)

[TrailMyx]

You're welcome. heh

Heh, well you were the guinea pig for the rest, so thanks!  Here's some lettuce.

[Cerveza]

Insure all your items.... you'll be nekid soon.

[12TimesOver]

12X, you will be the tester of the DeleteName sub.

[/quote]
No dice but I'm not done making sure that I'm using everything correctly. I'm having some other save variable issues as well.

I'll post more as I figure out something valid LOL.

X

[TrailMyx]

That's ok, i'll be playing with it a bit more this weekend.  Playing with the fisherman again has given me a bit of encouragement.  I've got the urge to work a bit more on my SOS farmer.

But post up some code; the last bit was pretty obvious to me what was up.

[12TimesOver]

But post up some code; the last bit was pretty obvious to me what was up.

Sure thing!

Pretty straightforward and not really any different than what I posted last time so maybe it will indeed be quickly obvious!

Here is the Setup sub. I snipped the section where all of the variables get set as that is not the problem and makes for a long copy+paste!

Code: [Select]

sub Setup
   gosub TM_NGFS_DoesSaveExist XIIxMining
   If #RESULT
      {
    display yesno It looks like you've used this script before. Would you like to use the settings saved from your last session?
    if #dispres = yes
       {
         gosub TM_NGFS_InitializeScript XIIxMining
     gosub TM_NGFS_LoadVariables XIIxMining
     gosub LoadSavedSettings
       return
       }
      if #dispres = no
         gosub TM_NGFS_DeleteName XIIxMining
    }

   gosub TM_NGFS_InitializeScript XIIxMining
   gosub TM_NGFS_RegisterVariables XIIxMining std std RunebookID SecureID OreBagID StoneBagID BlkRkBadID JewelBagID ToTinker ToBank TravelMethod SecureGmpName SecureGmpSize
   
   gosub Display_M_Setup

   ;-----snipped a bunch of variable setting code here-----

   gosub TM_NGFS_SaveVariables XIIxMining
   gosub Display_M_Tracking
Return


[TrailMyx]

And what is it not doing?  

And one thing right off the bat....  In your instance of using the Delete, you really don't even need to do that.  Since you are reinitializing right after that, you are pretty much deleting anyhow.   The delete is meant more for overall filesystem management, and not for the user.  I was actually going to divide up the subs to "user" routines and "admin" routines.

[12TimesOver]

And what is it not doing?  

And one thing right off the bat....  In your instance of using the Delete, you really don't even need to do that.  Since you are reinitializing right after that, you are pretty much deleting anyhow.   The delete is meant more for overall filesystem management, and not for the user.  I was actually going to divide up the subs to "user" routines and "admin" routines.

I want to delete because I don't want any residual values left in the "script".

This morning before I left for work the Delete line seemed to do nothing (the Script reg key remained fully in tact). Also, there are values that I'm setting on the fly withint the setup routine that didn't seem to get saved (were still set to N/A) but this is the one I still need to mess with further to make sure it's not a logic issue on my part.

Unfortunately I'm at work so I have no access to test.

X

[TrailMyx]

Ok, I'll look at it this evening.  I think the snippet you posted should be enough.

The thing about residual values is if your save set isn't dynamic (i.e. varies in size), then every time you save, you will wipe out the previous set which is kinda like deleting.  The Delete routine is useful for a dynamic set of data that might change size and must range accordingly.  But it seems you are implying that you are operating in a more dynamic regime.

[Scrripty]

I'll get around to testing the delete functions on the waypoint farmer.  I'll use it when deleting a rail from the list.

[12TimesOver]

Ok, I'll look at it this evening.  I think the snippet you posted should be enough.

The thing about residual values is if your save set isn't dynamic (i.e. varies in size), then every time you save, you will wipe out the previous set which is kinda like deleting.  The Delete routine is useful for a dynamic set of data that might change size and must range accordingly.  But it seems you are implying that you are operating in a more dynamic regime.

Hmmm good point, I suppose a "Reset Settings" sub would be appropriate instead. Was just hoping for a nice, easy reset with the NGFS subs.

X

[TrailMyx]

I suppose you could just initialize again.  That clears the list of things tracked.  I haven't used this enough to find all the pitfalls that might be lurking out there.  Twinkle McNugget has much more experience with it.

[Scrripty]

Honestly I had no problems at all with the stuff I have used this for and if you saw all the rails Ive saved and loaded with it... Ive put it through its paces with no problems at all.

[TrailMyx]

Honestly I had no problems at all with the stuff I have used this for and if you saw all the rails Ive saved and loaded with it... Ive put it through its paces with no problems at all.

Are you using the latest subs, Twinkle McNugget?  I don't think I changed anything having to do with the core routines however.

[12TimesOver]

Honestly I had no problems at all with the stuff I have used this for and if you saw all the rails Ive saved and loaded with it... Ive put it through its paces with no problems at all.

[Scrripty]

I'm not using the new subs.  But load up the waypoint farmer, run around while recording a 1000 point rail.  That's 3000 variables.  Save it, then restart the script and load it.  Should work perfectly.  Plus it's tied in with the list subs too.