VVVVVV/desktop_version/src/BlockV.h

#ifndef BLOCKV_H
#define BLOCKV_H

#include <SDL.h>
#include <stdint.h>
#include <string>

class blockclass
{
public:
    blockclass(void);
    void clear(void);

    void rectset(const int xi, const int yi, const int wi, const int hi);

    void setblockcolour(const char* col);
public:
    //Fundamentals
    SDL_Rect rect;
    int type;
    int trigger;
    int xp, yp, wp, hp;
    std::string script, prompt;
    int r, g, b;
    int activity_y;
    uint32_t print_flags;
};

#endif /* BLOCKV_H */
Hello WWWWWWorld! 2020-01-01 21:29:24 +01:00			`#ifndef BLOCKV_H`
			`#define BLOCKV_H`

Consistently use angle brackets for SDL.h includes That's how it should be done, because the SDL headers aren't going to be installed in this repository. The game was a bit inconsistent before but now it isn't anymore. 2020-07-19 06:21:27 +02:00			`#include <SDL.h>`
Print activity zone text in correct font, remove Graphics::drawtextbox Activity zones need to be in the interface font if the message is from the system (like Press ENTER to activate terminal, which may be in a different language) and in the level font if it's a customized message (setactivitytext). Graphics::drawtextbox was counting the textbox width and height in 8x8 characters, even including the borders as characters, so it'd need to be told what the font for the textbox is, and then probably only the height needs to be adapted to the font and not the width because that's adapted to the screen width... So just call Graphics::drawpixeltextbox directly instead. It was already weird enough how actual cutscene textboxes called Graphics::drawtextbox with x/8, y/8 before the previous commit, (when you already have the pixel width and height!) only to have that be a wrapper for drawpixeltextbox by doing x8, y8. 2023-01-13 20:32:05 +01:00			`#include <stdint.h>`
Hello WWWWWWorld! 2020-01-01 21:29:24 +01:00			`#include <string>`

			`class blockclass`
			`{`
			`public:`
Explicitly declare void for all void parameter functions (#628) Apparently in C, if you have `void test();`, it's completely okay to do `test(2);`. The function will take in the argument, but just discard it and throw it away. It's like a trash can, and a rude one at that. If you declare it like `void test(void);`, this is prevented. This is not a problem in C++ - doing `void test();` and `test(2);` is guaranteed to result in a compile error (this also means that right now, at least in all `.cpp` files, nobody is ever calling a void parameter function with arguments and having their arguments be thrown away). However, we may not be using C++ in the future, so I just want to lay down the precedent that if a function takes in no arguments, you must explicitly declare it as such. I would've added `-Wstrict-prototypes`, but it produces an annoying warning message saying it doesn't work in C++ mode if you're compiling in C++ mode. So it can be added later. 2021-02-25 23:23:59 +01:00			`blockclass(void);`
			`void clear(void);`
Hello WWWWWWorld! 2020-01-01 21:29:24 +01:00
			`void rectset(const int xi, const int yi, const int wi, const int hi);`
Move entityclass::setblockcolour() to blockclass::setblockcolour() This moves the function setblockcolour(), so I can directly call it on a particular block without having to have it be inside obj.blocks. 2020-04-04 00:26:19 +02:00
Replace `setblockcolour()` argument with `const char*` There's no reason it needs to be an std::string here. Although, realistically, we should be using an enum instead of string-typing, but, eh, that can be fixed later. 2021-09-12 08:15:34 +02:00			`void setblockcolour(const char* col);`
Hello WWWWWWorld! 2020-01-01 21:29:24 +01:00			`public:`
			`//Fundamentals`
			`SDL_Rect rect;`
			`int type;`
			`int trigger;`
			`int xp, yp, wp, hp;`
			`std::string script, prompt;`
			`int r, g, b;`
Remove x-position from `setactivityposition` After discussing with Ally and Dav, we came to the agreement that this is basically useless since the prompt will always be centered and take up most of the horizontal space of the screen. And the x-position was only added as an offset because at some point, there was a missing space from the side of the "- Press ENTER to Teleport -" prompt, and the offset was there so people could mimic the prompt accordingly. But that was fixed at some point, so it's useless now. 2023-02-18 05:38:05 +01:00			`int activity_y;`
Print activity zone text in correct font, remove Graphics::drawtextbox Activity zones need to be in the interface font if the message is from the system (like Press ENTER to activate terminal, which may be in a different language) and in the level font if it's a customized message (setactivitytext). Graphics::drawtextbox was counting the textbox width and height in 8x8 characters, even including the borders as characters, so it'd need to be told what the font for the textbox is, and then probably only the height needs to be adapted to the font and not the width because that's adapted to the screen width... So just call Graphics::drawpixeltextbox directly instead. It was already weird enough how actual cutscene textboxes called Graphics::drawtextbox with x/8, y/8 before the previous commit, (when you already have the pixel width and height!) only to have that be a wrapper for drawpixeltextbox by doing x8, y8. 2023-01-13 20:32:05 +01:00			`uint32_t print_flags;`
Hello WWWWWWorld! 2020-01-01 21:29:24 +01:00			`};`

			`#endif /* BLOCKV_H */`