Still hooked on Windows, I refactored the hook into a number of interfaces - I started with defining an IHook that can be attached, detached, exposes a property that tells whether a hook is attached or not, and raises an event when the hook receives a message:
public interface IHook
{
event ...
> When the SmartIndenter branch gets merged into [next], Rubberduck will be supporting hotkeys.
Let's determine what hotkeys will map to which features by default (not all of these are currently implemented, and not all of these might need a hotkey):
- Display Code Explorer toolwindow - Display ToDo Explorer toolwindow - Display the Test Explorer - Display the Source Control panel - Run code inspections - Run all unit tests - Refactor / rename - Refactor / extract method -
> @ckuhn203 I think it is possible - the "step into" and "step through" functionalities have menu items that can probably be invoked programmatically. I suggest we leave this issue closed and take it to the broader #866 about hotkeys in general.
> It's a little cumbersome, but it appears that Ctrl + Shift + [Key] combinations aren't used. (At least, they're not used often.) So, if we can use those, I recommend we go with whatever R# uses, only Ctrl + Shift instead of Ctrl.
> @ckuhn203 that would be the best compromise. Smart Indenter uses Ctrl+P and Ctrl+M to indent current procedure and current module, respectively. I'd change that to Ctrl+Shift+I,P and Ctrl+Shift+I,M, respectively. What do you think?
> Coming from Java-IDEs these commands are rather intuitive. I'm more used to Alt + Shift keystrokes, but that seems to be a Java thing.
re: code inspections: I'd say that running inspections whenever the parser is idle makes for a cleaner UX, but you should be able to "manually" run them anyways. This would obviously have to wait for the parser to get the necessary results ready, but you'd get a Progress indicator with that then ... :+1: ?
This is a simple question I hope. I learned about IIf today and want to implement it in some cases to save a few lines.
IIF(isnumeric(inputs), resume next, call notnum)
This is in red meaning there is a syntax error, how fix this? I have scanned MSDN article on this so I am not being lazy here.
> @ckuhn203 well R# has Ctrl+T for *go to anything*.. and I'm trying real hard, I can't seem to find a consistency there. Some are Ctrl+key, some are Ctrl+Shit+key, some are Alt+Shit+key, and then we even got some Ctrl+Shift+Alt+key in there... I completely agree with increasing the level of consistency.
How about a "scheme"?
- **Ctrl+Shift+{key}** for all 2-step hotkeys - **Alt+Shift+{key}** for all 1-step hotkeys
That'll take some thinking to get right, but then it will be much eas
> If you can rework the hotkeys, this suggests another possibility. When stepping through code, I am always falling into commonly called procedures that have been run millions of times and which do not need checking. Some examples include AddTrailingSlash(), StripSlash(), and particularly PushStack and PopStack, which generate a call stack for error reporting. I wish there was a skip over list for these functions so that I do not find myself in them. Pushstack is the first line of a called p
> @AndrewM- that's a whole can of worms there! I don't think it's impossible (although I'd rather use some '@DebugStepOver annotation at the top of such a procedure), but we're talking about something that might possibly become something to think about in 3, maybe 4 releases. Mental note taken though :wink:
Still hooked on Windows, I refactored the hook into a number of interfaces - I started with defining an IHook that can be attached, detached, exposes a property that tells whether a hook is attached or not, and raises an event when the hook receives a message:
public interface IHook
{
event ...
This is a simple question I hope. I learned about IIf today and want to implement it in some cases to save a few lines.
IIF(isnumeric(inputs), resume next, call notnum)
This is in red meaning there is a syntax error, how fix this? I have scanned MSDN article on this so I am not being lazy here.
VBA Rubberducking
VBA Rubberducking