2009/7/16  <juan at jvuletich.org>:
>>
>> On 16.07.2009, at 02:47, Juan Vuletich wrote:
>>
>>> Bert Freudenberg wrote:
>>>>
>>>> On 13.07.2009, at 04:41, Juan Vuletich wrote:
>>>>
>>>>> Bernhard Pieber wrote:
>>>>>> Am 11.07.2009 um 23:51 schrieb Juan Vuletich:
>>>>>>> Yes. You need to do InputSensor swapMouseButtons: true . Please
>>>>>>> look at this method to see why. Some preferences are a bit
>>>>>>> "special" and setting the value in the Preferences dictionary is
>>>>>>> not enough.
>>>>>> Thanks. Now I see. Hmm, doesn't that make the Preferences
>>>>>> inspector quite useless for these preferences?
>>>>>
>>>>> Yes... :(
>>>>
>>>>
>>>> Err, you can register a method to be called whenever a preference
>>>> is changed.
>>>>
>>>> - Bert -
>>> Right! In this case instead of setting the 'value' instance variable
>>> in the preference, you'd do 'self preferenceValue: true'.
>>>
>>> Cheers,
>>> Juan Vuletich
>>
>>
>> No, what I meant is that even if you change a preference in the
>> preferences dialog, a method can be executed to make all adjustments
>> necessary. In fact, in my image the #swapMouseButtons preference does
>> inform InputSensor:
>>
>> (Preferences preferenceAt: #swapMouseButtons) longPrintString
>> 'name:        #swapMouseButtons
>> value:        false
>> defaultValue:         false
>> helpString:   ''if true, swaps mouse buttons 2 and 3''
>> localToProject:       false
>> categoryList:         #(#general)
>> changeInformee:       InputSensor
>> changeSelector:       #installMouseDecodeTable
>> viewRegistry:         a PreferenceViewRegistry
>> '
>>
>> - Bert -
>
> Cuis does not include the preferences dialog. That's why we are talking
> about the inspector.
>

oh, then you might try to integrate a new preference system, like
someone proposed - with pragmas and other stuff.


> Cheers,
> Juan Vuletich
>
>
>
>



-- 
Best regards,
Igor Stasenko AKA sig.