Skip navigation
Currently Being Moderated

Blueprint shouldn't use entire lines of code as the search string.

Jun 15, 2009 11:32 AM

If I have the editor open on some MXML code, and a range of characters is selected in the editor, then invoking Blueprint uses the selected text as the search string. This seems like the right thing to do.

 

However, if there is NO text selected, Blueprint uses an entire line of code as the search string (whatever line the insertion point happens to be in). I my experience this is almost always wrong, because (a) most lines of code e.g. "}" or "allPanels[1] = new LayersPanel();" or "private var allPanels : Dictionary = new Dictionary(); do not usually produce very useful search results, and (b) because these strings clutter up the search history.

 
Replies
  • Currently Being Moderated
    Jun 16, 2009 10:49 AM   in reply to Mark Shepherd

    Thanks for the suggestion!

     

    We will reevaluate the use case for using an entire line of code as a query.

     

    Mira Dontcheva

    Research Scientist

    Adobe Systems

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points