[GH-ISSUE #397] Dynamic Resizable Header View #392

New issue

Open

opened 2026-03-03 19:18:10 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 19:18:10 +03:00

Owner

Originally created by @NghiaTranUIT on GitHub (Feb 12, 2020).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/397

Originally assigned to: @NghiaTranUIT on GitHub.

🐶 Brief

Currently we're using multiple-line NSTextField in Table View Row and add bundle of code to support dynamic resize if the text is large

We discover that there is an elegant way to achieve the same by using NSTextView without NSScrollView. Let refactor it

👑 Criteria

Remove all old size calculation and NSTextField in Header
Use NSTextView
Make sure the size is dynamically resizing depend on the content of text (via width and height)

Originally created by @NghiaTranUIT on GitHub (Feb 12, 2020). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/397 Originally assigned to: @NghiaTranUIT on GitHub. ## 🐶 Brief Currently we're using multiple-line NSTextField in Table View Row and add bundle of code to support dynamic resize if the text is large <img width="1638" alt="Screen_Shot_2020-02-12_at_21_23_32" src="https://user-images.githubusercontent.com/5878421/74343658-fdd61b80-4ddd-11ea-90de-d1d9ff675261.png"> We discover that there is an elegant way to achieve the same by using NSTextView without NSScrollView. Let refactor it ## 👑 Criteria - [ ] Remove all old size calculation and NSTextField in Header - [ ] Use NSTextView - [ ] Make sure the size is dynamically resizing depend on the content of text (via width and height)

kerem added the

enhancement

✅ Done

labels

2026-03-03 19:18:10 +03:00

kerem commented

2026-03-03 19:18:11 +03:00

Author

Owner

@NghiaTranUIT commented on GitHub (Feb 13, 2020):

Put it back to the Backlog since this approach doesn't work well if we have two Column (Header and Value) since we have to computer which content is bigger to expand or shrink.

Current solution work not bad, but it fits 90%.

@NghiaTranUIT commented on GitHub (Feb 13, 2020): Put it back to the Backlog since this approach doesn't work well if we have two Column (Header and Value) since we have to computer which content is bigger to expand or shrink. Current solution work not bad, but it fits 90%.