Add contextual constants i.e. NOT_FOUND = -1

[OffsetMOSFET]

As a habit, I often create consts as a way to avoid adding comments or look at documentation. I often add a const NOT_FOUND := -1 for a .find() or const ANTIALIASED := true for a .draw_circle() or other similar const to the top of my scripts or functions. It's a bit easier to parse for me, especially while glancing through code quickly.

My current issue is that, without a easy way to write global constants, I will have to add these to every script, which adds it to the script's consts lists. It's a little annoying.

[ssaenger]

You can access constants from any class. For example, if you have a class_name Globals, then you can access a const by Globals.NOT_FOUND

[OffsetMOSFET]

I know about that. I don't prefer it, because it adds a bit of filler text and tedium.

Like take this example:

if NOT_FOUND == idx:

versus

if Globals.NOT_FOUND == idx:

the first pair is very close to natural language. Also it pushes the most important context of the line more to the left, which is another strategy I employ to quickly skim my code.