"Unselectable" makes edit mode invalid

[sritcp]

1. Create a new stack; Draw a filled rectangle (or any graphic).

2. Make the graphic unselectable by clicking on the icon on the project browser

3. With the cursor in the Edit mode, click on the graphic; it sends a "mouseUp" message to the card underneath, as detected by the card script

Code: Select all

on mouseUp
   answer "The Card was sent a mouseUp message"
end mouseUp

This doesn't happen if you lock size and position in the inspector (rather than the project browser).

LC 6.7 on a Mac.

Regards,
Sri

[FourthWorld]

Correct: choosing the option to make a control unselectable will make it unselectable, and that behavior is different from the option to prevent interactive resizing, which will only prevent interactive resizing.

If you want an object to remain selectable don't turn on the cantSelect property for it.

If you want an object to prevent having its size or position altered interactively, set the lockLoc checkbox in the Inspector.

[dunbarx]

Hi.

The message is sent in all cases for me, as it should. Making an object unselectable does not change its ability to receive mouse events. Disabling will do that, of course.

Craig Newman

EDIT:

I just read Richard's post. Were you interested in resizing? I did not get that from your post. It looked to me like you were talking about messages.

[sritcp]

My point was,
this happens in the Edit mode (i.e., the mouseUp message is sent to the card).
This left me a little confused because I thought no messages were sent in the Edit mode.

Regards,
Sri

[dunbarx]

Sri.

Ah. I see what you mean now. Making an object unselectable enables messages with the edit tool. Feature or bug?

Craig

[FourthWorld]

I would suggest the engine's fine, and perhaps this is an unfortunate design decision in the IDE.

The cantSelect property is described in the Dictionary as maintaining browser tool behavior for a control even when the pointer tool is active. This is very valuable for a wide range of applications that sometimes use the pointer tool, and the behavior seems to work as described.

The question here is: What is the value of having that in the Project Browser?

Personally, I see much value in having lockLoc there, but none at all in having cantSelect there.

If anyone here feels strongly enough about it to file an enhancement request to replace the current cantSelect option with something more useful like lockLoc, please note the report number here so interested folks can add themselves to the CC list to follow the request's progress.

[sritcp]

..... I see much value in having lockLoc there, but none at all in having cantSelect there......

+1

Regards,
Sri

[FourthWorld]

Enhancement request submitted:
http://quality.livecode.com/show_bug.cgi?id=16416