Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The only important requirement here is to provide a deep copy constructor that stores all necessary information (or if that's not possible, a method to get all the required info). Then use that ctor/method to create a second vector. Something like:</p> <pre><code>class Object { RenderObject * m_Renderable; int m_Health; float3 m_Position; Object(const Object * other) : m_Renderable(nullptr), m_Health(other-&gt;m_Health), m_Position(other-&gt;m_Position) { }; Object * GetStorable() { return new Object(*this); } }; </code></pre> <p>then to store "checkpoints", you simply do:</p> <pre><code>vector&lt;vector&lt;shared_ptr&lt;Object&gt;&gt;&gt; gCheckpoints; vector&lt;shared_ptr&lt;Object&gt;&gt; gLevelObjects; vector&lt;shared_ptr&lt;Object&gt;&gt; checkpoint; std::for_each( gLevelObjects.begin(), gLevelObjects.end(), [&amp;](shared_ptr&lt;Object&gt; obj) { checkpoint.push_back(obj-&gt;GetStorable()); }); gCheckpoints.push_back(checkpoint); // creates a new checkpoint </code></pre> <p>You will need to recreate the render information for the objects when the checkpoint is restored; this is a requirement for most save systems in most graphics contexts, however.</p> <p>Depending on how your <code>Object</code> class is set up, you can also inherit from another class that consists <em>only</em> of the stored data, and simply store that and create the renderables from it when necessary (<code>class RenderObject : StoredObject { ... };</code>).</p> <p>You can alternatively serialize the objects in some fashion (binary save, xml, json) and store that to a file (autosave/quicksave/checkpoint) or in-memory, and then use your regular loading mechanism to load that specific file.</p> <p>The best method depends on what your plans are and how your system is set up, but this concept should provide the basics or give you a starting point.</p>
    singulars
    1. This table or related slice is empty.
    1. POC++: make full copy of vector of pointers
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USssube
    1. USssube
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COLambda isn't supported before C++11. There may be a `boost.lambda` solution, though.
      singulars
      1. PO
      1. USmoshbear
    2. CO@moshbear Lambdas are much easier to write into an answer without cluttering it up. ;) If not using 11, then it can be replaced with a functor.
      singulars
      1. PO
      1. USssube
    3. COSeconded about easier to write. `Boost.bind` looks and feels like a hack.
      singulars
      1. PO
      1. USmoshbear
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload