Yamajac

There is no official notation for Java. There never has been, and there never will be. To even begin to think there could be, is preposterous. And to prove my point, I will use the unofficial website you supplied me with. "To illustrate the point it's worth mentioning that most software companies will have a document that outlines the naming conventions they want their programmers to follow." This right here proves well enough that there are other naming conventions that will be used in different places by different groups. If there were to be only one single proper naming convention, documents would be unnecessary as using the official naming conventions would be part of being a good programmer - which is a requirement for having a job as a programmer. But there isn't a single proper naming convention. It doesn't exist. It depends entirely on the programmer or the group of programmers to decide what notation is going to be best for their program.

And that's wrong. camelCase is when the first letter is lowercase, and all the rest are upper. So his "ClassNamesShouldBeCamelCased" should've been "classNamesShouldBeCamelCase". THAT is proper camelCase. What he displayed is a variation of camelCase. Which just further proves my point. There is no single one proper notation. It's dependant entirely on what the people using it agree on and can read properly. Personally, camelCase isn't my preference. Hungarian Notation is by far my favourite notation, and it's the one I use if I'm going to be doing any serious programming. If I'm just throwing something together for myself, I use whatever I happen to use. Furthermore, the only class name that didn't use his variation of camelCase was my main class, which means that he was nitpicking at a mere 1/6th of my class names for a reason that doesn't exist.

1. IDK, didn't think of using a switch, I suppose. I'm gonna go change that. 2. "ClassNamesShouldBeCamelCased" isn't camel cased, and no, they shouldn't be. They should be easily readable by everybody who's using them. 3. Ahh.. I new it was going to be some super simple thing I missed. Of course it's gonna close immediately when I'm opening a container that's telling it to close immediately. 4.Vanilla crafting benches don't require tile entities. Consistent inventories do require tile entities.

GuiCraftingBench.java ContainerCraftingBench.java CraftingBench.java GuiHandler.java TileEntityCraftingBench.java minetweaks.java The spoilers aren't revealing anything in the preview, so it may also do so when I post this. Can't figure out what's wrong with 'em though. As for my problem, I can open up my GUI just fine, but it just flashes open and then closes immediately. I'm not quite sure what's wrong here, and googling it was giving me nothing.