Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2018.4.X, 2019.4.X, 2020.2.X, 2021.1.X
Votes
0
Found in
5.5.1f1
Issue ID
885341
Regression
No
When using custom PropertyDrawers the tooltip field of the serializedProperty is always empty
Reproduction steps:
1. Open the attached project "TooltipBug.zip";
2. Open the ExampleScene;
3. Select the ExampleObject;
4. From the folder Sources, drag and drop one of the scripts - WithAttribute or WithoutAttribute.
Expected results: the function should show tooltip field;
Actual results: the tooltip field is empty;
Reproduced on: 5.3.0a4, 5.4.4p3, 5.5.1f1, 5.6.0b10
-
Peter77
Jan 12, 2021 11:00
-
Peter77
Jan 12, 2021 10:55
-
hyagogow
Dec 26, 2019 16:16
Bug still present for 2019.1
-
phobos2077
Sep 07, 2018 13:06
Ok, I think I know why this is closed. There IS a way to obtain the tooltip inside property drawer:
label = EditorGUI.BeginProperty(position, label, property);
-
Rob-A
Jul 11, 2018 17:11
Still in 2018.2. Why is it closed?
-
Novack
Jul 05, 2018 16:41
Exactly, no comments or explnations? This is a bug still present to this day on latest Unity version.
-
phobos2077
Jul 01, 2018 07:28
Any explanation why this issue won't be fixed?
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a2
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0b5
Resolution Note (fix version 2020.2):
Fixed in 2020.2.5f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.24f1
Resolution Note (fix version 2018.4):
Fixed in 2018.4.35f1