User Tools

Site Tools


configuration

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

configuration [2016/09/01 10:53]
127.0.0.1 external edit
configuration [2016/10/10 23:11] (current)
editor
Line 1: Line 1:
 // Work in Progress. //  // Work in Progress. // 
  
-ToDoList can store configuration data in either a common .INI file, or in the Registry. This is determined ​at by a user prompt at installation time.+ToDoList can store configuration data in either a common .INI file, or in the Registry. This is determined by a user prompt at installation time.
  
 ====== The .INI File====== ====== The .INI File======
  
-===== The basics of .ini configuration file=====+===== The basics of the .ini configuration file=====
  
 The .ini file consists of sections and name/value pairs (also called key/​values). The following is an example of the beginning of such a file: The .ini file consists of sections and name/value pairs (also called key/​values). The following is an example of the beginning of such a file:
  
- [[keyboardshortcuts|KeyboardShortcuts]+<​code>​ 
- NumItems=67 +[KeyboardShortcuts] 
- ShowCommandIDs=0+NumItems=67 
 +ShowCommandIDs=0
  
- [[tools|Tools]+[Tools] 
- ToolCount=7 +ToolCount=7
- +
- [[preferences|Preferences]] +
- AddFilesToMRU=1 +
- AddLoggedTimeToTimeSpent=1 +
- AddLoggedTimeUnits=72+
  
 +[Preferences]
 +AddFilesToMRU=1
 +AddLoggedTimeToTimeSpent=1
 +AddLoggedTimeUnits=72
 +</​code>​
 ===== INI file location===== ===== INI file location=====
  
-Most users don't care about the contents of the file, only its location. For a new installation,​ the default configuration file is ToDoList.ini,​ in the root folder along with the .exe and .dll files. At startup, the ToDoList.exe tests to see if its folder location is writable by trying to create a temporary file. If the folder is *not* writable then the .ini file will be saved to   +Most users don't care about the contents of the file, only its location. For a new installation,​ the default configuration file is ToDoList.ini,​ in the root folder along with the .exe and .dll files. At startup, the ToDoList.exe tests to see if its folder location is writable by trying to create a temporary file. If the folder is __not__ ​writable then the .ini file will be saved to\\  
-**C:\Users\\ <​user>​ \Application Data\Abstractspoon\ToDoList**+**C:​\Users\<​user>​\Application Data\Abstractspoon\ToDoList** 
 + 
 +Some users save ToDoList into the Program Files folder, but this is not recommended. Depending on how the application is being run and system-specific permissions settings, Windows may transparently save the file to a different folder:\\  
 +**C:​\Users\<​user>​\AppData\Local\VirtualStore\Program Files (x86)\ToDoList**
  
-Some users save ToDoList into the Program Files folder, but this is not recommended. Depending on how the application is being run and system-specific permissions settings, Windows may transparently save the file to a different folder:  ​ 
-**C:​\Users\\ <​user>​ \AppData\Local\VirtualStore\Program Files (x86)\ToDoList**  ​ 
 That can be confusing. The reason for this is that Windows is a multi-user environment,​ and most configuration data is unique per-user. So apps should never write configuration data to the one and only "​Program Files" path because that's shared by all users. However, installing ToDoList under Program Files is a choice made by individuals (and completely understood) but as seen here there are technical consequences for that decision. To help with this common problem, Microsoft made it so that when an individual user runs an app that tries to save configuration data in the Program Files path, it may (depending on permissions) transparently save the file under the AppData VirtualStore folder. That avoids a collision of different user settings, and while useful, it's also confusing to those of us who just have one person per system. That can be confusing. The reason for this is that Windows is a multi-user environment,​ and most configuration data is unique per-user. So apps should never write configuration data to the one and only "​Program Files" path because that's shared by all users. However, installing ToDoList under Program Files is a choice made by individuals (and completely understood) but as seen here there are technical consequences for that decision. To help with this common problem, Microsoft made it so that when an individual user runs an app that tries to save configuration data in the Program Files path, it may (depending on permissions) transparently save the file under the AppData VirtualStore folder. That avoids a collision of different user settings, and while useful, it's also confusing to those of us who just have one person per system.
  
Line 40: Line 42:
 ===== Config file details===== ===== Config file details=====
  
-Some sections are broken up simply for convenience. For example, there are sections for [[preferences|Preferences]], [[preferences\attribuse|Preferences\AttribUse]], [[preferences\colors|Preferences\Colors]], etc. And there are other sections which are based on a template, where each section is like the others but unique in its own way. For example"​+Some sections are broken up simply for convenience. For example, there are sections for [Preferences],​ [Preferences\AttribUse],​ [Preferences\Colors],​ etc. And there are other sections which are based on a template, where each section is like the others but unique in its own way. For example"​
  
- [[keyboardshortcuts\item00|KeyboardShortcuts\Item00]+<​code>​ 
- CmdID=57670 +[KeyboardShortcuts\Item00] 
- Shortcut=112+CmdID=57670 
 +Shortcut=112
  
- [[keyboardshortcuts\item01|KeyboardShortcuts\Item01]+[KeyboardShortcuts\Item01] 
- CmdID=32934 +CmdID=32934 
- Shortcut=131142+Shortcut=131142 
 +</​code>​
  
 Those sections both define shortcuts. All KeyboardShortcuts sections look the same. Those sections both define shortcuts. All KeyboardShortcuts sections look the same.
  
-Notice that the [[keyboardshortcuts|KeyboardShortcuts]] section above defines NumItems=67. Looking into a .ini file you might see the sections listed like this:+Notice that the [KeyboardShortcuts] section above defines NumItems=67. Looking into a .ini file you might see the sections listed like this:
  
- [[keyboardshortcuts\item55|KeyboardShortcuts\Item55]+ [KeyboardShortcuts\Item55] 
- [[keyboardshortcuts\item56|KeyboardShortcuts\Item56]+ [KeyboardShortcuts\Item56] 
- [[keyboardshortcuts\item57|KeyboardShortcuts\Item57]+ [KeyboardShortcuts\Item57] 
- [[pos|Pos]+ [Pos] 
- [[version|Version]+ [Version] 
- [[settings|Settings]+ [Settings] 
- [[findtasks|FindTasks]+ [FindTasks] 
- [[findtasks\searches|FindTasks\Searches]+ [FindTasks\Searches] 
- [[updates|Updates]+ [Updates] 
- [[keyboardshortcuts\item58|KeyboardShortcuts\Item58]+ [KeyboardShortcuts\Item58] 
- [[keyboardshortcuts\item59|KeyboardShortcuts\Item59]]+ [KeyboardShortcuts\Item59]
  
-The order of the sections and the name/value pairs is not important. And sections do not need to be grouped together. This may be significant when looking ​in this file for sections and keys.+The order of the sections and the name/value pairs is not important. And sections do not need to be grouped together. This information ​may be helpful as you look in this file for sections and keys.
  
configuration.txt · Last modified: 2016/10/10 23:11 by editor