You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be useful to list hexadecimal numbers beside each error constant here, so that error constants produced by applications can be searched with some Ctrl + F-fu: godotengine/godot#53297
The codes should be listed outside the accordions, so that they can be searched even if sections are not expanded.
The decimal numbers could also be listed for convenience (although they're arguably less useful compared to hexadecimal numbers, which are nicely categorized in many libraries like mbedTLS).
The text was updated successfully, but these errors were encountered:
A nice suggestion, thanks!
I would go only for the hexa and understand the placement needs to be outside the accordions. Looking into the linked issue, I'll check the possibility of having the numbers as alternative IDs usable as URL anchors so that you can link to the particular error directly.
As you probably noticed, this project was a bit less maintained recently, but I expect additions with one of my bachelor's students work (it's all industry supported academic work).
In mbedTLS for instance, each error has its own hexadecimal integer constant: https://github.com/ARMmbed/mbedtls/blob/052deb941f051a07c1d9726e05dac2a8d7557959/include/mbedtls/x509.h#L56-L96
It would be useful to list hexadecimal numbers beside each error constant here, so that error constants produced by applications can be searched with some Ctrl + F-fu: godotengine/godot#53297
The codes should be listed outside the accordions, so that they can be searched even if sections are not expanded.
The decimal numbers could also be listed for convenience (although they're arguably less useful compared to hexadecimal numbers, which are nicely categorized in many libraries like mbedTLS).
The text was updated successfully, but these errors were encountered: