ffalarms 0.3 -- recurring alarms

[W.Kenworthy]

On Mon, 2009-10-26 at 22:48 +0100, Łukasz Pankowski wrote:
> William Kenworthy <billk at iinet.net.au> writes:
> 
> > Can I add to that request? - Ive just upgraded to ver2 and forgot I had
> > knobbled the puzzel on the old version ... so once .3 hits the shr feeds
> > I will have to spend more time decompiling, figuring out how it works,
> > kill the puzzel then compile it back up again - painful way to fix what
> > is to me a major usability problem (I cant see the numbers without
> > glasses, and of course I am not wearing glasses when the alarm goes off
> > in the morning :)
> >
> > Perhaps, make it a configuration option would make good sense then you
> > can continue torturing those poor souls who like it :)
> 
> :))
> 
> >
> > Its quite a good, reliable program, far better than the basic elementary
> > alarm and I use it most days more than once.  Good work.
> 
> Thanks.  Would turning off the alarm with a slider (please read my reply
> to Marcel for details) be fine for you?
> 
> I have done the one line hack for you (as I know the code :)) -- it
> makes every of four buttons immediately solve the puzzle.  Attached
> ffalarms.edj, put it as /usr/share/ffalarms/ffalarms.edj in your neo and
> it should work with ffalarms 0.2.4 and ffalarms 0.3 (not much tested :)).
> 
> The change was:
> 
> Index: ffalarms.edc
> ===================================================================
> --- ffalarms.edc	(revision 60)
> +++ ffalarms.edc	(working copy)
> @@ -523,7 +523,7 @@
>                  script {
>                      new s[2];
>                      getsarg(1, s, 2);
> -                    clicked(atoi(s));
> +                    emit("solved", "");
>                  }
>              }
>          }
> 
> 


Hi Lucasz, thanks for that - pretty similar to what I have done.

I have a particular HATRED of sliders - particularly the way shr uses
them - they take several swipes before they work and require careful
placement of the finger to "grab" them and move.  To me a slider is for
analog values - buttons are for on/off.

I realise you are worried about the alarm being accidentally
acknowledged - never found that to be a problem because I usually use
something like shr-today so the alarm comes up with the screen protected
(and shr today already uses a slider - grrrrr - so then there are
serial, multiple sliders to deal with - ggggrrrrrrrr :)  Even when I
dont use the today screen, there doesnt seem to be any problem when
carrying the phone in a pocket.  Looks to me like a problem that doesn't
need solving.  Note that the alarms on the other phones I have at home
dont have such devices so I question whether they are necessary at all.
This why a "disable/enable" in the settings file might be the easiest
way to deal with this.

One thing I have noticed with 0.2 is that the alarm isn't very loud and
the FR seems to go to sleep before the alarm gets loud enough to hear -
its inaudible except when there is nearly no environment noise.  0.1
seems to get a lot louder, and faster.  Something to think of for your
todo list is checking the profile setting before sounding the alarm - an
alarm going off in a meeting is just as disruptive as a phone ring.

0.3 is coming to shr-u soon so I'll see if that's any better in the
sleep department then.

Billk