• strict warning: Non-static method view::load() should not be called statically in /home/www/wowpro/public_html/sites/all/modules/views/views.module on line 879.
  • strict warning: Declaration of views_handler_argument::init() should be compatible with views_handler::init(&$view, $options) in /home/www/wowpro/public_html/sites/all/modules/views/handlers/views_handler_argument.inc on line 745.
  • strict warning: Declaration of views_handler_filter::options_validate() should be compatible with views_handler::options_validate($form, &$form_state) in /home/www/wowpro/public_html/sites/all/modules/views/handlers/views_handler_filter.inc on line 589.
  • strict warning: Declaration of views_handler_filter::options_submit() should be compatible with views_handler::options_submit($form, &$form_state) in /home/www/wowpro/public_html/sites/all/modules/views/handlers/views_handler_filter.inc on line 589.
  • strict warning: Declaration of views_handler_filter_boolean_operator::value_validate() should be compatible with views_handler_filter::value_validate($form, &$form_state) in /home/www/wowpro/public_html/sites/all/modules/views/handlers/views_handler_filter_boolean_operator.inc on line 149.
  • strict warning: Non-static method view::load() should not be called statically in /home/www/wowpro/public_html/sites/all/modules/views/views.module on line 879.
  • strict warning: Non-static method view::load() should not be called statically in /home/www/wowpro/public_html/sites/all/modules/views/views.module on line 879.
  • strict warning: Declaration of flag_handler_relationship_content::ui_name() should be compatible with views_handler::ui_name($short = false) in /home/www/wowpro/public_html/sites/all/modules/flag/includes/flag_handler_relationships.inc on line 87.
  • strict warning: Declaration of flag_handler_relationship_counts::ui_name() should be compatible with views_handler::ui_name($short = false) in /home/www/wowpro/public_html/sites/all/modules/flag/includes/flag_handler_relationships.inc on line 149.
  • strict warning: Non-static method flag_flag::factory_by_row() should not be called statically in /home/www/wowpro/public_html/sites/all/modules/flag/flag.module on line 890.
  • strict warning: Non-static method flag_flag::factory_by_row() should not be called statically in /home/www/wowpro/public_html/sites/all/modules/flag/flag.module on line 890.
  • strict warning: Non-static method flag_flag::factory_by_row() should not be called statically in /home/www/wowpro/public_html/sites/all/modules/flag/flag.module on line 890.
  • strict warning: Non-static method flag_flag::factory_by_row() should not be called statically in /home/www/wowpro/public_html/sites/all/modules/flag/flag.module on line 890.
  • strict warning: Non-static method flag_flag::factory_by_array() should not be called statically in /home/www/wowpro/public_html/sites/all/modules/flag/flag.module on line 961.
  • strict warning: Non-static method flag_flag::factory_by_array() should not be called statically in /home/www/wowpro/public_html/sites/all/modules/flag/flag.module on line 961.
  • strict warning: Non-static method flag_flag::factory_by_array() should not be called statically in /home/www/wowpro/public_html/sites/all/modules/flag/flag.module on line 961.
  • strict warning: Only variables should be passed by reference in /home/www/wowpro/public_html/sites/all/modules/flag/includes/flag.views.inc on line 241.

Wild Waypoints and a way to tame them

Ludovicus's picture

OK, so I started looking at the way waypoints were handled and got REALLY confused!

But I think I have discovered the current behaviour and what I want to change it to.

Right now:

  1. A Single step (that is not a r/R/N) with multiple coordinates gets a waypoint for every map coordinate and no autocompletion or waypoint proximity deletion.
  2. A r/R/N step with CC tag gets all the waypoints and autocompletes when the last one is reached.
  3. A r/R/N step with CS tag gets all the waypoints and autocompletes when the waypoints are hit in sequence
  4. A r/R/N step with no tag gets all the waypoints and does not autocomplete
  5. If there are sticky steps (i.e. more than one step active), the waypoints and mode for the last step take effect for ALL steps

Why case #5?  It turns out there is a global flag controlling both the autocomplete mode and proxymity deletion.  For sticky steps what mode is in effect is never obvious.   So really, I want to make it a property of each step's waypoint.

So my proposed alternative is:

  1. A step with no CC or CS tag and one waypoint gets  the waypoint and gets  no proximity deletion and no autocomplete based on waypoints (think NPC locations for a A step). 
  2. A step with no CC or CS tag and multiple waypoints gets all the
    waypoints and gets  proximity deletion and no autocomplete based on
    waypoints (think mob locations for a C step).  Each time a waypoint is deleted, the closest one is selected.
  3. A step with a CC tag gets all the waypoints and gets proximity deletion, and autocompletes when the last waypoint is hit if it is a r/R/N step.If it is not a r/R/N step, then the last waypoint stays active until the step is otherwise completed. (think possible path if you run there, but shortcut if you fly there, an A step for an NPC on a mountain).  The waypoint arrow points to the last waypoint.
  4. A step with a CS tag gets all the waypoints and gets proximity deletion, and forces you to hit each of the waypoints in sequence to autocomplete. The waypoint arrow points to the current waypoint.If it is not a r/R/N step, then the last waypoint stays active until the step is otherwise completed. (Think an A step for NPC in a twisty cave)
  5. If sticky steps are in effect, the above modes are in effect for the current "prime" step.  No interference.

Comments

Emmaleah's picture

Waypoints.

Waypoints are obviously a source of frustration, I think these ideas could help out.

 I assume #4 in your proposed alternative should say CS?

Ludovicus's picture

Re; Waypoints

Thanks for the correction.