mirror of
https://github.com/OpenMW/openmw.git
synced 2025-11-04 02:26:41 +00:00
df5919f2c5
- It is implementation-dependent if plain `char' signed or not. - C standard defines three *distinct* types: char, signed char, and unsigned char. - Assuming that char is always unsigned or signed can lead to compile-time and run-time errors. You can also use int8_t, but then it would be less obvious for developers to never assume that char is always unsigned (or always signed). Conflicts: components/esm/loadcell.hpp
40 lines
610 B
C++
40 lines
610 B
C++
#ifndef OPENMW_ESM_DIAL_H
|
|
#define OPENMW_ESM_DIAL_H
|
|
|
|
#include <string>
|
|
#include <vector>
|
|
|
|
#include "loadinfo.hpp"
|
|
|
|
namespace ESM
|
|
{
|
|
|
|
class ESMReader;
|
|
class ESMWriter;
|
|
|
|
/*
|
|
* Dialogue topic and journal entries. The actual data is contained in
|
|
* the INFO records following the DIAL.
|
|
*/
|
|
|
|
struct Dialogue
|
|
{
|
|
enum Type
|
|
{
|
|
Topic = 0,
|
|
Voice = 1,
|
|
Greeting = 2,
|
|
Persuasion = 3,
|
|
Journal = 4,
|
|
Deleted = -1
|
|
};
|
|
|
|
std::string mId;
|
|
signed char mType;
|
|
std::vector<DialInfo> mInfo;
|
|
|
|
void load(ESMReader &esm);
|
|
void save(ESMWriter &esm);
|
|
};
|
|
}
|
|
#endif
|