Note that there are some explanatory texts on larger screens.

plurals
  1. USMark
    primarykey
    data
    text
    plurals
    1. This table or related slice is empty.
    1. CO@Dave: You shouldn't need to touch with a future date, using the current date should be fine. All you need to kick off the dependency cascade is a time/date stamp that is *newer* on the sources than on the products. Since the products have been built in the past, the current time should be all that's required to kick off the copy step. If you use some future time (like next year) you could run into the situation where it is always copied regardless of whether anything has changed. This can be time consuming if you're doing quick start/stops (eg debugging).
      singulars
    2. COI should note: when I say "Inputs are dropped" they're not actually dropped, they just lag by anywhere from a fraction of a second to up to 10 seconds. This is not the standard lag seen on iOS and other touch-screen devices, but more like the "Message consumption running slower than message generation" lag that's cumulative (gets longer as time goes on)
      singulars
    3. COit looks like you're doing things similar to the way we were, that is, getting rid of the .nib, etc. I find your "doEvents" method v. interesting, though, as my intuition tells me the problems I'm getting are in event handling. I'm going to have to experiment with that one. I'm also interesting in how you're initiating things in APRIL. For my loop initialization when I ran things in my own run loop I simply spawned another thread and managed things that way, and that worked great except for the software interrupt kicking in on the wrong thread.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload