Karya, built on Sun Nov 26 01:04:37 PST 2017 (patch 0a920b2bde70c0cbac8ee09d158064798b61bbe5)

App.StaticConfig

Contents

Description

StaticConfig is an app-level configuration hook. The idea is that the local configuration can use it to override things.

Synopsis

# static config

Constructors

 StaticConfig Fieldsinstrument_db :: Cmd.InstrumentDb global_cmds :: [Msg.Msg -> Cmd.CmdT IO Cmd.Status]These Cmds are run before any of the usual ones, and can implement local global keymaps and whatnot.library :: LibraryDefault global namespace for deriver calls.setup_cmd :: [String] -> Cmd.CmdT IO Cmd.StatusRun this on startup, given the app's argv. It can set up an initial block, load a given file, or do nothing. Remember that no block is focused when this is run, so cmds that need a focused block will abort.midi :: Midi highlight_colors :: Map Color.Highlight Color.Color

data Midi Source #

Constructors

 Midi Fieldsrdev_map :: Map Midi.ReadDevice Midi.ReadDeviceReroute the hardware level read and write devices. This way, instruments and saved scores can use symbolic names which are then mapped to the devices exported by the MIDI driver.Because input devices are likely to be relatively static, the read device map is only configured here.wdev_map :: Map Midi.WriteDevice Midi.WriteDeviceWriteDevices may vary per score, e.g. softsynths may listen at any number of virtual devices. This map is taken as a default, but may be overridden by the score loaded.read_devices :: Set Midi.ReadDeviceOpen the given devices on startup. Even if they aren't plugged in, they'll be added to the read list so they're automatically connected if they are plugged in. If you open a virtual device for both reading and writing you'll get a loop, so don't do that.There's no corresponding write_devices because if you don't want to write to a device, just don't write to it!

Instances

 # MethodsshowsPrec :: Int -> Midi -> ShowS #show :: Midi -> String #showList :: [Midi] -> ShowS #

Create a Cmd.Config from a StaticConfig.