Kit Bishop

Results 82 comments of Kit Bishop

Rebased. Applied suggestions. - Found a fix to the duplication error I was having, it looks like it was https://github.com/godotengine/godot/issues/92880, but I found a way around it. The Dragger Nodes...

Fixed the stretching algorithm, it should now match BoxContainer in the case that the not-first-stretching child has a minimum size greater than its desired size. > I spotted one minor...

Rebased and removed unused includes. > Hiding a child makes the other children uses a wrong offset index, so hidden sortable children should be respected when getting the dragger's offset...

>Let's say we use offsets as a ratio which seems the best solution for this, it won't break compatibility since we can control the old behaviour in the deprecated method...

Draggers are now hidden when there is 0 or 1 child. They aren't removed since the first one is added in the constructor, and it could cause issues with duplicate.

- Rebased https://github.com/godotengine/godot/pull/90439 on this so it can be tested on the editor ui. There are some issues when docks are moved (when a child visibility changes), docks can jump...

- Rebased to fix merge conflicts after https://github.com/godotengine/godot/pull/72680 Still working on the visibility issue, - Due to the complexity and chance of regressions, I'd like to add some tests first...

To fix the compilation error, you need to add compatibility method bindings in a new editor_interface.compat.inc file. I recommend looking at how it was done for editor_plugin in https://github.com/godotengine/godot/pull/88081/files#diff-005a1ef5a7f4fa8db6b115528dbd935d1fc2836bf579c3ceb72f77ad848a4161. The...

How about something like: If [code]false[/code], using word selections or operations such as double-clicking or holding [kbd]Ctrl[/kbd] ([kbd]Cmd[/kbd] on macOS) while pressing [kbd]left[/kbd], [kbd]right[/kbd], [kbd]backspace[/kbd], or [kbd]delete[/kbd], will ...

Reworded to show true value first, and hopefully its more clear. Changed example in custom_word_separators, since `#` and `!` are always treated as separators so there is no point to...