Settings Concept - Revision history

Frosch67 at 19:51, 1 March 2012

2012-03-01T19:51:44Z

← Older revision		Revision as of 21:51, 1 March 2012
Line 45:		Line 45:
	Only the Application Defaults get changed, others will not be touched. Only if you create a new project, the Project Defaults will be initialized with the new values.<br>		Only the Application Defaults get changed, others will not be touched. Only if you create a new project, the Project Defaults will be initialized with the new values.<br>
	Same applies if you change Project Defaults. Neither Application Default nor Element Configurations will be touched, unless you create a new Element. It's configuration will be initialized with the newly set Project Defaults.		Same applies if you change Project Defaults. Neither Application Default nor Element Configurations will be touched, unless you create a new Element. It's configuration will be initialized with the newly set Project Defaults.



			[[de:Settings-Konzept]]
			[[en:Settings_Concept]]

Frosch67 at 19:51, 1 March 2012

2012-03-01T19:51:09Z

← Older revision		Revision as of 21:51, 1 March 2012
Line 45:		Line 45:
	Only the Application Defaults get changed, others will not be touched. Only if you create a new project, the Project Defaults will be initialized with the new values.<br>		Only the Application Defaults get changed, others will not be touched. Only if you create a new project, the Project Defaults will be initialized with the new values.<br>
	Same applies if you change Project Defaults. Neither Application Default nor Element Configurations will be touched, unless you create a new Element. It's configuration will be initialized with the newly set Project Defaults.		Same applies if you change Project Defaults. Neither Application Default nor Element Configurations will be touched, unless you create a new Element. It's configuration will be initialized with the newly set Project Defaults.



	~~[[de:Settings-Konzept]]~~
	~~[[en:Settings_Concept]]~~

	~~__NOTITLE__~~

Frosch67 at 19:48, 1 March 2012

2012-03-01T19:48:33Z

← Older revision		Revision as of 21:48, 1 March 2012
Line 49:		Line 49:

	[[de:Settings-Konzept]]		[[de:Settings-Konzept]]
	[[en:~~settings-concept~~]]		[[en:Settings_Concept]]

	__NOTITLE__		__NOTITLE__

Frosch67 at 19:46, 1 March 2012

2012-03-01T19:46:52Z

← Older revision		Revision as of 21:46, 1 March 2012
Line 45:		Line 45:
	Only the Application Defaults get changed, others will not be touched. Only if you create a new project, the Project Defaults will be initialized with the new values.<br>		Only the Application Defaults get changed, others will not be touched. Only if you create a new project, the Project Defaults will be initialized with the new values.<br>
	Same applies if you change Project Defaults. Neither Application Default nor Element Configurations will be touched, unless you create a new Element. It's configuration will be initialized with the newly set Project Defaults.		Same applies if you change Project Defaults. Neither Application Default nor Element Configurations will be touched, unless you create a new Element. It's configuration will be initialized with the newly set Project Defaults.



			[[de:Settings-Konzept]]
			[[en:settings-concept]]

			__NOTITLE__

Lord-helmy at 20:26, 19 February 2012

2012-02-19T20:26:39Z

← Older revision		Revision as of 22:26, 19 February 2012
Line 4:		Line 4:
	We differentiate between two major Setting Types.<br>		We differentiate between two major Setting Types.<br>
	First there are Settings that let you configure how DMXControl behaves in certain situations. You can enable or disable Questions/Functions, etc.		First there are Settings that let you configure how DMXControl behaves in certain situations. You can enable or disable Questions/Functions, etc.
	Then there are Configurations. Most Elements like CueList, Executor or Live View will ~~habe~~ various Configuration Options like Names.<br>		Then there are Configurations. Most Elements like CueList, Executor or Live View will have various Configuration Options like Names.<br>
	<br>		<br>
	===Settings===		===Settings===

Fisl: /* Settings */

2012-02-19T20:07:25Z

Settings

← Older revision		Revision as of 22:07, 19 February 2012
Line 13:		Line 13:
	3) Kernel Settings (Project wide)<br>		3) Kernel Settings (Project wide)<br>

	1) Lets you configure how your GUI "feels like". An example would be: disable various Questions or set a default answers. ~~These~~ type of Setting is stored in the Resource Folder of the GUI. That means, different GUIs can have different Settings. This also includes that your GUI will "feel like the same" on every Kernel you connect to.		1) Lets you configure how your GUI "feels like". An example would be: disable various Questions or set default answers. This type of Setting is stored in the Resource Folder of the GUI. That means, different GUIs can have different Settings. This also includes that your GUI will "feel like the same" on every Kernel you connect to.

	2) Some Settings are Kernel Settings because they affect things in the Kernel. The best example would be it the Kernel should load the last project on startup. That wouln't make sense as GUI Setting, would it?		2) Some Settings are Kernel Settings because they affect things in the Kernel. The best example would be it the Kernel should load the last project on startup. That wouln't make sense as GUI Setting, would it?
Line 25:		Line 25:
	In the Project Explorer under Settings you will find categroy 3 Settings<br>		In the Project Explorer under Settings you will find categroy 3 Settings<br>
	<br>		<br>

	===Configurations===		===Configurations===
	Now let's move on to the second major Setting Type<br><br>		Now let's move on to the second major Setting Type<br><br>

