F6 Blocking

6 posts, 1 answers
  1. robertw102
    robertw102 avatar
    265 posts
    Member since:
    Jul 2007

    Posted 20 Jan 2010 Link to this post

    I've noticed that with JustCode installed that when I press F6 to build my project it does not perform the action. It's almost like JustCode is blocking it.

    It's not a big problem, since I can build the project using CTRL + SHIFT + B, but I just wanted to know if this is something that JustCode is doing.

    It does this on both versions of Visual Studio, 2005 and 2008.

    Thanks.
  2. Answer
    Chris
    Admin
    Chris avatar
    221 posts

    Posted 20 Jan 2010 Link to this post

    Hello robertw102,
    Sorry for the inconvenience. Currently we take this shortcut for the Move Type To Namespace command.
    You can go to: Tools -> Options -> Environment -> Keyboard, then type "JustCode.Move" to find the command, then from the "Shortcuts for selected commands" select the "F6" shortcut and press the Remove button.
    We'll consider some other shortcut for this command.

    All the best,
    Chris
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
  3. DevCraft banner
  4. Dessie Lunsford
    Dessie Lunsford avatar
    10 posts
    Member since:
    Oct 2004

    Posted 22 Jan 2010 Link to this post

    Thanks for the workaround...I just installed "JustCode" beta and had the same issue with F6, but have fixed it as per your instruction.

    I would like to add that one thing you need to consider when building any sort of add-in to an existing piece of software is that you dont want to interfere with normal operations.  The Add-in should provide additional functionality and tools without causing any negative impact on standard operations built into the actual software itself.  Although the F6 issue is not a "huge" deal, it does cause the user to have to either use an alternative keyboard shortcut (multiple keys instead of the standard single-key default), or use the menu option to perform the build.
    I like what I see so far, but as a long time user of Visual Studio, the last thing I want to have to do is go through a bunch of configuration steps just to get the environment back to the standard I've been accustomed to for years, so I'd encourage you to make sure that "JustCode" doesn't modify things...too much :)

    Thanks,

    Dessie
  5. Chris
    Admin
    Chris avatar
    221 posts

    Posted 27 Jan 2010 Link to this post

    Hello Dessie,

    You're absolutely right, we'll need to fix this. Unfortunately we can never be sure whether the shortcuts we've chosen have no conflicts with the custom shortcuts on the client machine because we have to put some predefined shortcuts for our commands.
    That's why we tried to do everything possible to not override some important default VS shortcuts. For example the F6 shortcut overrides the VS Window.NextSplitPane command which I doubt someone is using heavily.

    What we can do is to react to customers' complaints about taking their favorite shortcut and choose some other shortcut for our command (and that's what we'll do for the F6 shortcut).

    So thanks a lot for the feedback and should you have some other concerns or suggestions please don't hesitate to contact us.

    Regards,
    Chris
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
  6. Steve
    Steve avatar
    1 posts
    Member since:
    Jan 2008

    Posted 28 Jan 2010 Link to this post

    Regarding the way JustCode takes ownership of various keyboard sequences:

    A while back I encountered a nice way to resolve conflicts like this.  After installation (I think it  was CodeRush, but it might have been Resharper), the first time I tried a keyboard shortcut with an existing mapping, a dialog was displayed that showed the "original" mapping, along with the new product's potential mapping.  I could then choose to "persist" either mapping.

    Just a thought.

    Thanks,

    s.s.
  7. Chris
    Admin
    Chris avatar
    221 posts

    Posted 29 Jan 2010 Link to this post

    Hi Steve,
    That's a really nice workaround for the problem, I like it. I'm adding this to our product backlog for future implementation.

    All the best,
    Chris
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
Back to Top
DevCraft banner