[gmpi] Re: Topic 8: Parameters
- From: Tim Hockin <thockin@xxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Thu, 7 Aug 2003 12:20:16 -0700 (PDT)
> > * The set of exported parameters are a snapshot of the current state of a
> > plugin.
> >
> > * Saving and restoring a full set of parameters is sufficient to resotre
> > the state of a plugin 'patch'.
> >
>
> I disagree with these two. It's too limiting to have the entire state of a
> plugin be defined by its parameters (when it comes to saving and loading that
> state).
As opposed to? We discussed this for XAP, too, and we couldn't find a REAL
reason that controls, with raw data blocks, were insufficient. An
alternative, I guess is:
typedef struct {
uint32_t magic; /* maybe useful, plugin defined */
uint32_t version; /* plugin specific */
uint32_t size; /* data size, in bytes */
unsigned char *data;
};
GMPI_state state;
plugin->save_state(&state);
write_state_to_output_file_somehow(&state);
free(state->data);
----------------------------------------------------------------------
Generalized Music Plugin Interface (GMPI) public discussion list
Participation in this list is contingent upon your abiding by the
following rules: Please stay on topic. You are responsible for your own
words. Please respect your fellow subscribers. Please do not
redistribute anyone else's words without their permission.
Archive: //www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe
Other related posts:
