Anaël
d8d65bcd49
Moved the whole logic to a new file (TooltipManager.cpp), and rewrote most of the logic to profit from object oriented programming. The side-effect is that the changes are scattered across entities, tiles and items because moving everything to OOP requires to add the tooltip to every .cpp file for every tile/item/entities (or their class, on plants for example which all use the tooltip IDS_TOOLTIPS_PLANT)
The issue with the default tooltips loop written by 4J is that:
Its running in the main Minecraft::tick loop and is more than a thousand lines long, polluting the function.
Not using C++'s full potential with object oriented programming, 4J decided to use a big switch case (probably because it could run better on hardware without branch prediction like the WiiU or Xbox 360 ?)
And seems to be better off in its own file than in the main Minecraft.cpp file
23 lines
651 B
C++
23 lines
651 B
C++
#pragma once
|
|
|
|
#include "Item.h"
|
|
|
|
class ItemInstance;
|
|
class Player;
|
|
class Level;
|
|
|
|
class FireChargeItem : public Item
|
|
{
|
|
private:
|
|
Icon *m_dragonFireballIcon;
|
|
public:
|
|
FireChargeItem(int id);
|
|
|
|
virtual bool useOn(shared_ptr<ItemInstance> itemInstance, shared_ptr<Player> player, Level *level, int x, int y, int z, int face, float clickX, float clickY, float clickZ, bool bTestUseOnOnly);
|
|
|
|
virtual Icon *getIcon(int itemAuxValue);
|
|
virtual void registerIcons(IconRegister *iconRegister);
|
|
|
|
virtual int getUseTooltipId(std::shared_ptr<ItemInstance> itemInstance, std::shared_ptr<Player> player, Level* level, int x, int y, int z, bool bUseItem) const;
|
|
};
|