[futurebasic] Re: [FB] Calendar Year On A Page

Message: < previous - next > : Reply : Subscribe : Cleanse
Home   : July 2001 : Group Archive : Group : All Groups

From: Ken Shmidheiser <k.shmidheiser@...>
Date: Mon, 30 Jul 2001 12:32:42 -0400
Chris Wyatt wrote from Oz,

>G'day Ken,

G'day Chris!

>you wrote:
>
>  > Here's a little app to create a entire calendar year on a page using
>  > FB^3 Release 5. (I was playing with DYNAMIC arrays and this is what
>  > came out of my brain fog!)
>
>Bloody beaut little app for such a fog.

Thanks for the nice compliment!

>  > As always, comments, critiques, bug reports welcome
>
>Could add the day of week when speaking the date.

I am working a better implementation of the Speech Manager stuff. I 
really just put it in there for the demo to let the program do 
something. I'd much rather have it build a database of information 
for each day clicked... But at least the shell is out there for 
everyone to use.

>  > I really would like to have a quicker response when redrawing the
>  > EDIT FIELDS. (I hoped Release 5 would be quicker in this, but I would
>  > still like more speed. Any suggestions?)
>
>Yes drawing of the boxes looked slow, even at 400Mhz. Maybe an 
>offscreen gWorld.

I'm trying to figure out how to implement this. Any help from the 
list will be greatly appreciated. (I am a gworld Phobic.)

>Also a print button.

Good idea.

>  > For demo purposes, this app speaks the date when a day EDIT FIELD is
>  > clicked. (This can get annoying but is easily killed by commenting
>  > out the _efClick  routines.)
>
>Why not a check box to turn on & off

I should have done this... or just left the speech out entirely!

>  > It would be nice to be able to click an EDIT FIELD, have a window
>  > open, and store info for that day as do the commercial calendar
>  > programs. Any suggestions on how to implement that?
>  >
>  > Anyway, maybe this will help you to build a little calendar in your
>  > apps, should you need one.
>
>Regards,
>
>Chris Wyatt, in Bendigo, Australia.

Thanks for the comments, Chris.

Best,

Ken