Posts

• ChrisHamons USForum Administrator, Xamarin Team Xamurai

  January 2017

  This is not a Xamarin.Mac bug.

  In your example, you have this:

      void Timer_Tick(object obj, EventArgs args)
      {
          Console.WriteLine("Got a tick = " + _tick++);
  
          if (_tick >= 5)
          {
              _timer.Stop();
              Discovering = false;
  
              BeginInvokeOnMainThread(() =>
              {
                  Console.WriteLine("About to stop animation.");
  

  Note that you are setting Discovering on the timer thread. This means you are setting WillChangeValue / DidChangeValue on the timer thread.

  This is bad. You should not do anything UI related on the non-UI thread unless you clear it by the documentation (https://developer.apple.com/library/content/documentation/Cocoa/Conceptual/Multithreading/ThreadSafetySummary/ThreadSafetySummary.html).

  Moving that into the BeginInvokeOnMainThread call made things work for me. I'm surprised that poking UI bits on the non-ui thread didn't crash/mess things up more.

  1
• AllanChin.6924 USUniversity ✭✭✭

  January 2017 edited January 2017

  That IS interesting that it didn't crash. But what's even more interesting is that the progress controls DID eventually hide AND the NSTextField hid immediately.

  Thanks Chris. I'll try not to make that mistake again:).

  0
• ChrisHamons USForum Administrator, Xamarin Team Xamurai

  January 2017

  Likely there is an update every minutes on Cocoa's end that happened to notice the variable was changed and your will/did were flat out ignored.

  0
• AllanChin.6924 USUniversity ✭✭✭

  January 2017

  But no problem at all with the NSTextField.

  0
• DaveHunt USMember ✭✭✭✭✭

  January 2017

  It doesn't really matter whether it worked for some controls and not others. What matters is the correct way to do it is as @ChrisHamons described. No need for speculation.

  1
• AllanChin.6924 USUniversity ✭✭✭

  January 2017

  The "correct" way is always the "best" way.

  1