X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=src%2Foutput%2Fdriver-provider.h;h=1f3f726949575adf2905086f125bf44cac2f6d53;hb=eeb5800b97c3d4e768fb3f7cbdabf54b3bd162b4;hp=754b0d0b5677adaa54b7f37c550dfe643fe22a20;hpb=c924d7187269c30657e0ad2d5a989b30aeb85c3f;p=pspp diff --git a/src/output/driver-provider.h b/src/output/driver-provider.h index 754b0d0b56..1f3f726949 100644 --- a/src/output/driver-provider.h +++ b/src/output/driver-provider.h @@ -24,7 +24,10 @@ #include "output/driver.h" struct output_item; +struct output_iterator; struct string_map; +struct file_handle; +struct page_setup; /* A configured output driver. */ struct output_driver @@ -36,11 +39,14 @@ struct output_driver void output_driver_init (struct output_driver *, const struct output_driver_class *, - const char *name, enum settings_output_devices); + const char *, enum settings_output_devices); + void output_driver_destroy (struct output_driver *); const char *output_driver_get_name (const struct output_driver *); +char *output_driver_substitute_heading_vars (const char *, int page_number); + /* One kind of output driver. Output driver implementations must not call msg() to report errors. This @@ -61,6 +67,10 @@ struct output_driver_class void (*submit) (struct output_driver *driver, const struct output_item *item); + /* Changes DRIVER's output page setup to PS, if possible. This may be NUL + if the driver doesn't support page setup. */ + void (*setup) (struct output_driver *driver, const struct page_setup *ps); + /* Ensures that any output items passed to the 'submit' function for DRIVER have actually been displayed. @@ -69,11 +79,18 @@ struct output_driver_class it doesn't make sense for DRIVER to be used this way, then this function need not do anything. */ void (*flush) (struct output_driver *driver); + + /* Ordinarily, the core driver code will skip passing hidden output items + to 'submit'. If this member is true, the core driver hands them to the + driver to let it handle them itself. */ + bool handles_show; + + /* Ordinarily, the core driver code will flatten groups of output items + before passing them to 'submit'. If this member is true, the core + driver code leaves them in place for the driver to handle. */ + bool handles_groups; }; -/* Useful for output driver implementation. */ -void output_driver_track_current_command (const struct output_item *, char **); - /* An abstract way for the output subsystem to create an output driver. */ struct output_driver_factory { @@ -98,10 +115,9 @@ struct output_driver_factory The returned driver should not have been registered (with output_driver_register). The caller will register the driver (if this is desirable). */ - struct output_driver *(*create) (const char *name, + struct output_driver *(*create) (struct file_handle *, enum settings_output_devices type, struct string_map *options); }; - #endif /* output/driver-provider.h */