Page 2 of 2

Re: My eagle eyes surrender... (Ruby Issue)

Posted: Wed Jul 15, 2015 1:31 pm
by tulamide
KG_is_back wrote:I think I don't understand what (you think) the issue is...
Yes, you don't understand. But I just don't know how to explain it in any other way.

For example, you are so homed in on the counter (@cx), although I already said in my second post
tulamide wrote:Of course I resetted the value before calling the draw method in the original. This example code was just to make absolutely sure that the value changed from valid to invalid between the event happening and the execution. I experienced the very same with my original code.

Still you insist on it. It is not the reason for my problem. I don't know how else I can say it.

You also mentioned this several times:
KG_is_back wrote:you need "buffer", to store the finished block for later drawing (like in example 2. you used @v to store exact value of @cx when redraw was called, opposed to when the draw happened).

But I already said
tulamide wrote:I don't care when exactly the drawing will happen. In my main code there's a copy of the array that will be drawn (aka the buffer). And, as I already said, that works just fine. No issues. The issue arises only when I use the frame size to calculate the block size. If I hardcode the blocksize, it again works.


Ignoring issues like the "int instead of float" one is dangerous. For exampe, it means the difference of 1 frame of data. It also means a quicker flow, leaving less headroom. Etc.

Re: My eagle eyes surrender... (Ruby Issue)

Posted: Wed Jul 15, 2015 3:00 pm
by KG_is_back
Can you then describe in simple steps what you are trying to achieve? and what you expect the outcome to be vs. what it is? Because I believe I did explain behaviour in both scenarios correctly (1. resetting counter in event method = block will have fixed size and redraws will happen at cca.30fps 2. resetting counter in draw method = block will be bigger than anticipated and redraws will happen at <30fps)

Re: My eagle eyes surrender... (Ruby Issue)

Posted: Wed Jul 15, 2015 7:43 pm
by tulamide
The more I try to make it run, the worse it gets. I'm not even sure anymore, if my example was the best one for my issue. I'll pm you with the real project in its current state.