Skip to content
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

Made some parts of DeleteObjectPlugin public #26

Merged
merged 3 commits into from
Apr 13, 2015
Merged

Made some parts of DeleteObjectPlugin public #26

merged 3 commits into from
Apr 13, 2015

Conversation

AnsisMalins
Copy link
Contributor

I've made DeleteXmlComboBox and GetFileNameForObject public so other plugins can access this information. It is necessary for my Perforce plugin so it can remove the XML file from Perforce correctly.

@vchelaru
Copy link
Owner

I think this is okay, but before I merge I just wanted to ask - what properties on the combo box do you need access to? Does it make sense to simply expose the properties off of the combo box that are needed rather than the entire combo box?

If a lot of the properties are needed, or if you envision other plugins needing access to the entire combo box let me know and I'll merge.

@AnsisMalins
Copy link
Contributor Author

You are right. I do not foresee anyone needing more than the Checked property, so I changed the code accordingly.

vchelaru added a commit that referenced this pull request Apr 13, 2015
Made some parts of DeleteObjectPlugin public
@vchelaru vchelaru merged commit 1107aca into vchelaru:master Apr 13, 2015
vchelaru added a commit that referenced this pull request Jul 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants