- I want to enable ctrl-click to select within group, but I don't see
how
it can be done. I've delved deep into the arena code and found that if a group is "transparent" then its members can be selected one by one. But
how
can I do that on ctrl-click? In select-context.c, the handler that
checks
what button/key was pressed seems to already get a selected item as an argument from the arena code. Will I have to analyze this preselected
item
on my own, or is there a more elegant way?
This is something I'd like to work on personally, as part of the continuing layers work. I'm still trying to determine what a "clean" solution would be, though.
Actually, analyzing the object under mouseclick and finding out what part of selection was clicked is pretty easy using document.cpp functions, without any help from arena code. I think I could write this feature now, but if you don't want me to mess with this, I'm fine :)
This sounds like a compiler bug. What version of g++ are you using? I've been unable to replicate the problem using g++ 3.3.2.
Mine is 3.3.1. Do you think it's worth the trouble to protect 3.3.1 users from this crash (which is admittedly rare, you'll need to scale a text string to microscopic sizes to get it)?
_________________________________________________________________ Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2f...
On Fri, 2003-12-19 at 04:30, bulia byak wrote:
Actually, analyzing the object under mouseclick and finding out what part of selection was clicked is pretty easy using document.cpp functions, without any help from arena code. I think I could write this feature now, but if you don't want me to mess with this, I'm fine :)
It's just that control+click to select "inside" isn't the whole issue, I think -- once selected, the item's parents in the arena need to become "transparent" themselves for everything to work as it should. I think.
That said, even simple control+click is an improvement -- so really I guess go ahead.
And maybe leaving "transparent" to be explicitly set by whatever UI we use to toggle a group's "layer" mode is best anyway.
Mine is 3.3.1. Do you think it's worth the trouble to protect 3.3.1 users from this crash (which is admittedly rare, you'll need to scale a text string to microscopic sizes to get it)?
Can you upgrade to 3.3.2 and try to replicate the bug, so we can rule out factors other than the compiler?
-mental
participants (2)
-
bulia byak -
MenTaLguY