1. 23 9月, 2016 1 次提交
  2. 08 9月, 2016 1 次提交
    • C
      Suggestion tag improvements. · a7f9782b
      CyrusNajmabadi 提交于
      1. Increase opacity
      2. Support user configuration of the suggestion tag color.
      3. Refresh the color when the user changes fonts and colors.
      a7f9782b
  3. 20 7月, 2016 1 次提交
  4. 06 5月, 2016 1 次提交
  5. 04 11月, 2015 1 次提交
  6. 28 10月, 2015 2 次提交
  7. 27 10月, 2015 2 次提交
  8. 24 10月, 2015 1 次提交
  9. 16 10月, 2015 1 次提交
  10. 13 10月, 2015 1 次提交
  11. 30 9月, 2015 1 次提交
    • D
      Inline Rename usability improvements · 66a6273a
      David Poeschl 提交于
      Fixes #5076
      
      - Introduce instructional text when the dashboard is first shown (or when newName = originalName). This should help users who are used to the pre-VS2015 modal dialog learn to edit the identifier inline in the editor. If we at some point add a way to launch Inline Rename with a new name already specified, we'll need to be a bit more careful about how to both show that new name *and* the instructional text.
      
      - Show the newName as the user types it
      
      - Rearranging the info in the window to flow a bit better:
          - Heading (rename from x to y, or show getting started instructions)
          - Settings
          - Summary (# locations to be updated and any conflict info).
      
      - Slightly changed the reference count text from "found 1 reference in 1 file" (which made sense in large solutions where you saw "Searching..." for a while, which then got replaced with this text) to a more standalone version of "Rename will update 1 reference in 1 file."
      66a6273a
  12. 29 9月, 2015 1 次提交
  13. 16 9月, 2015 1 次提交
    • M
      Add a new suggested action "FixMultipleSuggestedAction" for IDE layer... · d164777b
      Manish Vasani 提交于
      Add a new suggested action "FixMultipleSuggestedAction" for IDE layer corresponding to FixMultipleCodeAction and FixMultipleContext. Also implement the FixMultipleOccurrencesService to compute and apply a FixMultipleSuggestedAction.
      
      Subsequent change will use this service to fix (suppress) diagnostics selected in the error list.
      d164777b
  14. 10 6月, 2015 1 次提交
  15. 12 5月, 2015 1 次提交
  16. 06 5月, 2015 1 次提交
    • D
      Add "Brace Matching" color · f4c429cc
      David Poeschl 提交于
      Partial fix for internal TFS bug #927616 ""Brace Matching (Highlight)"
      Color setting is ignored"
      
      This change adds a new "Brace Matching" color (not to be confused with
      the existing "Brace Matching (Highlight)" and "Brace Matching
      (Rectangle)" colors) that controls the appearance of brace matching. It
      is user customizable and the Background color controls the fill
      ("Highlight") and the Foreground color controls the outline
      ("Rectangle").
      
      The default background color was chosen to match Visual Studio 2013's
      default "Brace Matching (Highlight)" color.
      
      There will also be a related closed-source change for the themed colors,
      and that change will complete the bug.
      f4c429cc
  17. 02 5月, 2015 1 次提交
  18. 25 4月, 2015 1 次提交
  19. 14 4月, 2015 1 次提交
  20. 10 4月, 2015 1 次提交
  21. 04 3月, 2015 1 次提交
    • D
      Better handle dismissed rename tracking sessions · 499a46f5
      David Poeschl 提交于
      Fixes #540 "Stale rename entries in the lightbulb menu"
      
      Prior to this change, dismissed rename tracking sessions continued to
      provide codefixes which would silently fail when invoked, without
      completing the rename operation.
      
      With this change, we now do the following when rename tracking is
      manually dismissed:
      
      - Trigger the diagnostic service to reanalyze the document, thus
      removing the rename tracking diagnostic.
      - Stop providing a codefix when requested
      - Show a dialog if a cached codefix is invoked explaining that the
      rename was not performed.
      
      Here are the there user scenarios:
      
      1. The user dismisses rename tracking
      
          - The lightbulb will continue to show in the margin, regardless of
      whether any codefix/refactoring is actually still available.
      
      2. The user expands the lightbulb without it ever having been expanded
      before.
      
          - In this case, we are queried for fixes and will not return any, so
      either the lightbulb will disappear or it will contain other relevant
      codefixes/refactorings at that position, excluding rename.
      
      3. The user expands the lightbulb after it was previously expanded.
      
          - Our fix was already cached, so we can only give a reasonable message
      when it is invoked.
      
      Once #885 is fixed, we can instead implement IDiagnosticUpdateSource and
      avoid forcing diagnostic reanalysis.
      499a46f5
  22. 24 2月, 2015 1 次提交
    • D
      Use TriggerDiagnosticDescriptor in RenameTracking · 50ef7ff5
      David Poeschl 提交于
      Fixes #466 "Use a 'TriggerDiagnosticDescriptor' for the rename tracking
      diagnostic"
      
      Updates the RenameTrackingDiagnosticAnalyzer to use a
      TriggerDiagnosticDescriptor, which prevents the diagnostic title from
      appearing in the preview area of the lightbulb. We now pass the
      RenameFrom and RenameTo names as part of the Diagnostic's property bag
      and construct the localized codefix title based on these in the codefix
      itself.
      50ef7ff5
  23. 20 2月, 2015 1 次提交
    • D
      Prevent CodeActions commits during Inline Renames · b21230ad
      David Poeschl 提交于
      Fix #554: This fixes a crash that was caused by invoking a lightbulb
      item that caused an Inline Rename session to launch when there's already
      an inline rename session active. We now check for inline rename sessions
      during lightbulb commit. If an inline rename session is active, we halt
      the lightbulb commit and tell the user to complete their rename session.
      
      This only prevents one (but probably the most frequent) manifestation of
      a larger problem in which rename is trying to perform a series of
      changes to the workspace that can be interrupted by some other feature
      applying its changes to the workspace. This larger design problem is
      tracked as #681.
      b21230ad
  24. 27 1月, 2015 1 次提交