|
Kanonball Novice
Joined: 06 Feb 2006 Posts: 48
|
|
|
|
Vijilante SubAdmin
Joined: 18 Nov 2001 Posts: 5182
|
Posted: Sun Dec 03, 2006 4:31 am |
This is generally not possible because the selection can include multiple types of settings.
|
|
_________________ The only good questions are the ones we have never answered before.
Search the Forums |
|
|
|
Kanonball Novice
Joined: 06 Feb 2006 Posts: 48
|
Posted: Sun Dec 03, 2006 12:55 pm |
i suppose one might expect a lowest common denominator in such cases, but it doesn't work even if you select a few of only the same type
|
|
|
|
MattLofton GURU
Joined: 23 Dec 2000 Posts: 4834 Location: USA
|
Posted: Sun Dec 03, 2006 9:28 pm |
Quote: |
This is generally not possible because the selection can include multiple types of settings.
|
I don't think this is the reason. After all, the same behavior works in Zugg's Delphi IDE as well as Delphi's various competitor's IDEs and the various products created with those tools. Probably more due to the fact that Zugg didn't design zScript with inheritence in mind, thus it's possible that some of the common attributes behave a bit differently across different settings (in other words, in terms of zScript a trigger is a completely unrelated class than an alias despite what attributes they would seem to share). |
|
_________________ EDIT: I didn't like my old signature |
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Mon Dec 04, 2006 10:35 pm |
Actually, CMUD *does* use class inheritance. For example, every setting has an Enabled property, and a Name property. But an Alias doesn't have a "Case Sensitive" option like a trigger does.
However, each setting does have an Options field, which is an integer bit field. But the interpretation of these bit values is different for each setting type. So just copying the options field from one setting to another of a different type would have lots of bad effects.
And because your selection can contain settings of different types, there is no easy way to do this. Maybe someday in the future I'll add something like this, but not for now. |
|
|
|
|
|