@Inarion yep, fonts are programs, so virus threats. it would be nice to bundle some open source fonts with RD, so users get a great IDE and some fonts to make it look even better, without any admin rights required.
@ThunderFrame I guess it's similar to embedding them in .pdf files? These files can then be properly printed even from machines that don't have that specific font installed.
@ThunderFrame And the code is where the font will matter the most (as far as I'm concerned)
@Inarion IIRC Bloomberg doesn't install any fonts, but instead uses font resources. Printing is just sending the postscript to the printer, so yes, you can print the fonts from that program... you just can't use those fonts in other programs, like you can with an installed font
So, I'll be recording a podcast interview (in French) about Rubberduck and the VBE with Montreal MVPs Mario Cardinal and Guy Barrette, on the evening of July 2nd.
@ThunderFrame Not sure, if you're kidding. Is that a thing? I've not used inspections very extensively, but I certainly don't know of any grumpy-face that is triggered by my bad code.
> Hi. I really like the Indenting function, but there's a feature I'd like. > > I'd like to set my own text I want indented. For instance, I often indent the code within the "On Error" block like this: > > On Error Resume Next > ActiveSheet.ShowAllData > On Error GoTo 0 > > > In Rubberduck I'd like to go to a field called "Indent Lines Beginning With:" and add "On Error Resume Next", then go to a field called "Outden
> I think @retailcoder has been itching to treat OERN as an indented block. It seems this is the only "block" that needs to be added. It would certainly be easier to just add this case, rather than having user-specified indentation syntax rules.
One additional downside to bang notation: You can't store the field names in variables. Or rather: You can't use bang notation when you want to store field names in variables. (That is, unless I'm missing something.)
The autofix for "Move declaration to smaller scope" breaks in certain scenarios.
It doesn't seem to like one-line if statements. If the first occurence of a too broadly scoped variable is as such If ImGoingToBreak = vbNullString Then ImGoingToBreak = "Don't autofix me, please!" then the autofix will move the declaration like this:
@Inarion does that compile? I've always been under the impression that despite Dim statements not being executable, the compiler still requires declarations to precede first use
> With AutoComplete having a setting (enabled by default) to treat OERN...OEG0 as a block (and thus applying default indent accordingly), the AC's indenting would be undone by Smart Indenter - we do need an indenter setting for that, and AC needs to use indenter settings to determine whether or not to indent OERN...OEG0 "block" bodies.
While they would definitely be flexible, I don't think allowing user-defined blocks in indenter settings would be useful though. I'd prefer adjusting the inden
Just thinking - for the initial VB6 release, would it be worth popping up a messagebox on launch if VB6 host detected, saying "warning - experimental feature. Please ensure that any critical code is backed up before proceeding"? (or similar)
> VB6 is milestoned for v2.3, however it will likely be a while before it's decently stable. In the interim we should pop a message box on launch when VB6 host is detected, warning that VB6 is experimental and to ensure that any critical code used with it is adequately backed up first (exact wording TBD)
Funny thing is, when I inserted the code markdown, the form broke. My cursor disappeared and continued to be invisible. (I was still able to enter text, I just had to guess the cursor position.) :D
TBH, for me personally, I'd love that the Move Closer to Usage factored in the blocks, not just the one-line If statement.
'Meh
Do Until .EOF
Dim Result As Boolean
If Result = .Fields("Something").Value Then
Exit Do
End If
.MoveNext
Loop
'Better
Dim Result As Boolean
Do Until .EOF
If Result = .Fields("Something").Value Then
Exit Do
End If
.MoveNext
Loop
> If I used RD in VB6 I'd want to be able to dismiss that warning once and for all after seeing it once... a `MessageBox` can't do that.
Can we make an `IMessageBox` implementation that brings up our own custom WinForms dialog? We could amend the returned enum value with a flag that contains the "don't show this message again" state... and then we'd need to figure out a way to make the interface expose a method for that, which the standard/current implementation could just ignore, forwarding
> From [Nikita B's Code Review](https://codereview.stackexchange.com/a/196810/23788):
> I double-checked that on my current R# version (which is a bit out of date), and R# **removes both braces if you hit backspace when cursor is in the middle. But it only removes last brace, if you hit delete.** Which is probably what I do nowadays, when I want a single opening brace. I type subconsciously, so its hard to tell for sure. :)
So given `"|"` and <kbd>DEL</kbd>, we want to end up with `"|`. An
> Good point, my only concern would be that if we implement "do not show again" in the general case, there should really be a way of resetting any flags set in the past (probably sits in settings somewhere).
Maybe not essential for this, just thinking it forward.
hmm, maybe I need to assign the WPF after I obtain the size. I may try that.
but i'm apparently reading from the elementhost, not from the WPF (the usercontrol).
ah yes I remember now - WPF and WinForms uses completely different units of measurement for their sizing, so I can't just read WPF's size and apply to Winform's stuff.
so I have to first assign the WPF to the elementhost, then try to infer the preferred size. But I've found that to be.... wonky.
First, I didn't find any answer so far. The article here on this site does not answer my question:
Converter of System.Drawing.Point' to 'System.Windows.Point
In the above article, one suggests to convert like this:
//convert
System.Drawing.Point dp = …;
return new System.Windows....
what I'd like is to abstract that min width/height from the ideal size that we specify in the WPF XAML code. IOW, we should be able to work exclusively in the WPF designer and never ever need to look at a WF designer.
IMO dialogs shouldn't be resizeable though. they should be sized to look right with how they're designed. although... with "preview" boxes I can see resizing being useful.
TBH refactorings need a "common dialog" featuring a preview pane and a content container, with the individual refactoring UIs being UserControls injected there
i got the containing and positioning the way I want it. I only want to get sizing completely automated - that would eliminate the need to provide a implementation for some refactorings that don't need it and allow them to use the DialogBase directly.
well there's also the caption but that can be solved, I think.
[rubberduck-vba/Rubberduck]mansellan pushed commit 91364e28 to next: Refactored IModuleExporter to a higher level ISourceCodeHandler abstraction, with concrete implementations for VBA and VB6
This is a part of the code for the almighty bot @Duga (That's me!).
Every evening, 15 minutes before "RELOAD" (00:00 UTC), I post the reputation differences for some Code Review users.
Example output is:
Mat's Mug vs. Simon Forsberg: 2728 diff. Year: +3618. Quarter: +885. Month: +648. Week:...
> Good catch, @Vogel612 ; it does not persist with explicit values given: ``` Public Enum LogLevel TraceLevel = 0 DebugLevel = 1 InfoLevel = 2 WarnLevel = 3 ErrorLevel = 4 FatalLevel = 5 End Enum ``` This does not trigger the inspection. I guess that narrows down the list of possible culprits?
> The problem here is that a sameLineStatement currently is a blockStmt but should be a mainBlockStmt. (Statement labels can only appear at the start of a line.)
e.g. With foo.GetSo with intellisense showing GetSomething, either tab/enter, and I end up with just With foo.GetSo ... End With, not With foo.GetSomething....End With
First, I didn't find any answer so far. The article here on this site does not answer my question:
Converter of System.Drawing.Point' to 'System.Windows.Point
In the above article, one suggests to convert like this:
//convert
System.Drawing.Point dp = …;
return new System.Windows....
This is a part of the code for the almighty bot @Duga (That's me!).
Every evening, 15 minutes before "RELOAD" (00:00 UTC), I post the reputation differences for some Code Review users.
Example output is:
Mat's Mug vs. Simon Forsberg: 2728 diff. Year: +3618. Quarter: +885. Month: +648. Week:...
VBA Rubberducking
VBA Rubberducking