Blocking resize

[Sakari Ruoho]

Well my problem is, that I want to create these so called  
'components', which are groups with objects in it. Let's say one  
component could be a group with a button on top and an image. The  
button sets the filename for the image. Now If I would let the user  
resize the group, the button nor the image would scale with the group,  
which would be not looking good. Of course I could use different tool  
and calculate the new sizes for the objects, but the user will use the  
pointer tool for other single objects, so a different tool for these  
'components' would be very confusing for the user I think.

But really might be, that I need to redesing the UI idea I have come  
up with.

Sakari Ruoho

On Feb 18, 2008, at 3:10 PM, Mark Schonewille wrote:

> Hi Sakari Ruoho,
>
> I believe you have to emulate your own pointer tool. Create tiny  
> buttons and place them at the corners of the object you want to  
> change. Allow the user to drag these buttons and change the size of  
> the object while the buttons are dragged.
>
> Why do you want to do this?
>
> Best regards,
>
> Mark Schonewille
>
> --
>
> Economy-x-Talk Consulting and Software Engineering
> http://economy-x-talk.com
> http://www.salery.biz
>
> Convert colours between different colour spaces with Color  
> Converter. Download at http://economy-x-talk.com/cc.html
>
>
>
> Op 18-feb-2008, om 14:04 heeft Sakari Ruoho het volgende geschreven:
>
>> Hiya Mark,
>>
>> I should learn to state my problem better.. sorry for that.
>>
>> The basic idea is that I want the user to be able to use the  
>> pointer tool where some objects can be resized and some can't. The  
>> objects which cannot be resizen are groups with objects in them. I  
>> call them components.
>>
>> As I understand, while the pointer tool is chosen, the revolution  
>> don't send mouseDown messages, correct?
>>
>> Now the grab command would do this for me, but then I would have to  
>> change the tool to browser and keep the pointer cursor in order to  
>> 'cheat' the user thinking that the tool is not changing. Maybe this  
>> is the only way to achieve this, but this is why I'm asking.  
>> Playing with cursors and tools gets the code much more messy, so I  
>> want to avoid this if possible.
>>
>> Maybe the problem is not a programming problem, but application  
>> design one. Still lots to learn from Revolution I reckon :D
>>
>>
>> Sakari Ruoho
>>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution