Benjamin Herzog
Benjamin Herzog
Hm, the problem is the change in the behavior of implicitly unwrapped optionals in Swift 4 and that JavaScriptCore doesn't offer nullability flags :/ I'll update the project to Swift...
I just pushed the update in dff687b7e70b360e13bf5237137070c0407ed59f. If you want - please go forward and fix the completer :) Had to disable it temporarily because it didn't work with my...
Thanks, that would be a great addition! Also sharing could be added in the future :)
Schwalbe is transpiled to Swift, so this should already be possible ;)
True, but there are a lot of more important features that should be implemented before ;)
> I'm seeing numbers that i'm having a hard time trusting with the flag enabled. ran the benchmark 3 times and getting the same results though. You should be able...
Crashed: com.apple.main-thread EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000000043000002 Crashed: com.apple.main-thread 0 libobjc.A.dylib 0x19860dbc8 objc_msgSend + 8 1 CoreFoundation 0x1839f3580 -[__NSCFTimer fire] + 120 This is happening on every device, every OS I tried...
Oh yeah, sorry, forgot to answer. I'll create a bugticket at Apple.
@scisci we are using an older version of SwiftyTimer which doesn't have the issues.
We have the same problem. What I found out: the control gets moved up for 60pts, which is the exact height of the refresh control itself.