FYI, I fixed the issue by configuring the dragging session using NSDraggingImageComponents for dragging items.

[quote='913330022, Etresoft, /thread/853644?answerId=913330022#913330022, /profile/Etresoft'] And what if it doesn't? [/quote] Then Apple should fix the issue. How do you suggest we do that? By reporting issues. That's what this forum is for. I'm not sure why you're here.

[quote='913292022, DTS Engineer, /thread/854240?answerId=913292022#913292022'] A table view subclass that overrides mouseDown: and calls super made both issues go away in every case I tried, and dragging still worked: [/quote] Wow. Would would have thought that overriding a method and only calling super would fix any bug? Thanks anyway. Though I would need to create subclasses for table views and outline views just to work around issues. I had already filed separate bug reports: FB25342199 and FB25342038

[quote='912698022, Etresoft, /thread/853644?answerId=912698022#912698022, /profile/Etresoft'] You can still use the legacy languages, targets, and platforms, but it will be your responsibility to understand how they work and test them on all supported OS versions. [/quote] A method that is not depecrated should work as intended. If developers don't hold Apple to basic standards, no one else will. NSSegmentedControl style is not deprecated, neither is ObjC.

OK, it appears that the new role property of NSSegmentedControl is what changes the appearance under macOS 27. Apple should make clear that the style property is ineffective.

[quote='912456022, Etresoft, /thread/853644?answerId=912456022#912456022, /profile/Etresoft'] What kind of style are you trying to change? And if it's a minimalistic app, why do you care? [/quote] I'm not sure what legacy platform you're referring to, but FYI, the minimanist app was just made to confirm the issue. It happens in my non-minimalist app. Anyhow, the fact that changing the style has no effect is a rather serious issue for anyone building an app with segmented controls.

Nevermind, I just realized I used the offStateImage rather than the image property for these menu items. The custom images indeed replace the default images, as expected.

It seems I didn't have a choice, so I renamed the class. I used @compatibility_alias, but I still needed to update the encoding and decoding of objects to maintain backward and forward compatibility . I guess I should have added prefixes to class names in the first place, but Apple may consider using more specific names for its (private) classes as well. "Trace" is very generic.

I meant Sequoia, not Sonoma.

Hi Chen. I too wonder why the binding does not bring back the object's attributes. Here a link to a simple project. https://upoitiers86-my.sharepoint.com/:u:/g/personal/jean_peccoud_univ-poitiers_fr/Eap9s3nnTfZGod0dfcDzhZ4BS6KVlJ-XCChuzsEhQyjpwA?e=YmSvqb To reproduce the issue, just click the "Swap folders" buttons, which reorders two Folder objects in an ordered to-many relationships, then saves the context (see swapFolderPositions: in AppDelegate.m). The name attributes of the folders are bound to two text fields, and you will see a name disappear when a folder is turned into a fault (a message is logged in the console when that happens, since I override willTurnIntoFault.

Update: the to-many ordered relationship doesn't have to point to the same entity for this issue to occur (in my example, the "parent" and "subfolders" can be different entities).

I see these messages in red in the Xcode console every time I click in a text field, even for a template app that only has one textfield. This is extremely annoying.

Of note, objects that turn into faults are those that has no pending changes, that is, those that were not inserted nor removed in/from the ordered collection. I can avoid the issue by making dummy changes to these objects, such that they don't turn into faults during the next save, but I'd like to understand the root cause. Maybe I don't know how to manage ordered collections properly. To insert an object, I use insertObject:inSubfoldersAtIndex and I don't modify other objects of the collection. Should I reorder all objects? The documentation says little about ordered to-many relationships.

I d'like to point out that this message is posted even with a template app that contains nothing else than a text field in the window's content view.

Hi. In case you're still around, I'd like to know what solution you've found to your problem. I too need to draw curves on a view that can be very wide, and a single CALayer cannot handle it (even if drawing is constrained to a small rectangle). My current solution is to use several contiguous CALayers, which is less than ideal...