Maybe bigcal_update_current could be changed to
bigcal_update_current(bigcal_timetype in time, bigcal_datetype in
date). This way you can name them whatever you like.

include big_calendar
var bigcal_timetype time
var bigcal_datetype date

time.second = 0
time.minute = 0
time.hour   = 8
date.day    = 1
date.month  = 1
date.year   = 2012

forever loop
   delay_1s(1)
   time.second = time.second + 1
   bigcal_update_current(time, date)
end loop

Matt.

On Apr 18, 12:05 am, Oliver Seitz <[email protected]> wrote:
> > I guess I'm confused weather your
> > library should use a RTC, or should
> > take user input. For example, what day of the week is today,
> > or what
> > day of the week is March 1st 2013?
>
> ATM, records are used. Therefore, today looks like this
>
>     x=bigcal_weekday(bigcal_current_date)
>
> Next saturday is
>
>     var bigcal_datetype searchdate
>
>     searchdate=bigcal_current_date
>
>     while bigcal_weekday(searchdate) != 6 loop
>       bigcal_add_days(searchdate,1)
>     end loop
>
> March, 1st 2013 is
>
>     searchdate.day=1
>     searchdate.month=3
>     searchdate.year=2013
>     x=bigcal_weekday(searchdate)
>
> I really like this record thing here.
>
>     x=bigcal_weekday(bigcal_current_date)
> or
>     x=bigcal_weekday(date_year,date_month,date_day)
>
>     var bigcal_datetype searchdate
>     searchdate=bigcal_current_date
> or
>     var byte searchday
>     var byte searchmonth
>     var word searchyear
>
>     searchday=date_day
>     searchmonth=date_month
>     searchyear=date_year
>
> It is much more readable using records and some errors can not even occur 
> (like accidentally swapping month and day or so.)
>
> Greets,
> Kiste

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/jallib?hl=en.

Reply via email to