Support Board
Date/Time: Wed, 25 Dec 2024 06:03:48 +0000
directories
View Count: 1183
| [2015-05-21 14:37:36] |
| jesslinn - Posts: 108 |
|
This is a low priority suggestion to clean up the SC use of directories (folders). I have a number of different chartbooks, dlls, and Study Collections that I share between multiple instances of SC. All of these are very different than data, which cannot be shared. It is esthetically unpleasing to place these shared files with unshared data. More importantly, while collections and dlls do not change that frequently, and it is possible to synchronize them externally, the interface for opening chartbooks, when not in the data folder, is annoying, since one must click on folder, navigate to a folder, click ok, click on a chartbook, click ok. Please allow us to set a default chartbook directory or have open chartbooks start in the last folder selected. It would also be nice to be able to set at least one directory for the other non-data files so that they are not mixed with the data which has very different handling. I, of course, already use the setting of the data folder to separate program files that can change with a new release from the persistent files. It would be ideal if one could specify directories for the config files, trade data, and log files that are stored in the program directory and are of very different character than those files which come with a clean install. |
| [2015-05-23 10:48:54] |
| |
|
What we can do is remember the last folder used when opening a Chartbook.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [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
|
| [2015-11-06 05:09:17] |
| |
|
Some of these things can lead to conflicts unless the user is careful. The general problem with what you suggest is that when there is a problem, it makes resolving the problem much more difficult and confusing and often the burden is on upon us. Also please read this: Notice: Suggestions (Currently not accepting) Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
To post a message in this thread, you need to log in with your Sierra Chart account: