Border screen "artifacts" on dynamically moving button on Windows

[J. Landman Gay]

On 11/25/03 7:27 PM, Sannyasin Sivakatirswami wrote:

>  We mentioned this before in relation to "Button" and "Menu"   where, 
> sometimes one want a button to look and feel like a button, and yet 
> behave like a pull down menu. This was easily achieved in MC as the 
> property inspector showed all such properties that could be set...  But 
> now, with Rev it's a bit of a headache. If you chose a "menu" from the 
> tools you get a property inspector that is "crippled" with respect to 
> what you can do the object, which is a "button" in the docs, with a 
> property list that is only partially accessible except from the msg box.
> 
> Anyway this case is closed... but I wonder if we shouldn't feature request
>  that the properties inspector reveal all properties to the user...

I have to agree with you. Limiting the property list in the inspector 
gives the impression that each style of button is also a different kind 
of object. I think this may be confusing for newcomers, and it makes it 
harder for all users to change an object style on the fly. There are 
lots of times I start out with one type of button or field and decide 
later I want it to be a different type. In Rev, I have to make the 
change from the message box. I imagine new users may think they have to 
delete the object and start all over again with a new one.

I think a better approach would be to offer all the properties for an 
object in the inspector, and let the tool palette act as simply a 
shortcut method of setting an object to act a certain way.

-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com