Posts

Post not yet marked as solved
3 Replies
Same behaviour on 14.4.1. Not fixed.
Post not yet marked as solved
3 Replies
Same issue is observed with TIFF
Post not yet marked as solved
2 Replies
Xcode15 quicklook renders this as a one solid red color square on a P3 display, while the NSImageView displays it as a 2 different shades of red on a P3 display. let size = CGSize(width: 250, height: 250) let image = NSImage(size: size, flipped: false) { drawRect -> Bool in let rects = drawRect.divided(atDistance: drawRect.size.width/2, from: .minXEdge) NSColor(displayP3Red: 1.0, green: 0.0, blue: 0.0, alpha: 1.0).set ( ) NSBezierPath(rect: rects.slice).fill() NSColor(red: 1.0, green: 0.0, blue: 0.0, alpha: 1.0).set() NSBezierPath(rect: rects.remainder).fill() return true } imageView.image = image
Post not yet marked as solved
2 Replies
Documentation: If the pixel density or color space of the destination graphics context changes, though, the image representation throws away any caches and executes the block again to obtain a new version of the image. While the NSCustomImageRep is of Generic RGB colorspace it doesn't produce any backing cgImage. Backing cgImage is only created when needed based on destination cgContext. XCode quicklook (bug?): <<CGColorSpace 0x600001288180> (kCGColorSpaceICCBased; kCGColorSpaceModelRGB; sRGB IEC61966-2.1)> Directly asking for cgImage <<CGColorSpace 0x600002935aa0> (kCGColorSpaceICCBased; kCGColorSpaceModelRGB; Color LCD)> If you use the method to resize an image and assign it to NSImageView it will display it correctly. For this reason I wouldn't recommend using NSImage drawingHandler to resize image. The only way is to set custom context inside the drawing handler) The image representation copies the block and stores it for later use. This is a huge memory waste if it's a bitmap image rep. E.g. you have 5000x5000 image hanging around in memory.
Post marked as solved
14 Replies
I have the same problem - cannot generate promo codes. I also remember a day prior I accepted changes to the paid user agreement but it was flaky (it missed some steps). Nevertheless the status is I accepted it and got confirmation email. I have contacted support but so far they requested screenshots and steps to reproduce and sent it to technical team. Issue has been present since 29APR22
Post not yet marked as solved
5 Replies
I am currently facing this issue.
Post not yet marked as solved
25 Replies
Dear Apple. Either update following documentation (remove conformance to RFC2368) https://developer.apple.com/library/archive/featuredarticles/iPhoneURLScheme_Reference/MailLinks/MailLinks.html#//apple_ref/doc/uid/TP40007899-CH4-SW1 or fix this annoying bug.
Post not yet marked as solved
1 Replies
iOS14 + iOS15beta2 only recognizes nopass, WEP, WPA, WPA2 or WPA/WPA2 within QR code You can check it using Hopper at: /Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/System/Library/PrivateFrameworks/BarcodeSupport.framework
Post not yet marked as solved
25 Replies
This bug or "feature" is still present in iOS 14.7 beta 3.
Post not yet marked as solved
2 Replies
I wouldn't say as solution but I finally found what is causing it. On Big Sur I have slightly better crash report. I found out that there is a strong reference to a block + NSStepper. I was changing first responder somewhere in app (resign first responder and hide stepper). The fact that and there is a delayed mouseDown event delivered which is causing the crash. Still trying to dig more. Application Specific Information: objcmsgSend() selector name: sendActionsForEvents:view: 0   libobjc.A.dylib                   0x00007fff201b0d1d objcmsgSend + 29 1   com.apple.AppKit                  0x00007fff232bb0da NSControlTrackMouseblockinvoke.55 + 701 2   com.apple.AppKit                  0x00007fff22e3c922 -[NSDragEventTracker trackEvent:usingHandler:] + 1155 3   com.apple.AppKit                  0x00007fff22e3bdb5 NSControlTrackMouse + 1397 4   com.apple.AppKit                  0x00007fff22e3b818 -[NSCell trackMouse:inRect:ofView:untilMouseUp:] + 130 5   com.apple.AppKit                  0x00007fff2338cd23 -[NSStepperCell trackMouse:inRect:ofView:untilMouseUp:] + 162 6   com.apple.AppKit                  0x00007fff231667d5 -[NSDatePickerCell(NSTextFieldWithStepperDatePickerInternal) textFieldWithStepperTrackMouse:inRect:ofView:untilMouseUp:] + 390 7   com.apple.AppKit                  0x00007fff22e3aa18 -[NSControl mouseDown:] + 722 8   com.apple.AppKit                  0x00007fff23160fcc -[NSDatePicker mouseDown:] + 47 9   com.apple.AppKit                  0x00007fff22e38e98 -[NSWindow(NSEventRouting) handleMouseDownEvent:isDelayedEvent:] + 4956 10  com.apple.AppKit                  0x00007fff22da7848 -[NSWindow(NSEventRouting) reallySendEvent:isDelayedEvent:] + 2594 11  com.apple.AppKit                  0x00007fff22da6c0a -[NSWindow(NSEventRouting) sendEvent:] + 347 12  com.apple.AppKit                  0x00007fff22da4ff0 -[NSApplication(NSEvent) sendEvent:] + 352 13  com.apple.AppKit                  0x00007fff2307dd16 -[NSApplication _handleEvent:] + 65 14  com.apple.AppKit                  0x00007fff22c0d983 -[NSApplication run] + 623
Post not yet marked as solved
1 Replies
Found out it works out of the box in Catalina, not Mojave.