ENIGMA Development Environment

xprevious / yprevious should be changed whenever an instance's x / y variable is changed.


Tracker Reference:
http://enigma-dev.org/tracker/ticket.php?id=88

I have been trying to debug this myself. I have found that the result of this bug is actually due to two issues:

1) background_showcolor is not used

In roomsystem.c background_color is defined using:

background_showcolor = (backcolor!=-1);Instead of from the background_showcolor boolean from LGM.

Note that when this is fixed GSscreen.cpp also needs updating. It uses (in 2 places):

      if (background_showcolor)
      {
         int clearcolor=((int)background_color)&0xFFFFFF;
         glClearColor(__GETR(clearcolor)/255.0,__GETG(clearcolor)/255.0,__GETB(clearcolor)/255.0, 1);
         glClear(GL_COLOR_BUFFER_BIT);
      }An else statement should be added to this clearing the screen in black (as GM does).


2) The instance's parent draw code is not being executed in my particular file.

EDIT: No longer a problem.

Oh I see what it's doing now, I misunderstood it's purpose.

OK so is this set to go then? I want to make sure we can actually sort something out because I believe it is necessary to help drive progress.

So the first thing needed is to populate the function list on wiki. Are you working on this TGMG?

Oh using a default parameter is fine then?

inline void action_move_to(double x, double y, bool argument_relative = false)
{
  enigma::object_planar* const inst = ((enigma::object_planar*)enigma::instance_event_iterator->inst);
  if (argument_relative)
  {
    inst->x += x;
    inst->y += y;
  }
  else
  {
    inst->x = x;
    inst->y = y;
  }
}You won't need argument_relative as a global variable then. Why wasn't this just used to start with?

So it needs to keep track of where to actually close the '{' for action_if's (that have the relatvie checkbox) which is much more complex than passing the value in by the argument.

Can't you put the closing brace in then move back up into the statements?

So I see, you would work relative like so EDL:

argument_relative = true;
action_move_to(4, 4);Should use the action relative. This I presume would actually work in gml however it doesn't allow you to set the argument_relative variable.

Calling plain as:
action_move_to(4, 4);Should always use the action not relative. This means that the argument_relative variable should always be set false after an action is called.