> I've looked at it, but I don't really know how the calendar functions
> are supposed to behave. Pretty hard to fix if you don't know what is
> 'right' :)I'll gladly accept input on what would be the desired
> behaviour and I'll try to make it so.
Hehe. Ok what I would like, is to have a function like this:
mgd_list_topic_date_created_all($topicid,$start,$stop,string [sort], int
[type]);
and
list_topic_date_created_all_fast
that returns the object without the author field set.
and where:
$start & $stop are unix timestamps
and they look at the _created_ field.
Hmm. After some thinking, this might be my misstake. (GRRRR). The function does
everything based on the calander fields in the article, while I need one for the
created field. Darn, (getting read in the head).
This is the type of trouble that comes from looking at a problem too long :)
how hard would it be to make this extra function?
Tarjei
>From the manual:
Lists calendar entry articles under the topic tree starting at topic with id
topic. Normally the function returns
the calendar entries that are currently happening or happen in future. The
entries are sorted by date. To list old
calendar entries or to limit a query to a specific time range, use the
alternative function signature.
Returns an object traversable by calling fetch if successfull. Returns FALSE
on failure.
>
> Emile
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
