HighPrecisionClock and Server param window

mhisted's Avatar

mhisted

16 Jul, 2015 04:19 PM

Hi Chris,

The new nightly has an option to use a "high precision clock (recommended)".

In the code on github it looks like this switches between MachClock and HighPrecisionClock. It looks like MachClock has been the default for a while. I couldn't find any code corresponding to the HighPrecisionClock, and I didn't see any documentation on it. Should we turn it on?

Also, with the new Server preferences window, does the Server now ever read setup_variables.xml? Does it read it when MWorks is upgraded?

You also seem to have removed the the "refresh_rate_hz" parameter. I was never sure what that did. I assume MWorks now gets the refresh rate from the hardware.

Thanks,
Mark

  1. Support Staff 1 Posted by Christopher Sta... on 16 Jul, 2015 05:28 PM

    Christopher Stawarz's Avatar

    Hi Mark,

    The new nightly has an option to use a "high precision clock (recommended)" ... Should we turn it on?

    Yes, I recommend that you turn it on. Actually, this has been available since 0.5.1. From the release notes:

    Added a new clock plugin (HighPrecisionClock) that supports more precise wait/sleep intervals (and, thereby, more accurate firing times for scheduled actions) than the old clock. Currently, it is not used by default but can be enabled via the #realtimeComponents variable.

    By "more precise", I mean that waits should be less likely to overshoot their target duration. That's not to say that we had a big problem with that with the old clock, but the new clock should still be better (and certainly no worse).

    Also, with the new Server preferences window, does the Server now ever read setup_variables.xml? Does it read it when MWorks is upgraded?

    There's no change in how MWorks uses setup_variables.xml. Changes made via the MWServer preferences window are written to the user-specific setup_variables file (which is created if it doesn't already exist).

    You also seem to have removed the the "refresh_rate_hz" parameter. I was never sure what that did. I assume MWorks now gets the refresh rate from the hardware.

    It never did anything (at least, not since I've been working on MWorks). MWorks never attempts to change the display's refresh rate. That's left to the user (via System Preferences or some third-party software).

    Cheers,
    Chris

  2. Christopher Stawarz closed this discussion on 16 Jul, 2015 07:45 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac