Discussion:
some changes.
dean blackketter
2001-11-30 03:56:17 UTC
Permalink
Dean,
This sounds excellent. Maintaining client state in a clean structure with
so many things going on has been a real challenge.
Yup. It's getting better, albeit slowly...
BTW I like the way all of the animations are interruptible - eg if I want
to move up two directories real quick, I don't have to wait for the
animation to finish. This still works with the new logic, right?
Of course.
Check it in!
Done!

-dean

------------------------ Yahoo! Groups Sponsor ---------------------~-->
Universal Inkjet Refill Kit $29.95
Refill any ink cartridge for less!
Includes black and color ink.
http://us.click.yahoo.com/iHh8lD/MkNDAA/ySSFAA/rIp0lB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
slimp3-dev-unsubscribe-***@public.gmane.org



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
dean blackketter
2003-02-22 13:19:46 UTC
Permalink
<!doctype html public "-//W3C//DTD W3 HTML//EN">
<head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
--></style><title>Re: [slimp3-dev] some changes.</title></head><body>
<blockquote type="cite" cite>Dean,<br>
<br>
This sounds excellent. Maintaining client state in a clean structure
with<br>
so many things going on has been a real challenge.</blockquote>
<div><br></div>
<div>Yup.&nbsp; It's getting better, albeit slowly...</div>
<div><br></div>
<blockquote type="cite" cite>BTW I like the way all of the animations
are interruptible - eg if I want<br>
to move up two directories real quick, I don't have to wait for
the<br>
animation to finish. This still works with the new logic,
right?</blockquote>
<div><br>
Of course.</div>
<div><br>
<br>
</div>
<blockquote type="cite" cite><br>
Check it in!</blockquote>
<div><br>
<br>
</div>
<div>Done!</div>
<div><br></div>
<div>-dean</div>
</body>
</html>
Sean Adams
2001-11-29 21:59:29 UTC
Permalink
Dean,

This sounds excellent. Maintaining client state in a clean structure with
so many things going on has been a real challenge.

BTW I like the way all of the animations are interruptible - eg if I want
to move up two directories real quick, I don't have to wait for the
animation to finish. This still works with the new logic, right?

Check it in!

Sean
Hi All,
I got sick of a few bugs and went after them. Trouble is it's a fair
sized change to the source base. Good news is it seems to fix all
the cosmetic bugs I could find.
Before I check it in, I want to get consensus from folks that I'm
doing the right thing at this point in the release cycle. I'd be
happy to hold off, but I'm confident that the server has fewer bugs
after I finished than before.
In short, I simplified the way that we keep track of the current
current display state in a single $client->mode variable, rather than
trying to remember what the last thing we displayed along with
several other mode tracking variables.
We now update the screen based on the current mode, rather than
explicitly telling the display what do show. We also have a
"screenSaver" now that the display reverts to if you haven't touched
the remote for a while. This handles the clock in power-off as well
as the current track while powered on and the flashing PAUSED
information. The code's a lot cleaner and simpler, and makes it
almost trivial to have a top-level navigation area for switching
between views and settings, etc... It will also be easier to have
the screensaver rotate between multiple screens of information and
animate, etc...
1. When you hit pause, the display started flashing. If you started
navigate around, it would keep flashing but would flash some random
stuff.
2. When you hit pause, fwd or rev when there was nothing playing you
got unpredictable results, including audio volume problems.
3. You could sometimes get unpredictable displays when skipping
around, pressing pause and pressing play. Now we seem to (afaict)
show the right thing.
1. During power off you can dim the clock all the way down to blank.
The dim state for power off is separate from power on. (This one's
for you, Amos...)
Diff available upon request.
Barring any protests, I'll check this in later tonight.
-dean
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
------------------------ Yahoo! Groups Sponsor ---------------------~-->
Universal Inkjet Refill Kit $29.95
Refill any ink cartridge for less!
Includes black and color ink.
http://us.click.yahoo.com/4bQK.B/MkNDAA/ySSFAA/rIp0lB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
slimp3-dev-unsubscribe-***@public.gmane.org



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
sam_saffron-/
2001-11-29 21:58:07 UTC
Permalink
In short, I simplified the way that we keep track of the current
current display state in a single $client->mode variable, rather
than
trying to remember what the last thing we displayed along with
several other mode tracking variables.
Thats great, it will help us centralise the server display routine,
and implementing the press chdown for 5 secs to kill the display and
track time will be heaps easier ...


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Universal Inkjet Refill Kit $29.95
Refill any ink cartridge for less!
Includes black and color ink.
http://us.click.yahoo.com/f00vhB/MkNDAA/ySSFAA/rIp0lB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
slimp3-dev-unsubscribe-***@public.gmane.org



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
dean blackketter
2001-11-29 21:42:26 UTC
Permalink
I got sick of a few bugs and went after them. Trouble is it's a fair
sized change to the source base. Good news is it seems to fix all
the cosmetic bugs I could find.
Sounds good Dean. I have notice a few of the bugs you mentioned and was
trying to find a way to describe what I was seeing and steps to reproduce.
Glad I don't have to now.
I still have some playlist files that crash the server. I'd be happy to
send them to you if you think that shouldn't be happening at this stage.
Fire away...
--
Amos Hayes
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
------------------------ Yahoo! Groups Sponsor ---------------------~-->
Universal Inkjet Refill Kit $29.95
Refill any ink cartridge for less!
Includes black and color ink.
http://us.click.yahoo.com/4bQK.B/MkNDAA/ySSFAA/rIp0lB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
slimp3-dev-unsubscribe-***@public.gmane.org



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
dean blackketter
2001-11-29 21:23:43 UTC
Permalink
Hi All,

I got sick of a few bugs and went after them. Trouble is it's a fair
sized change to the source base. Good news is it seems to fix all
the cosmetic bugs I could find.

Before I check it in, I want to get consensus from folks that I'm
doing the right thing at this point in the release cycle. I'd be
happy to hold off, but I'm confident that the server has fewer bugs
after I finished than before.

In short, I simplified the way that we keep track of the current
current display state in a single $client->mode variable, rather than
trying to remember what the last thing we displayed along with
several other mode tracking variables.

We now update the screen based on the current mode, rather than
explicitly telling the display what do show. We also have a
"screenSaver" now that the display reverts to if you haven't touched
the remote for a while. This handles the clock in power-off as well
as the current track while powered on and the flashing PAUSED
information. The code's a lot cleaner and simpler, and makes it
almost trivial to have a top-level navigation area for switching
between views and settings, etc... It will also be easier to have
the screensaver rotate between multiple screens of information and
animate, etc...

Bugs I know I fixed:

1. When you hit pause, the display started flashing. If you started
navigate around, it would keep flashing but would flash some random
stuff.

2. When you hit pause, fwd or rev when there was nothing playing you
got unpredictable results, including audio volume problems.

3. You could sometimes get unpredictable displays when skipping
around, pressing pause and pressing play. Now we seem to (afaict)
show the right thing.

Features:

1. During power off you can dim the clock all the way down to blank.
The dim state for power off is separate from power on. (This one's
for you, Amos...)

Diff available upon request.

Barring any protests, I'll check this in later tonight.

-dean

------------------------ Yahoo! Groups Sponsor ---------------------~-->
Universal Inkjet Refill Kit $29.95
Refill any ink cartridge for less!
Includes black and color ink.
http://us.click.yahoo.com/f00vhB/MkNDAA/ySSFAA/rIp0lB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
slimp3-dev-unsubscribe-***@public.gmane.org



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Amos Hayes
2001-11-29 21:02:19 UTC
Permalink
I got sick of a few bugs and went after them. Trouble is it's a fair
sized change to the source base. Good news is it seems to fix all
the cosmetic bugs I could find.
Sounds good Dean. I have notice a few of the bugs you mentioned and was
trying to find a way to describe what I was seeing and steps to reproduce.
Glad I don't have to now.

I still have some playlist files that crash the server. I'd be happy to
send them to you if you think that shouldn't be happening at this stage.

--
Amos Hayes
ahayes-***@public.gmane.org


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Universal Inkjet Refill Kit $29.95
Refill any ink cartridge for less!
Includes black and color ink.
http://us.click.yahoo.com/4bQK.B/MkNDAA/ySSFAA/rIp0lB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
slimp3-dev-unsubscribe-***@public.gmane.org



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
dean blackketter
2003-02-22 13:19:55 UTC
Permalink
<!doctype html public "-//W3C//DTD W3 HTML//EN">
<head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
--></style><title>Re: [slimp3-dev] some changes.</title></head><body>
<blockquote type="cite" cite>On Thu, 29 Nov 2001, dean blackketter
wrote:<br>
<br>
&gt; I got sick of a few bugs and went after them.&nbsp; Trouble is
it's a fair<br>
&gt; sized change to the source base.&nbsp; Good news is it seems to
fix all<br>
&gt; the cosmetic bugs I could find.</blockquote>
<blockquote type="cite" cite><br>
Sounds good Dean. I have notice a few of the bugs you mentioned and
was<br>
trying to find a way to describe what I was seeing and steps to
reproduce.<br>
Glad I don't have to now.</blockquote>
<blockquote type="cite" cite><br>
I still have some playlist files that crash the server. I'd be happy
to</blockquote>
<blockquote type="cite" cite>send them to you if you think that
shouldn't be happening at this stage.</blockquote>
<div><br></div>
<div>Fire away...</div>
<div><br></div>
<blockquote type="cite" cite>--<br>
Amos Hayes<br>
ahayes-***@public.gmane.org<br>
<br>
<br>
------------------------ Yahoo! Groups Sponsor
---------------------~--&gt;<br>
Universal Inkjet Refill Kit $29.95<br>
Refill any ink cartridge for less!<br>
Includes black and color ink.<br>
http://us.click.yahoo.com/4bQK.B/MkNDAA/ySSFAA/rIp0lB/TM<br>
---------------------------------------------------------------------<span </span>~-&gt;<br>
<br>
To unsubscribe from this group, send an email to:<br>
slimp3-dev-unsubscribe-***@public.gmane.org<br>
<br>
&nbsp;<br>
<br>
Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/ </blockquote>
<div><br></div>
</body>
</html>
dean blackketter
2003-02-22 13:19:56 UTC
Permalink
Hi All,

I got sick of a few bugs and went after them. Trouble is it's a fair sized change to the source base. Good news is it seems to fix all the cosmetic bugs I could find.

Before I check it in, I want to get consensus from folks that I'm doing the right thing at this point in the release cycle. I'd be happy to hold off, but I'm confident that the server has fewer bugs after I finished than before.

In short, I simplified the way that we keep track of the current current display state in a single $client->mode variable, rather than trying to remember what the last thing we displayed along with several other mode tracking variables.

We now update the screen based on the current mode, rather than explicitly telling the display what do show. We also have a "screenSaver" now that the display reverts to if you haven't touched the remote for a while. This handles the clock in power-off as well as the current track while powered on and the flashing PAUSED information. The code's a lot cleaner and simpler, and makes it almost trivial to have a top-level navigation area for switching between views and settings, etc... It will also be easier to have the screensaver rotate between multiple screens of information and animate, etc...

Bugs I know I fixed:

1. When you hit pause, the display started flashing. If you started navigate around, it would keep flashing but would flash some random stuff.

2. When you hit pause, fwd or rev when there was nothing playing you got unpredictable results, including audio volume problems.

3. You could sometimes get unpredictable displays when skipping around, pressing pause and pressing play. Now we seem to (afaict) show the right thing.

Features:

1. During power off you can dim the clock all the way down to blank. The dim state for power off is separate from power on. (This one's for you, Amos...)

Diff available upon request.

Barring any protests, I'll check this in later tonight.

-dean

Continue reading on narkive:
Loading...