-
-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Big GUI Mappings PR (sorry!) #495
Conversation
mappings/net/minecraft/client/gui/screen/realms/RealmsPopupScreen.mapping
Outdated
Show resolved
Hide resolved
mappings/net/minecraft/client/gui/screen/world/SwitchGrid.mapping
Outdated
Show resolved
Hide resolved
mappings/net/minecraft/client/gui/widget/layout/RotatableLayoutWidget.mapping
Show resolved
Hide resolved
mappings/net/minecraft/client/gui/widget/layout/RotatableLayoutWidget.mapping
Show resolved
Hide resolved
mappings/net/minecraft/client/gui/widget/layout/RotatableLayoutWidget.mapping
Show resolved
Hide resolved
mappings/net/minecraft/client/gui/widget/layout/RotatableLayoutWidget.mapping
Show resolved
Hide resolved
mappings/net/minecraft/client/gui/widget/layout/RotatableLayoutWidget.mapping
Show resolved
Hide resolved
mappings/net/minecraft/client/gui/widget/layout/RotatableLayoutWidget.mapping
Show resolved
Hide resolved
mappings/net/minecraft/client/gui/screen/realms/RealmsPopupScreen.mapping
Show resolved
Hide resolved
I want to know what these invalid mappings are... (in the errors) |
mappings/net/minecraft/client/gui/hud/debug/TickRateDebugChartRenderer.mapping
Outdated
Show resolved
Hide resolved
mappings/net/minecraft/client/gui/hud/debug/AbstractDebugChartRenderer.mapping
Outdated
Show resolved
Hide resolved
mappings/net/minecraft/client/gui/hud/debug/AbstractDebugChartRenderer.mapping
Outdated
Show resolved
Hide resolved
mappings/net/minecraft/client/gui/hud/debug/AbstractDebugChartRenderer.mapping
Outdated
Show resolved
Hide resolved
mappings/net/minecraft/client/gui/hud/debug/FrameRateDebugChartRenderer.mapping
Outdated
Show resolved
Hide resolved
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good with the given changes!
I'll try make the changes today, just a lil busy. Also to add a proper summary. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
refactors are great overall, but I'm not sure I like the ResourcePack
to Pack
renames, they could pretty easily be mistaken for data pack things like that. thank you for the huge PR!
for my approval:
- address supersaiyansubtlety's comments
- justify the pack rename
mappings/net/minecraft/client/gui/screen/option/KeyBindOptionsScreen.mapping
Show resolved
Hide resolved
The pack renames was for exactly that reason: they are data pack things as well. At least, some of them are, I'm not certain if there's some of them that aren't. |
As in, data packs use these classes, they don't have their own. |
🚀 Target branch has been updated to 1.20.2-rc1 |
oh perfect, address changes and you're golden! |
I don't have the time to address the changes at the moment because I have a very busy week. I feel like it might be good to merge this before 1.20.2 releases, however, as it would lump any breaking changes together. If someone had the time to PR to my branch with the changes then I could merge that; otherwise I'll do it when I have time. |
@Antikyth would you like me to resolve comments myself? |
🚀 Target branch has been updated to 1.20.2-rc2 |
Still have to manually apply some suggestions in Enigma. |
mappings/net/minecraft/client/gui/hud/debug/AbstractDebugChartRenderer.mapping
Outdated
Show resolved
Hide resolved
mappings/net/minecraft/client/gui/hud/debug/AbstractDebugChartRenderer.mapping
Outdated
Show resolved
Hide resolved
makes getSampleColor param javadocs lowercase with no full stops
Co-authored-by: ix0rai <[email protected]> Co-authored-by: Will <[email protected]>
Co-authored-by: Will <[email protected]>
7d0ddd1
to
3c2f555
Compare
I just rebased it onto the recipe holder changes ^ |
🚀 Target branch has been updated to 1.20.2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one word: damn
great job here!
just one nitpick: i feel like something like "the X coordinate" would be better than "the 'x' coordinate" or "the x coordinate"
ARG 2 layoutSettingsConsumer | ||
CLASS C_ekgfxrpf Orientation | ||
METHOD m_fnqdcoug setRotatedY (Lnet/minecraft/unmapped/C_zuxsitrm$C_isrpishr;II)V | ||
COMMENT Sets the "y" coordinate of the given {@code widget} rotated with this orientation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
COMMENT Sets the "y" coordinate of the given {@code widget} rotated with this orientation. | |
COMMENT Sets the Y coordinate of the given {@code widget} rotated with this orientation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No no no! Coordinates are almost always lowercase in math notation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unless you have a very good reason to make it capital, it should be lowercase.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm confused; i thought this was a standard on our javadocs
And yes, math does have the fancy x
and such but we don't have TeX on our javadoc and uh, just having a lowercase letter doesn't make sense here; i made this request because it felt like it blended with the rest of the text, which is bad; it didn't feel distinct, and considering that stuff like Blender does use capital letters for coordinates? I feel like my gut feelings are justified here
So, if we want to follow a lowercase standard, we ought to use {@code x}
in order to make it distinct and we must make it a formal standard; else? It has to be capital
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd prefer flat x
over {@code x}
, since we usually use code for parameters it may get people to do a double take
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- I think it should be lowercase because that's how it's used in math
- I agree with EnnuiL that "it felt like it blended with the rest of the text, which is bad"
- I don't think we should make it distinct with
{@code}
, because it's not code, that's misleading
So, how about it's made distinct with other text formatting, like some combination of bold/italic/<strong>
/etc?
I'm partial to italics, but idk if that's enough to make it stand out in all cases.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I support italics, I don't think it needs to be super flashy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Italics is the closest way of making the coordinate letters look like math notation without making Java implement TeX on their javadoc engine :p
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It uses quotes because it's not necessarily the actual y coordinate by the way. I think. On mobile, GitHub won't let me scroll the text to the right to see what it says.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I definitely wouldnt capitalize it, whatever you pick. The issue isn't so much that coords are generally lowercase in math - it's that uppercase letters have several other connotations! I see an X somewhere and my brain goes "matrix!"
COMMENT <p> | ||
COMMENT If the orientation is {@link Orientation#HORIZONTAL HORIZONTAL}, this will set the actual y | ||
COMMENT coordinate of the {@code widget}. Otherwise, if it is {@link Orientation#VERTICAL VERTICAL}, | ||
COMMENT it will set its x coordinate. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
COMMENT it will set its x coordinate. | |
COMMENT it will set its X coordinate. |
COMMENT Returns the "y" coordinate of the given {@code widget} rotated with this orientation. | ||
COMMENT <p> | ||
COMMENT If the orientation is {@link Orientation#HORIZONTAL HORIZONTAL}, this will be the actual y | ||
COMMENT coordinate of the {@code widget}. Otherwise, if it is {@link Orientation#VERTICAL VERTICAL}, | ||
COMMENT it will be its x coordinate. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
COMMENT Returns the "y" coordinate of the given {@code widget} rotated with this orientation. | |
COMMENT <p> | |
COMMENT If the orientation is {@link Orientation#HORIZONTAL HORIZONTAL}, this will be the actual y | |
COMMENT coordinate of the {@code widget}. Otherwise, if it is {@link Orientation#VERTICAL VERTICAL}, | |
COMMENT it will be its x coordinate. | |
COMMENT Returns the Y coordinate of the given {@code widget} rotated with this orientation. | |
COMMENT <p> | |
COMMENT If the orientation is {@link Orientation#HORIZONTAL HORIZONTAL}, this will be the actual Y | |
COMMENT coordinate of the {@code widget}. Otherwise, if it is {@link Orientation#VERTICAL VERTICAL}, | |
COMMENT it will be its X coordinate. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again, there is a reason it is in quotes. Perhaps it needs to be made clearer if that wasn't clear, how I don't know.
COMMENT Returns the "x" coordinate of the given {@code widget} rotated with this orientation. | ||
COMMENT <p> | ||
COMMENT If the orientation is {@link Orientation#HORIZONTAL HORIZONTAL}, this will be the actual x | ||
COMMENT coordinate of the {@code widget}. Otherwise, if it is {@link Orientation#VERTICAL VERTICAL}, | ||
COMMENT it will be its y coordinate. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
COMMENT Returns the "x" coordinate of the given {@code widget} rotated with this orientation. | |
COMMENT <p> | |
COMMENT If the orientation is {@link Orientation#HORIZONTAL HORIZONTAL}, this will be the actual x | |
COMMENT coordinate of the {@code widget}. Otherwise, if it is {@link Orientation#VERTICAL VERTICAL}, | |
COMMENT it will be its y coordinate. | |
COMMENT Returns the X coordinate of the given {@code widget} rotated with this orientation. | |
COMMENT <p> | |
COMMENT If the orientation is {@link Orientation#HORIZONTAL HORIZONTAL}, this will be the actual X | |
COMMENT coordinate of the {@code widget}. Otherwise, if it is {@link Orientation#VERTICAL VERTICAL}, | |
COMMENT it will be its Y coordinate. |
COMMENT Sets the "x" coordinate of the given {@code widget} rotated with this orientation. | ||
COMMENT <p> | ||
COMMENT If the orientation is {@link Orientation#HORIZONTAL HORIZONTAL}, this will set the actual x | ||
COMMENT coordinate of the {@code widget}. Otherwise, if it is {@link Orientation#VERTICAL VERTICAL}, | ||
COMMENT it will set its y coordinate. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
COMMENT Sets the "x" coordinate of the given {@code widget} rotated with this orientation. | |
COMMENT <p> | |
COMMENT If the orientation is {@link Orientation#HORIZONTAL HORIZONTAL}, this will set the actual x | |
COMMENT coordinate of the {@code widget}. Otherwise, if it is {@link Orientation#VERTICAL VERTICAL}, | |
COMMENT it will set its y coordinate. | |
COMMENT Sets the X coordinate of the given {@code widget} rotated with this orientation. | |
COMMENT <p> | |
COMMENT If the orientation is {@link Orientation#HORIZONTAL HORIZONTAL}, this will set the actual X | |
COMMENT coordinate of the {@code widget}. Otherwise, if it is {@link Orientation#VERTICAL VERTICAL}, | |
COMMENT it will set its Y coordinate. |
METHOD m_fnqdcoug setRotatedY (Lnet/minecraft/unmapped/C_zuxsitrm$C_isrpishr;II)V | ||
COMMENT Sets the "y" coordinate of the given {@code widget} rotated with this orientation. | ||
COMMENT <p> | ||
COMMENT If the orientation is {@link Orientation#HORIZONTAL HORIZONTAL}, this will set the actual y |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh i missed one
COMMENT If the orientation is {@link Orientation#HORIZONTAL HORIZONTAL}, this will set the actual y | |
COMMENT If the orientation is {@link Orientation#HORIZONTAL HORIZONTAL}, this will set the actual Y |
Personally, I don't think so, it's how I'd always write it myself, but if other people agree with that then it can be changed. |
Summary: probably not coming unfortunately, I'm very busy at the moment
Big PR, adds a lot of mappings and refactors some existing ones.