this post was submitted on 23 Nov 2023
0 points (NaN% liked)

Godot

5876 readers
1 users here now

Welcome to the programming.dev Godot community!

This is a place where you can discuss about anything relating to the Godot game engine. Feel free to ask questions, post tutorials, show off your godot game, etc.

Make sure to follow the Godot CoC while chatting

We have a matrix room that can be used for chatting with other members of the community here

Links

Other Communities

Rules

We have a four strike system in this community where you get warned the first time you break a rule, then given a week ban, then given a year ban, then a permanent ban. Certain actions may bypass this and go straight to permanent ban if severe enough and done with malicious intent

Wormhole

[email protected]

Credits

founded 1 year ago
MODERATORS
 

I'm just starting out with Godot and I've run into some strange or unwanted behaviors. Maybe some of you can help me fix them. I'm currently running Godot on arch linux with x11/i3 as my desktop environment.

1.) Godot got some really aggressive focus. The editor grabs the focus mid typing in other applications and suddenly I'm tying there. With i3 being a tiling manager, Godot is sometimes passively resized when I resize another window - of course it also immediately gets itself focused and messed the resizing up.

2.) The focus within Godot is even stranger. I can ctrl c + ctrl v nodes just fine on a freshly opened project. But once I've a clicked a single property in the import or inspector docker, ctrl c + ctrl v will work exclusively there. Even if the import docker is hidden underneath the scene docker where I'm clicking the nodes I want to copy/paste.

3.) The last one is about using an external editor. Whenever Godot encounters a bug, it will automatically open the script in question. Which is annoying because I use vim for everything and will throw warnings at me, that the file has been changed. I've looked through all editor settings and tried setting vim as my external editor but the behavior persists.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 0 points 11 months ago

Though be careful with this as the duplicated nodes will use shared instances of resources instead of instantiating their own. This can lead to unexpected behaviour if you don't make resources unique after duplicating.