Tag: c++

Give job entry points a way to specify a custom position status. Do some refactoring to make this possible.

Resolves #33

Hello! The actual functional change would have been pretty straight-forward, had it not been for the fact that since the very early development of OLives there were some enums (later enum classes) defined right in the main Object class.
Over time, this led to some interesting #include structures and other fun issues, today I finally decided to move each of them into its own respective file, so the biggest part of this commit is just that – and adapting all the usages.
So far, there don’t seem to be any regression and on top of that we have our neat little feature, as mentioned in the commit message. 🙂

Make enter/leave animation configuration entry point specific

Resolves #31

This moves the way the enter/leave animations are configured from a “global” job setting to a setting of the entry points, as I realised as soon as I started thinking about how to implement the “sleeping” mechanics, as the bed requires specific animations for the different entry points.
That is something the current use case, the shower, does not require, as most showers only have one door to the best of my knowledge. Not so long story even shorter, that’s changed now.
Obviously this required some overall changes in the code, it also moved the handling of default animations fully to the C++ side of things, which is probably for the best for “default” behaviour – obviously the animation can still be freely defined from Python 🙂

Add mising animations to the human model

Fixes #29

Hello! Finally this commit finishes the object-in-object job logic, the short video shows off the example implementation:

With this finished the next step will be.. I don’t know, let’s see 🙂

Add the additional logic to leave an object again after finishing a job or the job has been cancelled

Relates to #29

Hi! This should more or less complete the actual code work required to get object-in-object jobs going and is actually also implementing the “take a shower” case as a first example. The missing thing here are the actual animations, I’ll put together a quick video once they’re done. 🙂

Extend the job type configuration (and JobType class) with an is_internal setting (no function yet)

Relates to #29

Hi! This mostly added some boilerplate code (and comments describing what it’s for) to the mentioned parts of the code as well as fixing some warnings. Next up will be exposing that new information to the Python scripts and starting to implement the “shower” job from a code perspective – as theoretically all the building blocks (enter/leave mechanics) should be in place already.
Then of course there’ll also be more animations to be done to finish it off, something I don’t look forward to that much after having done the enter/leave animation marathon not too long ago, but I’m sure it will be worth it. 🙂

Workaround for out-of-sync widget states resulting in segfaults in the UiPipeline

Resolves #2

Since this is a race condition testing was the opposite of fun, so after about three hours of debugging of potential causes I decided to give up and simply throw (and catch) and exception if this happens, ta-da!

Add a usable shower model + a bath tile texture

Relates to #29

The world of OLives just got a bit bigger again. The shower object, while technically existing before with a dummy model, will be used soon hopefully as the first object that requires another to enter it to perform a job (i.e. take a shower).
If that mechanic works properly, that opens up a world of new possibilities – the next work will be finishing this up though and potentially looking into some stability issues when updating the UI, a known issue. :\ Anyway, check out this amazingly detailed new model and texture. Lifelike.