FourthWorld wrote: ↑Fri Mar 09, 2018 3:49 pm
Perhaps I had misunderstood, but I had thought preventing the checkbox that governs tool mode from being selectable was the point.
Well, it is equally possible I am over-thinking the problem, or misunderstanding it myself, don't feel all alone, come on in and join the confusion that is my mind
(**Warning, if you can't get back out, I can't help you).
My conception of the original problem in this thread was -
- Set pointer mode so that the user can move and size a button (I possibly mistakenly assume this means you desire to have the selection ring showing the points you can drag to modify the object, as well as showing which object(s) are currently selected)
- When a user then clicks on a button, it would display its location, id, etc., into individual fields...
Now, while setting the cantSelect of the checkbox *does* leave it un-editable, i.e. in 'browse mode', in the context of the previous code, it still shows the selection ring
and reports its position in the field. My thoughts were that this may lead to user confusion, since cantSelect only stops some of the mouseDown messages, but not all of them. The check box shows it is selected, but isn't resizeable, etc.
Too offset this, you could add more code, but at that point your writing code, what I understood your point of using cantSelect to avoid having to do, and going nearer to -hh's solution. Even there, though, the report is made to the field, and the selection ring is temporarily around the check box.
I am sure you know I don't use dp releases
and I don't recommend them to someone trying to figure out how to do something either. Why add possible problems not of your making to something if you don't have to? I realize our friend here is using it, though, and it is a valid point that I did no testing using it as a release.
However, in 8.1.6, the behavior is still the same
- Selection_004.png (14.8 KiB) Viewed 5023 times
Like I said, though, I may be over thinking it or completely off target, but if I set 'cantSelect' on something, then I expect it to appear as if it isn't in pointer mode, not as if it is selected (the selection ring), or report its position in the field.
I'll see your drawing program with a readily available counter, can you imaging how confused we might be if you cicked on a button in the tools palette of the IDE, and it looked as if you had selected it on your main stack? It is desireable to have the button hilite for sure, but not to look like you have it ready for modification.
Despite that, though, I completely agree with the way you guys all went with it back in the day, I use it frequently in other things
** Sort of an interesting aside, in IDEs v6.5 to 7.x i had no problem running this test and getting back to the IDE by hitting 'Restore Development', but in 8.1.6 I actually had to force quit it