197 commits

Author	SHA1	Message	Date
Tom Poole	88b6a400f8	Resave all projects	2022-08-15 17:37:04 +01:00
Tom Poole	c2180845bc	Resave all projects	2022-08-15 17:26:22 +01:00
Tom Poole	a72f508a47	Android: Use default architectures for projects in extras	2022-07-06 11:29:20 +01:00
Tom Poole	f82430c746	Resave all projects	2022-07-04 15:33:44 +01:00
Tom Poole	1a578f787c	Resave all projects	2022-06-21 08:51:47 +01:00
Tom Poole	cdd619e7a1	Xcode: Update LastUpgradeCheck	2022-06-01 13:57:33 +01:00
Tom Poole	8c48956681	Resave all projects	2022-05-23 13:18:08 +01:00
Tom Poole	2ec861d99e	Update licensing banners to JUCE 7	2022-05-16 17:55:48 +01:00
attila	10d32c104d	Resave all projects	2022-05-12 12:31:30 +02:00
Tom Poole	c2ecde591b	macOS: Remove 32 bit specific functionality ... This includes Carbon support	2022-05-03 08:16:37 +01:00
Tom Poole	b48dddcf4e	RTAS: Remove RTAS functionality	2022-05-03 08:16:37 +01:00
Tom Poole	f69fe7be0f	Resave projects	2022-04-26 15:30:29 +01:00
reuk	61f3c1dd98	LV2: Add initial client support	2022-04-22 14:18:52 +01:00
reuk	1182024fc4	LV2: Add initial hosting support	2022-04-22 14:18:51 +01:00
Tom Poole	570bcb666a	Resave projects	2022-04-22 14:18:48 +01:00
Tom Poole	3dd812052e	macOS/iOS: Add a Metal layer renderer ... This restores the functionality of JUCE_COREGRAPHICS_RENDER_WITH_MULTIPLE_PAINT_CALLS. Using this preprocessor flag may avoid Core Graphics rendering much larger regions than necessary, but the small regions that are rendered will likely be rendered slower. Whether using this flag improves or degrades the performance of your rendering overall will be specific to each application. Previously enabling JUCE_COREGRAPHICS_RENDER_WITH_MULTIPLE_PAINT_CALLS was ineffective from versions of macOS around 10.13, but enabling it didn't have any negative impact on performance. Now enabling JUCE_COREGRAPHICS_RENDER_WITH_MULTIPLE_PAINT_CALLS may result in slower rendering.	2022-04-04 12:36:33 +01:00
Tom Poole	dea3fe60e4	Update copyright banners	2022-04-04 12:36:32 +01:00
reuk	1e820fd362	Resave projects	2022-03-23 16:51:39 +00:00
Tom Poole	ccd3a29cc7	Resave all projects	2022-03-04 11:48:48 +00:00
Tom Poole	a0994ac576	Resave all projects	2022-02-28 12:59:09 +00:00
Tom Poole	086b21be1b	Re-save all projects	2022-02-23 15:06:22 +00:00
Tom Poole	300ab8b084	Resave all projects	2022-02-18 16:28:51 +00:00
Tom Poole	4eb6eb828a	Resave all projects	2022-01-26 13:06:01 +00:00
Tom Poole	ea5dae4ab6	Remove some unused properties from .jucer files and re-save all projects	2022-01-25 11:25:08 +00:00
Tom Poole	da5e0e0cd3	Resave all projects	2021-12-20 11:14:39 +00:00
ed	156722d299	Re-save projects	2021-12-14 17:01:26 +00:00
ed	4f49032fa8	Re-save projects	2021-12-10 15:50:04 +00:00
reuk	c9b28be145	Resave all projects	2021-12-08 15:26:08 +00:00
reuk	221a137526	Resave projects	2021-11-19 16:35:22 +00:00
ed	a970b15959	Add Visual Studio 2022 solutions to all projects	2021-11-09 15:35:45 +00:00
ed	bfea8c89b0	Re-save all projects	2021-11-08 09:04:11 +00:00
reuk	b72b155443	Naming: Fix up naming of ChildProcessCoordinator and ChildProcessWorker	2021-10-25 09:51:21 +01:00
ed	c6f4d8494c	Re-save all projects	2021-10-15 10:10:55 +01:00
ed	bb9b24d048	Re-save all projects	2021-10-05 16:30:26 +01:00
ed	49fdf1a4d3	Re-save all projects	2021-09-23 14:26:05 +01:00
reuk	3768349a05	Font: Make Font and TypefaceCache threadsafe ... Previously, it wasn't safe to access Font instances from multiple threads because there was a chance that they might reference the same shared internal state. In this case, calling getTypeface() or getAscent from two threads simultaneously would cause a race on the typeface and ascent data members, even though the Font instances appeared to be disjoint. With this change in place, it is now safe to use Font instances from multiple threads simultaneously. It is still an error to modify the same Font instance from multiple threads without synchronization! // Fine: Font a; Font b = a; auto futureA = std::async (std::launch::async, [&a] { /* do something with a */ }); auto futureB = std::async (std::launch::async, [&b] { /* do something with b */ }); // Bad idea: Font f; auto futureA = std::async (std::launch::async, [&f] { /* do something with f */ }); auto futureB = std::async (std::launch::async, [&f] { /* do something with f */ });	2021-09-23 10:28:47 +01:00
reuk	23e621f26e	Projucer: Add BOM when writing VS solution files ... Without the BOM, VS assumes UTF-8 strings (subproject file names etc.) are ansi-encoded.	2021-09-22 10:23:03 +01:00
Tom Poole	6f4618f9bc	Re-save all projects	2021-09-20 13:24:39 +01:00
Tom Poole	1c7dc0b053	Re-save all projects	2021-09-09 12:57:24 +01:00
Tom Poole	3833c6d207	Re-save all projects	2021-08-23 10:17:46 +01:00
ed	b13af2df95	Re-saved all projects	2021-08-16 16:13:59 +01:00
ed	63f2a7c30c	Re-saved all projects	2021-08-11 12:01:05 +01:00
ed	7ab0c9812a	Re-saved all projects	2021-07-28 11:44:29 +01:00
ed	ff935c5103	Re-saved all projects	2021-07-28 09:23:24 +01:00
ed	d394c770c9	Re-saved all projects	2021-07-22 16:33:42 +01:00
ed	f38f721794	Re-saved all projects	2021-07-21 16:34:22 +01:00
ed	b41b80ed7c	Re-saved all projects	2021-06-21 18:55:14 +01:00
ed	37eb70d676	Re-saved all projects	2021-06-16 10:15:54 +01:00
ed	c0f18670f4	Re-saved all projects	2021-06-09 16:04:39 +01:00
ed	430ffd4b96	Re-saved all projects	2021-06-07 19:38:29 +01:00