- Apr 22, 2020
-
-
Fix #237
-
when creating groups by media id
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
Which will be used by the missing index schema checks
-
Hugo Beauzée-Luyssen authored
We now require all migrations to create all individual tables, triggers or indexes. This mean the createTables/createTriggers/createIndex functions always create all tables/triggers/indexes at the current version, which in turn means there's no use for the additional parameter, nor do we need to create old schemes.
-
- Apr 15, 2020
-
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
-
- Apr 09, 2020
-
-
Hugo Beauzée-Luyssen authored
This reverts 1cfef937 Fix #234
-
Hugo Beauzée-Luyssen authored
refs #234
-
- Apr 03, 2020
-
-
Steve Lhomme authored
Fixes the build with mingw64 in winrt mode.
-
- Mar 26, 2020
-
-
Hugo Beauzée-Luyssen authored
-
- Mar 25, 2020
-
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
So that 3rd parties device listers also get them
-
Hugo Beauzée-Luyssen authored
And restore them when they reappear, once the appropriate device lister are started
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
All background services are now started lazily
-
Hugo Beauzée-Luyssen authored
Only on explicit use for now
-
Hugo Beauzée-Luyssen authored
Since it now does those 2 things. This also clarifies the distinction between this method and refreshDevice( fs::IFileSystemFactory& )
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
Only start them when network discovery is enabled
-
Hugo Beauzée-Luyssen authored
Instead of relying on a dedicated task, to be run only once as the first task, just call the function directly & automatically.
-
Hugo Beauzée-Luyssen authored
Now that we lazily start the discoverer worker, we can start its associated thread sooner. This will help when we start delegating the device refresh to the discoverer background thread
-
Hugo Beauzée-Luyssen authored
We don't need a full instance, all we care about is for the instance to handle tasks being enqueued This will allow us to automatically start the thread for the real instance, but not for unit tests
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
One locked version, one public unlocked version
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
So return void instead of a bool
-
Hugo Beauzée-Luyssen authored
This is a valid case on platforms that don't have a default device lister.
-
- Mar 24, 2020
-
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
One locked & one public, unlocked
-
- Mar 23, 2020
-
-
Soomin Lee authored
Since on iOS we use a specific DeviceLister, there is no need to build the macOS one.
-