title: How does one pass an argument to a directive without over-writing parent scope?
body: <p>I need to create a directive that acts upon table cells where the table rows are rendered using <code>ng-repeat</code> -- to that end I have relied in part on <a href="https://stackoverflow.com/a/15208347/34806">this answer</a> to a question entitled "Calling a function when ng-repeat has finished". Unlike that Q&amp;A however, I need to pass in an argument to my directive, and for this I have relied in part on <a href="https://stackoverflow.com/a/26409802/34806">this answer</a> (to a question entitled "Angularjs - Pass argument to directive").</p>
  
  <p>So in my case I've added <code>fixed-column-tooltip</code> for my directive, and <code>columnselector</code> as its argument to the <code>&lt;tr&gt;</code> as follows:</p>
  
  <pre><code>&lt;tr fixed-column-tooltip columnselector=".td-keyField" ng-repeat="trData in trDataWatch"&gt;
  </code></pre>
  
  <p>But when per the second answer, I added what I've learned is an "isolate scope" to my directive, I no longer had access to the original scope necessary as per the first answer:</p>
  
  <pre><code>'use strict';
  
  angular.module('cmt.cases.directives')
  
  .directive('fixedColumnTooltip', function ($timeout) {
      return {
          restrict: 'A',
          scope: {
              columnselector: '@'
          },
          link: function (scope, element, attr) {
              if (scope.$last === true) { //undefined because not operating on original scope
          ...
  </code></pre>
  
  <p>Is there a way to maintain access to the original scope, but also have access to the <code>columnselector</code> argument?</p>