Re: WinXP - Win 8 --- something I need to know ?!?
Posted: Tue Oct 22, 2013 12:46 am
interesting news back from beta-tester ...
I made an exact copy of the VST ... but exported as an EXE file.
The entire Saving AND loading process is WORKING. It can both create the folder and the configuration file ...and then successfully load it back in for distribution around the plugin.
The only difference ... this is an EXE. The VST is not working ... the file is not loaded
Same program ... different app structure.
I don't know what this means overall, but wanted to report back what has been tested.
So many questions now come up ... like, what happens with the PreSet Manager [in VST] ... can it load/save a file ... because this simple config file won't. Trying to load in a registration serial number ... is this going to have an issue ???
Knowing that I'm now not the only one facing this issue ... I'm a bit stunned that I've not read of this major issue so blatantly. [Unless everyone else already knows how to deal with this].
My 'tester' is a bit of a Geek
, and is active in beta testing ... he says that forcing a user to allow special privileges is a real negative out there ... they call it 'lazy' programming. Well ... maybe this is so ... but I'm not aware how to solve this properly.
I'm seeking 1 reliable location to store and read a text file, without forces the user to do anything special ... like other apps he installs.
The mention of the C:\Users folder is one that I also have on my XP system. There is another folder inside called 'Public'. Is this the place available to use ??? Is it called the same name regardless of language or OS ???
If so ... do I 'hard code' to this location, or can the SYSFolder prim have an environmental viable set to locate this ??
I know ... bunch of questions ... but in order for me to test any of this, I have to indulge someone else's time. [and this has exceeded all time expectations] ... but a solid solution is needed, otherwise there is no apps to develop.
Calling all the 'Experienced Ones' ... desperately need help here ... I would think everyone would be affected by this at some point.
Sincerely ... Thank-you for what's been posted, and continued advice and guidance.
I made an exact copy of the VST ... but exported as an EXE file.
The entire Saving AND loading process is WORKING. It can both create the folder and the configuration file ...and then successfully load it back in for distribution around the plugin.
The only difference ... this is an EXE. The VST is not working ... the file is not loaded
Same program ... different app structure.
I don't know what this means overall, but wanted to report back what has been tested.
So many questions now come up ... like, what happens with the PreSet Manager [in VST] ... can it load/save a file ... because this simple config file won't. Trying to load in a registration serial number ... is this going to have an issue ???
Knowing that I'm now not the only one facing this issue ... I'm a bit stunned that I've not read of this major issue so blatantly. [Unless everyone else already knows how to deal with this].
My 'tester' is a bit of a Geek
I'm seeking 1 reliable location to store and read a text file, without forces the user to do anything special ... like other apps he installs.
The mention of the C:\Users folder is one that I also have on my XP system. There is another folder inside called 'Public'. Is this the place available to use ??? Is it called the same name regardless of language or OS ???
If so ... do I 'hard code' to this location, or can the SYSFolder prim have an environmental viable set to locate this ??
I know ... bunch of questions ... but in order for me to test any of this, I have to indulge someone else's time. [and this has exceeded all time expectations] ... but a solid solution is needed, otherwise there is no apps to develop.
Calling all the 'Experienced Ones' ... desperately need help here ... I would think everyone would be affected by this at some point.
Sincerely ... Thank-you for what's been posted, and continued advice and guidance.