Re: [Denemo-devel] Denemo warnings and code cleanup

[Richard Shann]

Inside Denemo's code "print" was used to mean running an external
process (LilyPond) to generate a pdf or png document. The printstatus
structure is just a description of a set of variables used to control
background/foreground "printing"; that is, there is only one variable of
the type printstatus which is global to print.c, that being the variable
PrintStatus.
On Sun, 2013-05-26 at 23:04 +0200, Éloi Rivard wrote:
> In print.c, could you tell me what is the Printstatus structure ? I
> believe it is a structure that deals with the Lilypond process, am I
> right?
> 
> My English is far from perfect, in a general way, I feel the word
> "print" ambiguous.
AFAIK it means typeset, except for the menu item Print which typesets if
need be and then invokes the system printer dialog.
>  If you look in the print menu, sometimes it means "print", with a
> printer, and sometimes it means "output", "display" or even "export".
It used to include export but those were moved to Export a while ago.
What are the "output" and "display" cases you refer to?
I did wonder about replacing Print with Typeset, but decided against it
because naive users would not understand, they think "I want to print
this" and are only vaguely aware of the need to typeset it first. OTOH I
stopped popping up the printer dialog for every "Print" command, because
people want to examine the typesetting and probably tweak it before
actually invoking Print, which they will do from the Print View (which I
did consider naming Typeset View, but again decided against it), after
they have looked through the typeset score.

Richard


> 
> 
> 
> 2013/5/21 Richard Shann <address@hidden>
>         On Tue, 2013-05-21 at 14:07 +0200, Éloi Rivard wrote:
>         > In the branch keymap-refactoring, I refactored a bit
>         keymapio.c,
>         > kbd-custom.c and keyboard.c so it will be a bit easier to
>         add a new
>         > xml field. Now we would need to add a new field in
>         command_row, fill
>         > it from xml, and store it into the keymap, no function
>         prototype
>         > change would be required.
>         >
>         > Could you please check that it works for you?
>         
>         
>         This seems to be working fine - I created a new command,
>         loaded it,
>         stored it with my default command set &c, all seems good :)
>         
>         Richard
>         
>         
> 
> 
> 
> -- 
> Éloi Rivard - address@hidden
>         
> « On perd plus à être indécis qu'à se tromper. »
>