ClickDetectors not working for un-collidable Parts?

Bug Reports Engine Bugs
1

Lets saying you’re making a simple door with ClickDetectors. Once you’ve finished it, you realize you can’t click the door anymore once its property: “CanCollide” is set to false and transparency is greater than 0.95. This is annoying, I’m trying to make said door with ClickDetectors and this is getting in the way. If this is intentional, can it be reverted? (or maybe a Bool property for ClickDetectors)? I haven’t tried this in real game mode, but I can say it happens in Play Solo and server mode.

EDIT: The part’s transparency must be greater than 0.95 in order for the bug to take place.

2

This definitely isn’t the case. Running a script with this code in a Part with a ClickDetector runs as intended:

[code]local part = script.Parent
function onClick()
part.CanCollide = not part.CanCollide – each time the part is clicked, the CanCollide property toggles
end

part.ClickDetector.MouseClick:connect( onClick)[/code]

Can we see the code you’re running?

3

[quote] This definitely isn’t the case. Running a script with this code in a Part with a ClickDetector runs as intended:

[code]local part = script.Parent
function onClick()
part.CanCollide = not part.CanCollide – each time the part is clicked, the CanCollide property toggles
end

part.ClickDetector.MouseClick:connect( onClick)[/code]

Can we see the code you’re running? [/quote]

Insert a part and put a ClickDetector in it, notice it is clickable. Make the part un-collidable. Notice now that it isn’t clickable. If it is still clickable, make the part’s transparency to 1, then try. But this happens to me.

4

[quote]
Insert a part and put a ClickDetector in it, notice it is clickable. Make the part un-collidable. Notice now that it isn’t clickable. If it is still clickable, make the part’s transparency to 1, then try. But this happens to me. [/quote]
You’re right. The part has to be both not CanCollide and its transparency has to be greater than 0.95 for the clickdetector to stop working.

local part = script.Parent
function onClick()
	part.CanCollide = not part.CanCollide
	part.Transparency = part.CanCollide and 0 or 0.9501 -- breaks
end
part.ClickDetector.MouseClick:connect( onClick)

It’s most likely intended behavior. For a temporary fix, you can set the transparency to 0.95 instead.

5

[quote]
Insert a part and put a ClickDetector in it, notice it is clickable. Make the part un-collidable. Notice now that it isn’t clickable. If it is still clickable, make the part’s transparency to 1, then try. But this happens to me. [/quote]
You’re right. The part has to be both not CanCollide and its transparency has to be greater than 0.95 for the clickdetector to stop working.

local part = script.Parent
function onClick()
	part.CanCollide = not part.CanCollide
	part.Transparency = part.CanCollide and 0 or 0.9501 -- breaks
end
part.ClickDetector.MouseClick:connect( onClick)

For a temporary fix, you can set the transparency to 0.95 instead[/quote]

Oh, okay. Well that changes things. This most likely is a bug then. But, I’ve found a temporary fix involving two parts. Otherwise, I would use what you’ve suggested.