This is a feature request. As discussed earlier, it might be nice to improve the day and night cycle by adding lights to the map. For this to happen, at least the following things need to happen:

• Extend the json map to include Light objects.
• Design some implementation to be able to parse these Lights out of the map.
• Fix the day-night cycle (#27).
• Actually draw the lights.

Problem

The filepaths on MacOs, Windows and Linux Distro's differ from each other. It would be handy if there is an absolute so we can use things like assets with (for example) 1 line of code, instead of checking which OS is running on the device.

To-Do to solve

• check how absolute paths work in Java
• refactor code to work with absolute paths

The CalendarTable2D doesn't display performances well: durations are trimmed to hours, resulting in wrong sizes or even invisible items (if the duration is any less then one hour). CalendarTable handles it better (half-hours), but it could be improved.

lets say i load prev on 13;13 it will load 13:00 but when i click on in again it says it hasn't load

When the simulator is reset, the day-night cycle doesn't (stays light). It seems that the current implementation still uses some constant increment per frame. Instead it should use the current simulated time to calculate the current brightness. @Zwen1111, since this is your invention, could you please refactor it (again)?

When an performance almost begins almost all visitors go to the toilet. Visitors should go to the toilet when watching the performance when they need to pee or drink not before

when you chose a location, de visitors go to an other destination. This needs to be fixed

The festivalplanner doesn't save stages and artists that aren't used in a performance.

smartscaling should happen if you click away from a visitor
aka change:
if (visitor != null && follow == null) {
to
if (visitor == null && follow != null) {

212:SimulatorPanel

@Maartenwn, you forgot to add the background to the resources.

Currently, the user can 'add' stages to the calendar. However, as noted in #3, these are not stored in memory when a Stage has no Performances (as the saving is designed around Performances). Secondly, there is the question if a user should be able to even define new Stages (in which case we should store them better and include a position), ór we let the loaded map decide which stages exist. Since the latter is far more easier to implement and it is highly unlikely that the setup of stages need to change more regularly than the map, it is that one that I'll start to implement.

Feature request. As talked about earlier, it would be nice if you could click visitors and then the map would zoom in and follow the visitor until you click on a different visitor (then follow that other one) or somewhere other on the map (restore zoom to global using smartscale).

• Create a Camera class to wrap the current logic. Add methods such as followVisitor(Visitor v).
• Implement logic to catch mouseclicks and convert them to Visitors (hit) or null (no hit, zoom out).

To me this seems a good job for @sander123133, @Maartenwn and @craftio.