59e6694405
fix lack of region trimming when not displaying name highlight bar
2014-04-16 09:03:16 -04:00
78bab09e98
improve comment text
2014-04-16 07:35:20 -04:00
0f7f9b068c
add preferences item for show-name-highlight (does not take effect till next instance)
2014-04-16 07:31:01 -04:00
e324249d8c
fix logic for Config->show_name_highlight (reversed from inital experiments)
2014-04-16 07:30:09 -04:00
981754781a
use new config option to control name highlight and name placement
2014-04-16 06:35:24 -04:00
cd8aa4e304
add new config parameter controlling visibility of name highlights in regions.
...
This also affects region name placement.
2014-04-16 06:31:24 -04:00
5668eea2a3
add a transparent rect that is always located at the bottom of the track canvas
...
This gives us an event/drag-n-drop/click target for things "at the bottom"
2014-04-16 04:16:56 -04:00
8b93576c18
not that anyone ever runs with the SAE profile and not that we want to support it, but don't crash if they do
2014-04-16 03:00:49 -04:00
dbb8501429
make our intentions even clearer when call Editor::track_canvas_viewport_size_allocated()
2014-04-16 02:55:08 -04:00
fea4f14242
make our intentions clear when call Editor::track_canvas_viewport_size_allocated()
2014-04-16 02:52:55 -04:00
0d1d50a8b4
remove pointless assert (since condition is if-tested just before it was used)
2014-04-15 14:30:37 -04:00
2b10af45ab
Ensure that 'fixup_bundle_environment()' returns a suitable localedir (msvc)
2014-04-15 18:53:24 +01:00
dc4eae5c37
hopefully fix issue with Editor::set_canvas_cursor_for_region_view() which was incorrectly switching to trim cursors.
...
This started happening more frequently after this function started to be called more often (which was the right thing to do, but
had this side effect (now fixed).
2014-04-15 12:44:49 -04:00
dbaf203bac
fix ridiculous spelling error
2014-04-15 12:44:49 -04:00
6edc47f71b
explicitly create MIDNAM folder in OS X app packaging
2014-04-15 12:44:49 -04:00
70755c9950
Add some stuff that's needed for an MSVC built target:-
...
1) Make sure we create or open any files in binary mode
2) Make sure the user can see an error message of we fail to parse the command line
3) Make sure that the call to 'windows_vst_gui_init()' matches its declaration (i.e. only applicable when NOT on PLATFORM_WINDOWS)
2014-04-15 11:01:48 +01:00
dcd18d84ef
Make sure that the preprocessor directive in 'winmain.cc' matches the one in 'main.cc'
...
(also, some minor housekeeping)
2014-04-15 10:56:12 +01:00
396fae31a9
Make sure that the input string doesn't go out of scope when using boost::tokenizer
2014-04-14 20:26:48 +01:00
16a8762dd4
fix minor problem with recent cherry-picking from cairocanvas
2014-04-14 14:14:30 -04:00
be0da8ff5c
merge 5764970709 from cairocanvas as final(?) change related to data loss
2014-04-14 13:07:07 -04:00
2e3a84b15a
check whether a source with the same path exists in session list not just on disk.
...
This is intended to catch a potential wierd condition where a source exists as a stub, but has not yet been written to disk,
and then a new source is created with the same path. Currently it is not understood how/when this might happen
2014-04-14 13:05:35 -04:00
b49bb451d2
further code simplification and rationalization related to MIDI source/file renaming
2014-04-14 13:05:21 -04:00
0d5f4c553a
dramatic change in logic and naming for operations related to adding a MIDI region on demand and cloning/unlinking
...
Existing code would cause data loss due to creation of two Source objects referring the same path, one with removable flags and one without. Careful code review suggested a variety of thinkos, function naming problems and other confusion that caused this. I have tried ot extensively comment what is going on with these operations, because it is one key area in which MIDI differs from audio: with audio, capture is the only way to add a new audio region, but for MIDI there are GUI input events that can add a new region.
2014-04-14 13:05:08 -04:00
384c0a9fac
redesign technique for naming/creating regions for MIDI clone (or other non-capture driven MIDI region creation operations).
...
See comments in Session::new_midi_source_name() for details.
2014-04-14 13:04:14 -04:00
2b3cb052ca
after cloning a MIDI region, mark the source file as non-removable. Fixes reports about missing MIDI files on the forums and IRC
2014-04-14 13:01:23 -04:00
e1bf151ab0
after cloning a MIDI region, mark the source file as non-removable. Fixes reports about missing MIDI files on the forums and IRC
2014-04-14 13:00:24 -04:00
99bf5d9eed
backport 1d85ab27a7 and ba128eea from cairocanvas branch to remove GIO (possible hotfix release)
2014-04-14 12:53:30 -04:00
7cc5f8b321
fix prev commit (MSVC release builds)
2014-04-14 17:59:28 +02:00
18d4fd9f37
fun with the c-preprocessor. platform dependent VST support.
2014-04-14 17:54:21 +02:00
57f09d5d9d
Now that we can build with VST support, make sure our MSVC build knows about it
2014-04-14 16:14:07 +01:00
4336f75d3b
Make sure that when building with MSVC, a Release build will launch without an annoying, floating console window
2014-04-14 16:14:06 +01:00
09d5d7f26b
remove code intended for use with basename(), fix memory leak since g_path_get_basename() returns a newly allocated string.
2014-04-14 15:21:29 +02:00
15c5d12321
clean up 6cc2812f2e (interim vst fixes)
2014-04-14 15:10:28 +02:00
56b9398208
despite what MSVC thinks, C is not C++.
2014-04-14 15:04:50 +02:00
eef4e1efee
-d (disable plugin) option takes no arguments
2014-04-14 12:26:10 +02:00
55bfe10fa6
make frame/trim handles transparent for now.
...
This is a new GUI feature that will not be completed for the 3.6 release, so just hide them.
2014-04-14 04:46:24 -04:00
5764970709
more work on linking file existence and removability
2014-04-14 03:03:35 -04:00
062dd5b71d
check whether a source with the same path exists in session list not just on disk.
...
This is intended to catch a potential wierd condition where a source exists as a stub, but has not yet been written to disk,
and then a new source is created with the same path. Currently it is not understood how/when this might happen
2014-04-14 02:17:31 -04:00
b81d57f049
further code simplification and rationalization related to MIDI source/file renaming
2014-04-14 02:17:30 -04:00
343b06d8d3
dramatic change in logic and naming for operations related to adding a MIDI region on demand and cloning/unlinking
...
Existing code would cause data loss due to creation of two Source objects referring the same path, one with removable flags and one without. Careful code review suggested a variety of thinkos, function naming problems and other confusion that caused this. I have tried ot extensively comment what is going on with these operations, because it is one key area in which MIDI differs from audio: with audio, capture is the only way to add a new audio region, but for MIDI there are GUI input events that can add a new region.
2014-04-14 02:17:30 -04:00
d2a31ab6ee
remove unnecessary include
2014-04-12 14:07:51 +02:00
unknown
d2ab2e8b31
another stab at a working vst on windows
2014-04-11 14:41:58 -05:00
unknown
9fe353c4a2
more vst tweaks
2014-04-11 14:23:35 -05:00
unknown
6cc2812f2e
interim vst fixes
2014-04-11 14:23:29 -05:00
f678700376
amend previous commit, remove cruft, no more extern function pointers
2014-04-11 19:36:17 +02:00
e359521fad
export fst functions (for MSVC)
2014-04-11 17:30:37 +02:00
670c066793
add manual reference to missing video-tools warnings
2014-04-11 17:24:50 +02:00
5d9c2104d2
Oops - correct some typos in my previous commit
...
(accidentally used G_DIR_SEPARATOR instead of G_SEARCHPATH_SEPARATOR)
2014-04-11 15:36:04 +01:00
d95de39339
Make sure we use the correct style of filepath separator on Windows
...
('libs/ardour/file_source.cc' still to be investigated)
2014-04-11 13:03:48 +01:00
c046b7c9d3
Remove 'pipex' from my pbd.vcproj as it's not needed for Ardour3
2014-04-11 12:59:03 +01:00
