Paul Davis c4c6c38dbd do NOT use Glib::ustring unless you know that the contents are UTF-8 AND that you need to iterate glyph by glyph
This fixes a Glib::ConvertError that occured when using Glib::ustring::operator<<
inside a compose operation. This implicitly uses Glib::locale_from_utf8(), and if the string
is not legal UTF-8, an exception will be thrown.

std::string should be used EVERYWHERE unless glyph-by-glyph iteration is required. This is
very rare in the Ardour codebase, so you really shouldn't see Glib::ustring anywhere. The
main exception is handling user-input for a few specific cases.
2016-04-24 00:38:05 -04:00
2016-02-28 21:16:44 +01:00
2016-02-28 21:16:44 +01:00
2016-04-24 02:53:01 +02:00
2009-11-09 14:13:59 +00:00
2013-03-12 13:32:56 -04:00
2015-05-09 13:08:56 -04:00
2013-03-13 14:35:39 -04:00
2015-07-21 01:12:39 +02:00
2011-11-21 23:21:05 +00:00
2016-02-28 21:48:49 +01:00

Please see the Ardour web site at http://ardour.org/ for all documentation..

For information on building ardour: 
      
     http://ardour.org/development.html
Description
No description provided
Readme 202 MiB
Languages
C++ 56.5%
C 39.6%
JavaScript 1.3%
Lua 0.9%
Python 0.6%
Other 0.9%