On Oct 06, 2016, at 12:05 PM, "J.E. Schotsman" wrote:
I have simple progress bar in a window that refuses to update normally.
I don't suppose it's as simple as progress.usesThreadedAnimation = YES;?
Sent from iCloud's ridiculous UI, so, sorry about the formatting
On Oct 6, 2016, at 13:26 , Jens Alfke wrote:
>
> Maybe someone’s come up with a generic proxy class that can be used to
> dispatch the notifications to the main thread?
Well, Apple has. NSProgress is a multi-purpose class, one of whose purposes is
to provide a thread-safe
> On Oct 6, 2016, at 11:36 AM, J.E. Schotsman wrote:
>
> CoreAnimation: warning, deleted thread with uncommitted CATransaction; set
> CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
Definitely looks like a threading problem — the view tried to use CA on the
Thank you very much. It's especially annoying when using
MultipeerConnectivity. I'll check it out.
On Thu, Oct 6, 2016 at 3:54 PM Quincey Morris <
quinceymor...@rivergatesoftware.com> wrote:
> On Oct 6, 2016, at 12:06 , Eric E. Dolecki wrote:
>
>
> Is there a way to turn
On Oct 6, 2016, at 12:06 , Eric E. Dolecki wrote:
>
> Is there a way to turn this off for Xcode 8.0?
I believe this (the unwanted messages) is resolved in Xcode 8.1 beta 2,
although I haven’t verified this personally.
___
You can set the environment variable OS_ACTIVITY_MODE=disable on the
scheme's Run page in the arguments tab. In the simulator that stops all the
stuff from the system and NSLog in your app still works. Unfortunately on
device this also suppresses NSLogs from your own code.
On 6 October 2016 at
When I build to device for iOS - I get the expected logging. If I build to
an iOS Simulated device, I am getting a bunch of logging to the console.
2016-10-06 15:02:35.138443 testBars[59267:10948290] subsystem:
com.apple.UIKit, category: HIDEventFiltered, enable_level: 0,
persist_level: 0,
On Oct 6, 2016, at 1:36 PM, J.E. Schotsman wrote:
>
>
>> On 06 Oct 2016, at 19:43, Jens Alfke wrote:
>>
>> That means that KVO is going to call the view’s observeChange method on your
>> background thread, not on the main thread. Which I believe
> On 06 Oct 2016, at 19:43, Jens Alfke wrote:
>
> That means that KVO is going to call the view’s observeChange method on your
> background thread, not on the main thread. Which I believe qualifies as
> “updating the UI from a background thread”, which is illegal. It may
> On Oct 6, 2016, at 10:04 AM, J.E. Schotsman wrote:
>
> Its doubleValue is bound to the progress value of my ProgressController
> class, so is “animating" and “indeterminate".
> ...
> The progress value and other values are changed on a background thread.
That means that
Hello,
I have simple progress bar in a window that refuses to update normally.
Its doubleValue is bound to the progress value of my ProgressController class,
so is “animating" and “indeterminate".
If I print the values during a job everything is correct, but the progress bar
won’t update. It
Apple has historically suggested using ICU for functionality that it's
higher-level frameworks don't provide, and it's easy enough to get at all
needed functionality through its C functions without using C++ (at least what I
care about). Since most significant changes only occur in the data
On 6 Oct 2016, at 10:43, dangerwillrobinsondan...@gmail.com wrote:
>
> Pretty sure the reason is a simple one.
> If you look at the history of open source in the OS on the Apple open source
> page, you'll notice they pretty much bump the ICU version they use annually.
> Although unlikely, ICU
Pretty sure the reason is a simple one.
If you look at the history of open source in the OS on the Apple open source
page, you'll notice they pretty much bump the ICU version they use annually.
Although unlikely, ICU might change in ways that breaks your app. They don't
want to support ICU
My experience has been that last year (iOS 9 and OS X 10.11) Apple made ICU a
private framework worthy of rejection from its App Store if you used its APIs
directly. I encountered this because like in years past when Apple did not
provide ICU through a higher-level framework, we were encouraged
The Icu stuff (57.1) is included in macOS 12.
There is:
/usr/lib/libicucore.A.dylib
and Xcode has:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/lib/libicucore.tbd
But I cannot find the headers.
Gerriet.
16 matches
Mail list logo