Looks awesome! I agree with @Vogel612, "priority" == "index" and doesn't need to even be explicitly in the UI - just have them sorted in the order they appear in the settings, and allow move up / move down and perhaps even drag-and-drop reordering
I don't think I'm dull, but I would probably have a hard time figuring that out.
@Mat'sMug It would actually be much more busy than what I currently have.
Now I have to have a one-column datagrid if I want to keep the current look, or else implement a listbox, which doesn't support a header, I don't think.
Then, I have to add more buttons, rather than just the existing combobox that already works.
Sure. I'll add another pixel or two between them too.
After this, I'm going to do the Inspections view. Can you make a list of what I should include in the unit test view, like datatypes being set, and stuff?
@Hosch250 given the new left panel, I think a GroupingGrid is in order; group by InspectionType (i.e. "Code quality issues", etc. - they have localized strings now), and display the Name and have a dropdown for the Severity.. and perhaps a tooltip on each item to show the meta-content, now that we have that
@Mat'sMug You know, sometimes an example is worth a thousand words. Do you think we should show before/after code (maybe in a GIF?) of the inspections and refactorings somewhere?
After ages of searching, I found a surprisingly simple way to do this that's cleaner than the Got/LostFocus approach posted earlier:
<DataGrid.Resources>
<SolidColorBrush x:Key="{x:Static SystemColors.InactiveSelectionHighlightBrushKey}" Color="DarkGray"/>
</DataGrid.Resources>
This just s...
> I second this idea for a book myself in a do it yourself fashion however need to put forward some concerns.
Firstly, this topic being rubberduck is going to evolve over time, per version release. Does re-printing or additional footnotes matter if a bug is found in the release and how could the user read it need to find patches?
Might be practical in the long run to have an ability to just print the "updated" wiki like what Wikipedia offers as a functionality for printing to create a
> @PeterMTaylor I think we would need to limit it to being an e-book, and I agree that there would need to be a section on known bugs. However, I do not think we need to track which features are in which release as the users can just download the latest version.
> @Hosch250 Sounds good for users to seek and find when required. I'm glad the book boundaries is being defined at this point in time and the preferred format.
[rubberduck-vba/Rubberduck]autoboosh pushed commit 0a7a9980 to next: at runtime WPF localization with resx files using the "WPF Localization Using RESX Files" library (partially resolves #1014)
CorelDraw Works, including testing. HostApplication resolves more reliably for Excel and Word.
Added a ctor override to HostApplication Base, that gets the host application via vbe.vbProject.vbComponent.Properties. That allows the vbe to reliably find the real host, if there is more than 1 copy of a host application open.
[retailcoder/Rubberduck]autoboosh pushed commit 0a7a9980 to next: at runtime WPF localization with resx files using the "WPF Localization Using RESX Files" library (partially resolves #1014)
[Hosch250/Rubberduck]autoboosh pushed commit 0a7a9980 to BugBlipper: at runtime WPF localization with resx files using the "WPF Localization Using RESX Files" library (partially resolves #1014)
Oh, and you will need to update the InspectionsUI.resx and a couple other .resx's too. We are working on separating them because it was becoming difficult to manage.
If you want to wait a couple weeks, I will finish that after the Settings window.
Vogel612 has written a little "translation helper" tool in Java, to help comparing different versions of a .resx - e.g. you get to compare the English and Japanese files, the tool shows if any keys are missing, for example
I haven't tried it, but he's been using it extensively to create the German translations, seems to work fine :)
then yeah, you can load the RubberduckUI.resx and RubberduckUI.ja.resx files into the tool and it's going to make it much easier than manually editing the xml
when you're ready, make a pull request and we'll merge it into the main repository
and don't hesitate to ask if you have any questions, too - even if nobody's here in this room, we'll ping/reply back whenever we can (I mean, it's 1:10AM here)
the scope/goal of Rubberduck is to enhance the VBE by giving it features that you'll find in "real IDE's" like Visual Studio or Eclipse. Refactorings, unit testing, source control integration, code inspections, navigation tools, ...things like that.
After ages of searching, I found a surprisingly simple way to do this that's cleaner than the Got/LostFocus approach posted earlier:
<DataGrid.Resources>
<SolidColorBrush x:Key="{x:Static SystemColors.InactiveSelectionHighlightBrushKey}" Color="DarkGray"/>
</DataGrid.Resources>
This just s...
VBA Rubberducking
VBA Rubberducking