Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Fri, 03 May 2024 06:46:13 +0000
Post From: directories
| [2015-11-06 01:07:22] |
| jesslinn - Posts: 108 |
|
Thank you for adding the last folder bit. Note that if you store cht files anywhere but the data directory, the "Files To Open on Startup" will not work. This mechanism looks for the base file name in the data directory. It would be great to remember a relative path name as well as the base file name. It would still be neat and convenient to be able to set one or more separate folders in order to be able to separate files with completely different use cases. It would also be nice to use a more normal file open widget where it is not necessary to select the folder and then the file rather than just drilling down to the file. Here are some possible directories: INSTALLATION(globally sharable): It would be a great deal more convenient to install or upgrade only once. This is opposed to installing or upgrading many times, once for each combination of user, instance, and Intraday Data Storage Time. Obviously, this would require moving the rest of the config data (Accounts, GlobalSettings, Order info, ini, cfg,Trade data) out of the installation directory to a CONFIG directory. CONFIG: Just about every other program that I know of that needs configuration, allows the configuration (folder or file) to be set on the command line or with an environment variable. This capability would be great even if the users have to manually copy all txt, config, xml, ini, dat, and data files from the installation directory. With this one could install or upgrade once and run it for every desired instance. DATA: dly and scid files only CHARTS: charts, study collections, and all the other things that a user could share between different instances by specifying a directory. If these things are in the Data directory along with scid and dly files, they cannot be shared. LIBRARY: It would be convenient to be able to specify the directory where an instance looks for dll files. Currently, if I want to build a release and debug version of custom dlls I have to have separate instances for each, and separate installs for every instance. Wouldn't it make more sense to install two sets of dlls and then be able to share them with all the different instances? Again, these are low-priority suggestions. SC is great and all of this stuff can be worked around. I think, perhaps, that someone there actually thinks that it is desirable to "Always Use Data Folder Within Main Folder", and I want to share a very different point of view (i.e. Never Store Data in Main Folder). Date Time Of Last Edit: 2015-11-06 01:08:52
|