Re: SAVE/LOAD multi-size arrays - must b better way
Posted: Fri Oct 18, 2013 8:25 pm
Thank-you TROG ... as usual, a lot of information to absorb.
I've assembled a modified schematic that centers around the Marshal routine you supplied.
I've kept your 'Save Load Application Data settings file' module as the reference model that handles the Directory Management.
I'm definately not comfortable playing RUBY when it comes to writing files or folders ... I've just not had any experience in those functions ... and won't want to tempt a possible disaster.
My lame-a** solution would probably look to a 'primitive' front-end. That would be a challenge enough
Posting the schematic ....
It would be nice if someday I could help someone else
**** EDIT ****
Updated schematic with 1st draft of Dir Management [Prims]
Added Dir checking, FIND, Folder Create, confirmation LEDs, and routed the AUTO-LOAD after a SAVE.
This is still a 1st draft test of the idea.
oh ... wanted to comment on Trogs earlier post
With my earlier routine, I had wondered if 'file permissions' was a factor. At this point, I still think it was my shoddy programming
The reason I had gone the 're-load' route was actually to deal with my programs criteria. The User will have a special 'Patch list' file in XML format. I have them load this file into my VST, from which I parse, bend, fold, sort and organize into special groups. I wanted this to be a one time procedure. so I then have the app save off a configuration file [along with some other User settings]. Then, this new config file gets auto-loaded at run time. Most all of this config data is being routed around the schematic, filling up pull-down menus that now contain the patch names and PRGCHG numbers. These are used in the MIDI stream to control 'external' VST.
It needs to be a very dynamic file system, as I would never know the contents or amount of the Users XML. This Marshal routine provided the perfect solution, as the grouping and number of entries are easily maintain. This has greatly simplified the schematic. Secondly, the way You presented it allows even ME to customize it
The front-end piece is what I need to finalize. It obviously must work flawless. I'm testing the PRIM concept, and it does 'seem' to be working. But, as we are dealing with computers and various OS's ... 'seems to work' is not much of a confidence builder
Sure appreciate to check over the shoulder to correct where I might have gone wrong or overlooked!
Thanks !!!
I've assembled a modified schematic that centers around the Marshal routine you supplied.
I've kept your 'Save Load Application Data settings file' module as the reference model that handles the Directory Management.
I'm definately not comfortable playing RUBY when it comes to writing files or folders ... I've just not had any experience in those functions ... and won't want to tempt a possible disaster.
My lame-a** solution would probably look to a 'primitive' front-end. That would be a challenge enough
Posting the schematic ....
It would be nice if someday I could help someone else
**** EDIT ****
Updated schematic with 1st draft of Dir Management [Prims]
Added Dir checking, FIND, Folder Create, confirmation LEDs, and routed the AUTO-LOAD after a SAVE.
This is still a 1st draft test of the idea.
oh ... wanted to comment on Trogs earlier post
Your logic seems sound enough - verify the contents of the save by re-loading; useful as you might otherwise not see it if the save fails for some reason. Windows 7/8 can be buggers for this as they'll sometimes not save a file as expected because of file permission, but without displaying any error!
With my earlier routine, I had wondered if 'file permissions' was a factor. At this point, I still think it was my shoddy programming
The reason I had gone the 're-load' route was actually to deal with my programs criteria. The User will have a special 'Patch list' file in XML format. I have them load this file into my VST, from which I parse, bend, fold, sort and organize into special groups. I wanted this to be a one time procedure. so I then have the app save off a configuration file [along with some other User settings]. Then, this new config file gets auto-loaded at run time. Most all of this config data is being routed around the schematic, filling up pull-down menus that now contain the patch names and PRGCHG numbers. These are used in the MIDI stream to control 'external' VST.
It needs to be a very dynamic file system, as I would never know the contents or amount of the Users XML. This Marshal routine provided the perfect solution, as the grouping and number of entries are easily maintain. This has greatly simplified the schematic. Secondly, the way You presented it allows even ME to customize it
The front-end piece is what I need to finalize. It obviously must work flawless. I'm testing the PRIM concept, and it does 'seem' to be working. But, as we are dealing with computers and various OS's ... 'seems to work' is not much of a confidence builder
Sure appreciate to check over the shoulder to correct where I might have gone wrong or overlooked!
Thanks !!!