From: Josh Cheek <josh.cheek@...>
Date: 2013-03-12T14:28:49+09:00
Subject: Re: Extending Ruby. Little help or guidance if you are willing!

--f46d042c64b930fb6704d7b390bd
Content-Type: text/plain; charset=ISO-8859-1

Rereading this, I suspect that you might have mis-analyzed the issue. I
don't know how the profiler works, but if it's just looking at total time,
then it should see you spend a lot in this method, because it has both IO,
and a sleep statement inside of it. The 10-20% could just be what it takes
to run the Ruby runtime. The flickering could be due to

  io.write(power, HIGH)
  sleep delay
  io.write(power, LOW)

I don't know about your device, but is there actually value to writing low
at all? Could that cause it to flicker?


On Mon, Mar 11, 2013 at 10:44 AM, Cliff Rosson <cliff.rosson@gmail.com>wrote:

> Got ya. So it doesn't really matter if I convert things to ID and compare
> on that basis or keep things a symbol. Thanks Bartosz.
>
>
That's true if you mean to just swap them straight over, to avoid creating
lots of throw-away arrays and iterating over them.

There isn't enough code here to know what you can do (e.g. do you have
control over the representation shown by display.segments), or to play with
it (or, for me, to even really understand how the pieces fit together) but
if your low-level lib takes something like a number where each digit or
each bit represents the value of a pin in that position, then you could
just deal with ints like this:

    case num.to_s
    when '0' then 0b1111110
    when '1' then 0b0110000
    when '2' then 0b1101101
    when '3' then 0b1111001
    when '4' then 0b0110011
    when '5' then 0b1011011
    when '6' then 0b1011111
    when '7' then 0b1110000
    when '8' then 0b1111111
    when '9' then 0b1110011
    end

--f46d042c64b930fb6704d7b390bd
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div><div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-si=
ze:13px;background-color:rgb(255,255,255)">Rereading this, I suspect that y=
ou might have mis-analyzed the issue. I don&#39;t know how the profiler wor=
ks, but if it&#39;s just looking at total time, then it should see you spen=
d a lot in this method, because it has both IO, and a sleep statement insid=
e of it.=A0<span style=3D"font-size:small;background-color:transparent">The=
 10-20% could just be what it takes to run the Ruby runtime.=A0</span>The f=
lickering could be due to</div>
<div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13=
px;background-color:rgb(255,255,255)"><br></div><div style=3D"color:rgb(34,=
34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255=
,255,255)">
<font face=3D"arial, sans-serif">=A0 io.write(power, HIGH)</font></div><div=
 style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;b=
ackground-color:rgb(255,255,255)"><font face=3D"arial, sans-serif">=A0 slee=
p delay</font></div>
<div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13=
px;background-color:rgb(255,255,255)"><font face=3D"arial, sans-serif">=A0 =
io.write(power, LOW)</font></div></div><div><font face=3D"arial, sans-serif=
"><br>
</font></div><div><font face=3D"arial, sans-serif">I don&#39;t know about y=
our device, but is there actually value to writing low at all? Could that c=
ause it to flicker?</font></div><div><br></div><div><br></div>On Mon, Mar 1=
1, 2013 at 10:44 AM, Cliff Rosson <span dir=3D"ltr">&lt;<a href=3D"mailto:c=
liff.rosson@gmail.com" target=3D"_blank">cliff.rosson@gmail.com</a>&gt;</sp=
an> wrote:<br>
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">=
Got ya. So it doesn&#39;t really matter if I convert things to ID and compa=
re on that basis or keep things a symbol. Thanks Bartosz.</div>
<div class=3D"gmail_extra"><div><div class=3D"h5"><br></div></div></div></b=
lockquote><div><br></div><div>That&#39;s true if you mean to just swap them=
 straight over, to avoid creating lots of throw-away arrays and iterating o=
ver them.</div>
<div><br></div><div>There isn&#39;t enough code here to know what you can d=
o (e.g. do you have control over the representation shown by display.segmen=
ts), or to play with it (or, for me, to even really understand how the piec=
es fit together) but if your low-level lib takes something like a number wh=
ere each digit or each bit represents the value of a pin in that position, =
then you could just deal with ints like this:</div>
<div><br></div><div><div>=A0 =A0 case num.to_s</div><div>=A0 =A0 when &#39;=
0&#39; then 0b1111110</div><div>=A0 =A0 when &#39;1&#39; then 0b0110000</di=
v><div>=A0 =A0 when &#39;2&#39; then 0b1101101</div><div>=A0 =A0 when &#39;=
3&#39; then 0b1111001</div>
<div>=A0 =A0 when &#39;4&#39; then 0b0110011</div><div>=A0 =A0 when &#39;5&=
#39; then 0b1011011</div><div>=A0 =A0 when &#39;6&#39; then 0b1011111</div>=
<div>=A0 =A0 when &#39;7&#39; then 0b1110000</div><div>=A0 =A0 when &#39;8&=
#39; then 0b1111111</div>
<div>=A0 =A0 when &#39;9&#39; then 0b1110011</div><div>=A0 =A0 end</div></d=
iv><div><br></div><div><br></div></div>

--f46d042c64b930fb6704d7b390bd--