playMaker

Author Topic: ArgumentException: Getting control 1's position SOLVED  (Read 7241 times)

24pfilms

  • Playmaker Newbie
  • *
  • Posts: 16
    • View Profile
ArgumentException: Getting control 1's position SOLVED
« on: September 17, 2013, 11:07:15 AM »
Getting this error on very simple FSM.

ArgumentException: Getting control 1's position in a group with only 1 controls when doing mouseDown Abort
« Last Edit: September 17, 2013, 11:32:36 AM by 24pfilms »

24pfilms

  • Playmaker Newbie
  • *
  • Posts: 16
    • View Profile
Re: ArgumentException: Getting control 1's position
« Reply #1 on: September 17, 2013, 11:29:36 AM »
Application reboot solved it.

Alex Chouls

  • Administrator
  • Hero Member
  • *****
  • Posts: 3630
  • Official Playmaker Support
    • View Profile
    • LinkedIn
Re: ArgumentException: Getting control 1's position
« Reply #2 on: September 17, 2013, 11:32:46 AM »
I think there may be a couple of places where this happens in the editor GUI, but it should be harmless. I'd still like to track down where it happens and fix it...

24pfilms

  • Playmaker Newbie
  • *
  • Posts: 16
    • View Profile
Re: ArgumentException: Getting control 1's position SOLVED
« Reply #3 on: September 17, 2013, 11:50:30 AM »
I was doing a very simple function with change "Set Material color" on mouse drag or mouse down

Alex Chouls

  • Administrator
  • Hero Member
  • *****
  • Posts: 3630
  • Official Playmaker Support
    • View Profile
    • LinkedIn
Re: ArgumentException: Getting control 1's position SOLVED
« Reply #4 on: September 17, 2013, 12:07:52 PM »
Thanks, I'll try to repro. I think it happens when the editor GUI layout changes while the GUI is being drawn. It should fix itself the next time the GUI is drawn, but it's still annoying...