-
Notifications
You must be signed in to change notification settings - Fork 82
add PersistLoadWatermark #482
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -36,6 +36,7 @@ namespace Exchange { | |||||
| virtual bool ShowWatermark(const bool show) = 0; | ||||||
| virtual bool CreateWatermark(uint32_t id, uint32_t zorder) = 0; | ||||||
| virtual bool UpdateWatermark(uint32_t id, uint32_t key, uint32_t size) = 0; | ||||||
| virtual bool PersistLoadWatermark(uint32_t id) = 0; | ||||||
|
||||||
| virtual bool PersistLoadWatermark(uint32_t id) = 0; | |
| virtual bool LoadPersistedWatermark(uint32_t id) = 0; |
Copilot
AI
Jan 21, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding a new method to an existing interface is a breaking change for the API. This change will break binary compatibility because any existing implementations of the IWatermark interface will not have this method implemented, causing vtable mismatches. Consider versioning the interface (e.g., IWatermark2) or using a COM versioning strategy to maintain backward compatibility with existing implementations.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The method lacks documentation explaining its purpose, parameters, and return value semantics. Since this is an interface method being added to support persistent watermark features, it should include documentation that explains: what "persist and load" means in this context, what the 'id' parameter represents, and what the boolean return value indicates (success/failure conditions). This is especially important for interface methods that will be implemented by external parties.