Fisl at 15:41, 14 January 2012

2012-01-14T15:41:10Z

← Older revision		Revision as of 17:41, 14 January 2012
Line 41:		Line 41:
	If you create a new Element, lets say a new Executor. This Executor will get the configuration values you set as Project Defaults.<br>		If you create a new Element, lets say a new Executor. This Executor will get the configuration values you set as Project Defaults.<br>
	If you create a new Project, the Project Defaults will be set to the Application Defaults.<br>		If you create a new Project, the Project Defaults will be set to the Application Defaults.<br>
	If you change Application Defaults do Project Defaults or event the configuration of specific Elements get changed? NO!<br>		If you change Application Defaults do Project Defaults or event the configuration of specific Elements get changed? No!<br>
	Only the Application Defaults get changed, others will not be touched. Only if you create a new project, the Project Defaults will be initialized with the new values.<br>		Only the Application Defaults get changed, others will not be touched. Only if you create a new project, the Project Defaults will be initialized with the new values.<br>
	Same applies if you change Project Defaults. Neither Application Default nor Element Configurations will be touched, unless you create a new Element. It's configuration will be initialized with the newly set Project Defaults.		Same applies if you change Project Defaults. Neither Application Default nor Element Configurations will be touched, unless you create a new Element. It's configuration will be initialized with the newly set Project Defaults.

Fisl: Created page with "... or why do "the same" settings appear at different places.

First let me explain the basic concept behind all this.
We differentiate between two major Setting Type..."

2012-01-14T15:39:40Z

Created page with "... or why do "the same" settings appear at different places. First let me explain the basic concept behind all this. We differentiate between two major Setting Type..."

New page

... or why do "the same" settings appear at different places. 

First let me explain the basic concept behind all this. 
We differentiate between two major Setting Types. 
First there are Settings that let you configure how DMXControl behaves in certain situations. You can enable or disable Questions/Functions, etc.
Then there are Configurations. Most Elements like CueList, Executor or Live View will habe various Configuration Options like Names. 
 
===Settings===
Let me explain the Type "Setting" first: 
three categories of Settings exist: 
1) GUI Settings 
2) Kernel Settings (Application wide) 
3) Kernel Settings (Project wide) 

1) Lets you configure how your GUI "feels like". An example would be: disable various Questions or set a default answers. These type of Setting is stored in the Resource Folder of the GUI. That means, different GUIs can have different Settings. This also includes that your GUI will "feel like the same" on every Kernel you connect to.

2) Some Settings are Kernel Settings because they affect things in the Kernel. The best example would be it the Kernel should load the last project on startup. That wouln't make sense as GUI Setting, would it?

3) However there are some Settings that affect project specific things. For example if a new Executor Set should be created when a new Executor Page is added. 
What if you create a new Project? Are all these settings lost and you have to set them all again? 
No. Every Setting from this category also has a equivalent setting in category 2. So if you create a new Project all Settings will be initialized with the Application wide values.

So now where are the Places you can set all this? 
In the Main Menu under Settings -> Application Settings you will find category 1 and 2 Settings 
In the Project Explorer under Settings you will find categroy 3 Settings 
 
===Configurations===
Now let's move on to the second major Setting Type 
The so called "Configurations and Default Configurations" 
Nearly every Element in DMXControl has some configuration Options. Like Executors the Executor Type, or if the Live View shows Names or Numbers, etc. 
You must distinguisch between 3 Types 
1) Application Defaults 
2) Project Defaults 
3) Element Configuration 
You can find them here: 
1) Main Menu -> Settings -> Application Settings 
2) Project Explorer -> Settings or right click on the Branch in Project Explorer and open Properties. 
3) Select the Element you want to change the configuration of, right click and open Properties. You can select multiple Elements and change the configuration parameters for all at the same time. 

Why are there three different places and what affects what? 
If you create a new Element, lets say a new Executor. This Executor will get the configuration values you set as Project Defaults. 
If you create a new Project, the Project Defaults will be set to the Application Defaults. 
If you change Application Defaults do Project Defaults or event the configuration of specific Elements get changed? NO! 
Only the Application Defaults get changed, others will not be touched. Only if you create a new project, the Project Defaults will be initialized with the new values. 
Same applies if you change Project Defaults. Neither Application Default nor Element Configurations will be touched, unless you create a new Element. It's configuration will be initialized with the newly set Project Defaults.

Settings Concept - Revision history

Frosch67 at 19:51, 1 March 2012

Frosch67 at 19:51, 1 March 2012

Frosch67 at 19:48, 1 March 2012

Frosch67 at 19:46, 1 March 2012

Lord-helmy at 20:26, 19 February 2012

Fisl: /* Settings */

Fisl at 15:41, 14 January 2012

Fisl: Created page with "... or why do "the same" settings appear at different places. First let me explain the basic concept behind all this. We differentiate between two major Setting Type..."

Fisl: Created page with "... or why do "the same" settings appear at different places.

First let me explain the basic concept behind all this.
We differentiate between two major Setting Type..."