Age | Commit message (Collapse) | Author |
|
|
|
Interpolation errors still need addressing.
|
|
|
|
changes the visibility status of the item (i.e. make no-ops really be no-ops)
|
|
|
|
|
|
than drawing the entire region as a single rect
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
export
|
|
|
|
|
|
|
|
|
|
|
|
files
|
|
and breakout get_win_special_folder() into its own file
|
|
|
|
windows.
I may have gotten the precise linkflags string incorrect, but this my best guess.
|
|
|
|
|
|
|
|
|
|
|
|
appropriate everywhere, needs testing)
|
|
|
|
will require a different solution (if they exist)
|
|
|
|
|
|
This would have had the effect of hiding -DPACKAGE="ardour_osc" but since there is no i18n stuff in our OSC support,
it really had no effect.
|
|
default), -DLIBCANVAS_DLL_EXPORTS=1 is not lost
|
|
|
|
|
|
__attribute__((visibility)) for export control
|
|
environment vars provide the "default", but are no longer
relevant once ardour-internal paths are configured.
|
|
plugin-scan should always happen explicitly (either on start
or by user request).
|
|
typical GUI toolkits
|
|
|
|
Presmooth with quadratic bezier, then interpolate when rendering. Not finished yet
|
|
button"
|
|
|