Jai Bhagat

when a visual stimulus element's `show` property is set to true, could this trigger a callback that fills the `Screen` buffer? If not, do you know of code anywhere else...

> If that were the case you would never see a stimulus at the same time as the sync square. I hypothesize that you would still see both so long...

Great you found what is likely the cause! That is interesting/concerning though that it is a `FillRect` issue. Wonder if it's an issue with other `Screen` function calls as well...

have you tried with other `Screen` function calls? e.g., using the following as `Screen` input args: `FillArc`, `FillOval`, `FillPoly`, `DrawArc`, `DrawLine` ?

Another thing worth noting is that the issue may be caused by `Screen('AsyncFlipBegin')` instead of using `Screen('Flip')`. http://psychtoolbox.org/docs/Screen-AsyncFlipBegin. > In general you should avoid using asynchronous flips and instead use...

Could it be the case that the `Screen('FillRect')` sometimes does nothing because there are times when it is run when the Screen is in an async flip state?

Haven't run the current tests on this yet because I wanted your general opinion on this PR. I can check tomorrow. And yeah, I'll add test(s) here too.

> It seems the preference of @dendritic is to implement functions like round this was done in this merge: https://github.com/cortex-lab/signals/commit/d6f816b57d7c899d63825ba8d8226dcff4cffd84 but 'circLayer' still can't take 'dims' as a signal due...

Setting appropriate abstraction/encapsulation would benefit this package: ``` [Miles Wells 02/05/19 17:24] In the documentation I try to clearly differentiate between the fields/parameters/values/etc. that define a texture (i.e. the structs...

Thanks for that link, that's nice. Sure, I agree with most of this, and additionally this isn't high priority. I have cursorily thought about scalability, design, and testing for this...