Object activation mode 'rectangle' won't apply to 'real' children

I frequently use the rectangle activation mode to make mouse over effects work on objects made from pngs with a lot of transparent area. It allows the object to trigger mouse over even in transparent parts of the object.

The problem I'm having is that if I make an object a true child of another object, it seems to always be forced on normal activation, even if the properties shows rectangle activation.

If it is not a true child the problem goes away.
Just wondering if anyone knows of this, a solution, or if its normal.
Thanks
4,861 views 9 replies
Reply #1 Top
I tired some circular png files I had. They all used the rectangular activation area even as true children.
Reply #2 Top
I tired some circular png files I had. They all used the rectangular activation area even as true children.
Reply #3 Top
Hi thomassen, thanks for testing for me. Could you try one more thing? Make the parent Opacity 0 and set it's activation to None or default, and the child to being a true child and activation on rectangular area.

If you still don't see the 'effect' maybe it is something else related to me changing the child 'type'. I'll see if I can create a dxpack and link to it that definitly shows the effect on my comp.

Thanks again thomassen


Posted via WinCustomize Browser/Stardock Central
Reply #4 Top
object showing described problem: http://www.freewebtown.com/skarn/bug.dxpack
mouse over the 'scroll', which is a non-true child of a large, transparent object.
it will highlight as long as the mouse is over the scroll area.

Now edit the scroll to be a true child.

Try hovering over again, wherever the scroll is transparent will no longer detect the mouse over, even thought the activation is still set to rectangle.

Hope this does show it as happening, otherwise there's something dodge with my desktopx install


Posted via WinCustomize Browser/Stardock Central
Reply #5 Top
object showing described problem: http://www.freewebtown.com/skarn/bug.dxpack
mouse over the 'scroll', which is a non-true child of a large, transparent object.
it will highlight as long as the mouse is over the scroll area.

Now edit the scroll to be a true child.

Try hovering over again, wherever the scroll is transparent will no longer detect the mouse over, even thought the activation is still set to rectangle.

Hope this does show it as happening, otherwise there's something dodge with my desktopx install


Posted via WinCustomize Browser/Stardock Central
Reply #6 Top
object showing described problem: http://www.freewebtown.com/skarn/bug.dxpack
mouse over the 'scroll', which is a non-true child of a large, transparent object.
it will highlight as long as the mouse is over the scroll area.

Now edit the scroll to be a true child.

Try hovering over again, wherever the scroll is transparent will no longer detect the mouse over, even thought the activation is still set to rectangle.

Hope this does show it as happening, otherwise there's something dodge with my desktopx install


Posted via WinCustomize Browser/Stardock Central
Reply #7 Top
object showing described problem:

http://www.freewebtown.com/skarn/bug.dxpack

mouse over the 'scroll', which is a non-true child of a large, transparent object.
it will highlight as long as the mouse is over the scroll area.

Now edit the scroll to be a true child.

Try hovering over again, wherever the scroll is transparent will no longer detect the mouse over, even thought the activation is still set to rectangle.

Hope this does show it as happening, otherwise there's something dodge with my desktopx install


Posted via WinCustomize Browser/Stardock Central
Reply #8 Top
errm...sorry about that.

Posted via WinCustomize Browser/Stardock Central
Reply #9 Top
hmm..

Ok, I get the same behaviour as well now. I also tried to use an empty png picutre instead of transparency 0. Same effect.
Other Things I noticed, if I set the paret activation to none the child would not activate.
If I set the parent actication to default or visible only the child only activates at the visible areas.
If I set the parent activation to rectangle the child activates by it's own rectange.

So it seems that true child objects inherit it parent's activation setting. This seem to be a bug. I think it's worth reporting it. Link to this thread.