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

Custom method for saving and restoring QAT items #276

Closed
floele-ww opened this issue Feb 23, 2016 · 13 comments
Closed

Custom method for saving and restoring QAT items #276

floele-ww opened this issue Feb 23, 2016 · 13 comments
Assignees
Milestone

Comments

@floele-ww
Copy link
Contributor

Our application needs to store QAT items within an XML file. Currently the ribbon does not provide access to these items, however. My minimally invasive method to achieve my goal so far was changing

// Currently added in QAT items
private readonly Dictionary<UIElement, UIElement> quickAccessElements = new Dictionary<UIElement, UIElement>();

to

// Currently added in QAT items
protected readonly Dictionary<UIElement, UIElement> quickAccessElements = new Dictionary<UIElement, UIElement>();

and then implement the required functionality in a derived ribbon class. An officially supported way to do this would be great.

@batzen batzen added this to the 4.1.0 milestone Feb 24, 2016
@batzen batzen modified the milestones: 5.0.0, 4.1.0 Mar 19, 2016
@batzen batzen self-assigned this Jul 9, 2016
@batzen
Copy link
Member

batzen commented Jul 24, 2016

@floele-sp Could you have a look if my implementation fits your needs?

@floele-ww
Copy link
Contributor Author

@batzen Thanks, the GetQuickAccessElements()-method should be sufficient.

@batzen
Copy link
Member

batzen commented Aug 2, 2016

@floele-sp So the implementation fits your needs, or not? ;-)

@floele-ww
Copy link
Contributor Author

@batzen I cannot currently upgrade the Fluent library so I didn't use it yet, but in theory it fits my needs,

@batzen
Copy link
Member

batzen commented Aug 4, 2016

@floele-sp Ok, then please post back as soon as you got the chance to verify my implementation.

@batzen
Copy link
Member

batzen commented Sep 16, 2016

@floele-sp Any news?

@floele-ww
Copy link
Contributor Author

@batzen Sorry, but no. We'll need a few more weeks before we can upgrade, but I'll let you know. I probably need to report a few issues I noticed (if still present) anyway.

@batzen
Copy link
Member

batzen commented Sep 17, 2016

I don't like to pressure you, but this is the last open issue that's preventing version 5.0 from being released ;-)
Would be nice if you could have a look or just tell me to close this and if you encounter any problems open a new issue.

@batzen
Copy link
Member

batzen commented Sep 19, 2016

It's not the last open issue anymore. Moved some issues from 6.0 to 5.0. ;-)

@floele-ww
Copy link
Contributor Author

I don't really want to stop you releasing 5.0, so feel free to close it.
I would certainly love trying the new version, but since we still haven't moved to .NET 4.5 (quite sad) I cannot compile the current version of Fluent for a test run.

@batzen
Copy link
Member

batzen commented Sep 19, 2016

Fluent still works with .net 4.0. You just need VS 2015 to compile. Have a look at the appveyor build, you can grab the compiled binaries from there. Will release the first official preview for v5 to nuget someday this week.

@floele-ww
Copy link
Contributor Author

Oh I should probably have used the 4.0.csproj ;)

Alright, looks like the new property is working fine, thanks.

@batzen
Copy link
Member

batzen commented Sep 19, 2016

Thanks for testing.

@batzen batzen closed this as completed Sep 19, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants