Re: [Libvisual-devel] VisParamContainer question

[Dennis S. <den...@gm...>]

On 10/31/07, Burkhard Plaum <pl...@ip...> wrote:
>
> Hi,
>
> Dennis Smit schrieb:
> > Parameters:
> > There is no nth parameter function because parameters are entered in a
> > hashmap by their name. You can iterate this hashmap tho!
> >
> > visual_collection_foreach_do
> > (VISUAL_COLLECTION(&paramcontainer->entries), VisHashmapChainEntry
> *entry)
> > {
> >  char *name = entry->key.key.string;
> >  VisParamEntry *paramEntry = VISUAL_PARAMENTRY(entry->data);
> > } visual_collection_foreach_end;
>
> That's not for 0.4.0, only for CVS, right? Depending on non-released libs
> is
> not good. Any alternative, which works with 0.4.0? Maybe with
> visual_collection_get_iter()/visual_collection_iter_next()?


You are completely right!!! my mistake.

the example I posted was using macros for:

VisCollectionIterator iter;
visual_collection_get_iterator (&iter, collection);
while (visual_collection_iterator_has_more (&iter)) {
 VisHashmapChainEntry *entry = visual_collection_iterator_get_data (&iter);
 visual_collection_iterator_next (&iter);
 }
 visual_object_unref (VISUAL_OBJECT (&iter));
}


> I have to admit that I didn't test this, and also won't deny that this
> > should have been much easier.
>
> Indeed :)
>
> > Another (half completed) feature is the VisUI stuff that plugins can
> > expose which is an abstract representation of the configuration UI.
>
> I need to convert the parameter descriptions to gmerlins own format,
> which can then be used for saving values in the registry, building GUI
> dialogs or passing options on the commandline. Gmerlin plugins never
> assume a GUI to be present, they just tell what parameters they have.


The same goes for libvisual actually, however there is a system to describe
the potential gui, that is all ;)

Foreign plugins (ladspa or libvisual), get a small wrapper, which lets
> them behave exactly as native plugins.


Sounds good!