That's the missing little piece...

Ah, yes. This is the second time I fell into the same pit. The last time was years ago... Just hate this design by Apple, why a tight loop cannot have ARC automatically?

I am aware of Regex, but it's not the same as direct file pattern globbing. And for my case, I need to support older macOS versions (11+), but Regex is only available on macOS 13+.

You don't need to start over again. What I meant was remove the file by reference from the project and add it back again. This should work.

Same problem here, macOS Sonoma 14.2.1.

Ah, I didn't notice there is this builtin property!

I don't want to define it in IB. I want to dynamically add rows and define width and height.

It seems that there is no builtin support for this purpose. I will write my own logics, anyway it's not difficult at all.

My need is simple - search in some directories for certain types of files and process the result list.

Well yes, I think that is the reason. I did some hacking and I have been running Xcode 14.3.1 on macOS 12.7 for half a year.

Actually I think it's waste of both performance and space. I am aware that when I get a 'copy' of an array in Swift as long as I do not modify it, I actually get a special reference of the array. But when I modify it, the copy-on-write mechanism kicks in and I now get a copy. Later on, I have to replace the original array with the modified array. That's totally against my experience on other languages and systems. But, I know I cannot change anything.

Thanks for your effort and replies. Sorry I cannot make your reply as answer because my question does not have an answer.

This is just the situation where people feel helpless. We can't do anything to it. It's just by design. Another pain for me in Swift is that it does not explicitly support namespace. Apple is genius but sometimes they just fell asleep when making decisions.

Yeah, that's fantastic! I seldom use the symbol navigator and when I tried to use it it demonstrated problems.

It's my fault. I did not read the article thoroughly. The article has example code which I did not observe.