IDK if I agree - I don't see binary as necessary numeric. Binary is just ... anything. Could be ASCII. Could be Unicode. Could be executable code. Thus to say it's signed is kind of strange and implies you're using it like a number. Doesn't have to be, IMPOV.

@ThunderFrame just to make sure you don't get lost in the sticks --- is this something that must be 100% completed just to deliver? Can't you deliver what you can parse and enhance? The bug reports that comes may in fact help your effort, maybe? Just ideas.

> FWIW we should respect the font-size coming from OS customizations. As such we shouldn't expose that setting directly as a Rubberduck setting, but instead grab that information from our host app (or even the OS)

> FWIW we should respect the font-size coming from OS customizations. As such we shouldn't expose that setting directly as a Rubberduck setting, but instead grab that information from our host app (or even the OS)

> And grabbing that information from host app (VBA editor) is already implemented? Is it OK, that my VBA (Excel) editor appears with all controls in 10px, but Rubberduck controls are 12px height at the same time?

I have this very recurrent pattern at my VBA macros, where I have to ask the user to give me certain information that will be necessary for the processes to come. Most often for example, I need him to give me some workbooks and maybe a date.
So I often declare a Type whose elements are all the w...

How can i improve the following working code?
I would like to be able to join the "Select Case True" with the normal "Select Case" conditions
With w.Sheets("test")
For i = n To 10 Step -1
Select Case .Cells(i, 1)
Case 1,2,3,4
.Cells(i, 1).EntireRow.Delet...

> Asynchronous/ non-blocking parse cannot guarantee that there aren't any code changes made; parsing before the dialog is shown but without blocking the editor / UI thread wouldn't ensure we're working with the most up-to-date code.

Also the canexecute logic for all commands needs to change to a default `return true` if every command will trigger a blocking parse.

> What about an option within the RD menu that allows the user to disable the blocking dialog if they so choose? That would allow for regular users to get the blocking message reminding them to re-parse before using commands, but a power user to disable the warning since they will be aware of the risks. From a UX standpoint it would be a compromise that prevents a regression, but adds additional protection for users who want/need it.

> I would like to propose a somewhat different approach. We could display a dialog before trying to execute a refactoring command indicating that a reparse is required, provided the loaded projects are dirty at that point. We could also put a _reparse now_ button on the dialog.

One reason why I prefer this to an automatic parse is that, in the eyes of RD, the user might have selected something to refactor that is entirly different from what he intended; the selection that RD sees correspond

@Duga FWIW that would be a good opportunity to refactor the creation logic of MVP/MVVM for all other dialogs, as well. I think that dialogs only really need one presenter and maybe only one dialog if the elementhost can be altered runtime.

How can i improve the following working code?
I would like to be able to join the "Select Case True" with the normal "Select Case" conditions
With w.Sheets("test")
For i = n To 10 Step -1
Select Case .Cells(i, 1)
Case 10111,23232,98076,41324
.Cells(i, 1)...

> That is because I didn't express what I meant fully.... That functionality is currently **not** implemented. That is why this is labeled [enhancement] and not [bug]. If it were already implemented, but there was a difference between the VBE and Rubberduck, that'd be a bug.

Do note that RD UI is not striving to look like the VBE, quite the opposite. We should respect accessibility and OS-Wide definitions though, and control / font size is one of those...