Skip to main content
Stack Overflow
  1. About
  2. For Teams

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Draft saved
Draft discarded
Cancel
4
  • 1
    While I like the idea of "how can I do this more efficiently", your question will no doubt only spur opinionated responses. Eg: You are mixing presentation, business and database concerns into a highly coupled and fragile design. I’d recommend revising your question to spell out your objectives more clearly and highlight specific problems you are experiencing so that folks can provide a clear non-subjective answer. Commented Feb 13, 2025 at 20:08
  • Property change notifications originate in the affected object's "properties"; not in the "pipeline". Then you can start thinking in terms of generics and interfaces. Commented Feb 13, 2025 at 20:45
  • @GerrySchmitz I have a listbox with db records (items) represented. If I change one of these from the UI (CRUD operations), it must propagate to the DB. I need INotifyCollectionChanged and INotifyPropertyChanged. Commented Feb 13, 2025 at 21:07
  • I didn't say you didn't need them; yours are just not localized and is causing redundant code. And "backups" can be accomplished via cloning; a generic method. Commented Feb 13, 2025 at 21:18

lang-cs

AltStyle によって変換されたページ (->オリジナル) /