Comments (2)

Rob SherrattSun, 5th Jul 2015 1:09pm

Related to this, there is a broader issue due to the current "synchronous" operation of the GBS library functions which locks the user's thread and causes 100% processor utilisation as well as providing no progress mechanism. In my opinion, the correct way to resolve this is for GB to implement a second set of operations which are "asynchronous". Please see the suggestion "Asynchronous support for thread locking GBS operations" which would also solve the "File Loading Progress" issue.

Jim GerrardMon, 15th Feb 2016 10:36am

I'm not convinced that complicating the API with a second set of calls is the best way to do this; a simple optional callback would work just fine. I gather this could be supported through a nullable Action parameter or similar.