use this

&gt; ng-if=&quot;area == false&quot;

 OR 

&gt; ng-if=&quot;area == true&quot;


this may help someone

Use like this

    &lt;div ng-if=&quot;data.IsActive === 1&quot;&gt;InActive&lt;/div&gt;
    &lt;div ng-if=&quot;data.IsActive === 0&quot;&gt;Active&lt;/div&gt;

**Just use for True:**

    &lt;li ng-if=&quot;area&quot;&gt;&lt;/li&gt;

**and for False:**

    &lt;li ng-if=&quot;area === false&quot;&gt;&lt;/li&gt;



**try this:**

    &lt;div ng-if=&quot;$scope.length == 0&quot; ? true : false&gt;&lt;/div&gt;

**and show or hide**

    &lt;div ng-show=&quot;$scope.length == 0&quot;&gt;&lt;/div&gt;

else it will be hide


-----------------or--------------------------

if you are using $ctrl than code will be like this:

**try this:**

    &lt;div ng-if=&quot;$ctrl.length == 0&quot; ? true : false&gt;&lt;/div&gt;

**and show or hide**

    &lt;div ng-show=&quot;$ctrl.length == 0&quot;&gt;&lt;/div&gt;

else it will be hide

In angular 1, you can use `ng-show` and `ng-hide`.In your case, you would use `ng-hide`. For example:

    &lt;li ng-hide=&quot;area&quot;&gt;&lt;/li&gt;

you are not using the $scope 
you must use $ctrl.area or $scope.area instead of area

As far as I can tell, anywhere `std::back_inserter` works in an STL algorithm, you could pass an `std::inserter` constructed with `.end()` instead:

    std::copy(l.begin(), l.end(), std::back_inserter(dest_list));
    std::copy(l.begin(), l.end(), std::inserter(dest_list, dest_list.end()));

AND, unlike `back_inserter`, as far as I can tell `inserter` works for ANY STL container!! I tried it successfully for `std::vector`, `std::list`, `std::map`, `std::unordered_map` before coming here surprised.


I thought that maybe it&#39;s because `push_back` could be faster for some structures than `insert(.end())`, but I&#39;m not sure...

That doesn&#39;t seem to be the case for `std::list` (makes sense):

    // Copying 10,000,000 element-list with std::copy. Did it twice w/ switched order just in case that matters.
    Profiling complete (884.666 millis total run-time): inserter(.end())
    Profiling complete (643.798 millis total run-time): back_inserter
    Profiling complete (644.060 millis total run-time): back_inserter
    Profiling complete (623.151 millis total run-time): inserter(.end())

But it does slightly for `std::vector`, though I&#39;m not really sure why?:

    // Copying 10,000,000 element-vector with std::copy.
    Profiling complete (985.754 millis total run-time): inserter(.end())
    Profiling complete (746.819 millis total run-time): back_inserter
    Profiling complete (745.476 millis total run-time): back_inserter
    Profiling complete (739.774 millis total run-time): inserter(.end())

I guess in a vector there is slightly more overhead figuring out where the iterator is and then putting an element there vs just arr[count++]. Maybe it&#39;s that?


But still, is that the main reason?

My followup question, I guess, is &quot;Is it okay to write `std::inserter(container, container.end())` for a templated function and expect it to work for (almost) any STL container?&quot;

&lt;hr&gt;

I updated the numbers after moving to a standard compiler. Here is my compiler&#39;s details:
&lt;br&gt;gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) &lt;br&gt;
Target: x86_64-linux-gnu

My build command:

    g++ -O0 -std=c++11 algo_test.cc



&lt;hr&gt;

I think [this question asks the second half of my question][1], namely, &quot;Can I write a templated function that uses `std::inserter(container, container.end())` and expect it to work for almost every container?&quot;

The answer there was &quot;Yes, for every container except for `std::forward_list`.&quot; But based on the discussion in the comments below and in [user2746253][2]&#39;s answer, it sounds like I should be aware that this would be slower for `std::vector` than using `std::back_inserter`...

Therefore, I might want to specialize my template for containers using `RandomAccessIterator`s to use `back_inserter` instead. Does that make sense? Thanks.


  [1]: https://stackoverflow.com/q/23360656/751061
  [2]: https://stackoverflow.com/users/2746253/user2746253

What&#39;s the benefit of std::back_inserter over std::inserter?

How To check response.statusCode in SendSynchronousRequest in Swift
The Code is Below :

    let urlPath: String = &quot;URL_IS_HERE&quot;
    var url: NSURL = NSURL(string: urlPath)
    var request: NSURLRequest = NSURLRequest(URL: url)
    var response: AutoreleasingUnsafeMutablePointer&lt;NSURLResponse?&gt; = nil
    
    var error: NSErrorPointer? = nil
    var data = NSURLConnection.sendSynchronousRequest(request, returningResponse: response, error: nil) as NSData?

before and in objective c , we check response.statusCode With this :
      (long)response.statusCode
but in swift i have no idea how can check response status Code

How To Check Response.statusCode in sendSynchronousRequest on Swift

Why doesn&#39;t this work.

`&lt;li ng-if=&quot;!area&quot;&gt;&lt;/li&gt;`

Feels a bit illogical since

`&lt;li ng-if=&quot;area&quot;&gt;&lt;/li&gt;`

works just fine.

&#39;area&#39; is defined in scope as true/false
Any workarounds for this? I would prefer not to use ng-show/ng-hide since both of them renders items in DOM.

Angular ng-if not true

Why doesn't this work.
<code>&#x3C;li ng-if="!area">&#x3C;/li></code>
Feels a bit illogical since
<code>&#x3C;li ng-if="area">&#x3C;/li></code>
works just fine.
'area' is defined in scope as true/false
Any workarounds for this? I would prefer not to use ng-show/ng-hide since both of them renders items in DOM.

Anyone know how to clear the selected value of an ui-select box in angular?

I want the functionality of select2 where you have a small x in the selectbox. Doesn&#39;t look like it&#39;s got the allow-clear method that select2 got.

Clear selected option in ui-select angular

I would like to use `angular.js` for my Image Editing Tool in my website. Do I need `node.js` also?

I don&#39;t understand the scenario. If I don&#39;t need it, then when do we use both nodejs and angularjs together?



Do I need node.js to use Angularjs?

Im wondering if there is a way to pass an argument to a directive?

What I want to do is append a directive from the controller like this:

    $scope.title = &quot;title&quot;;
    $scope.title2 = &quot;title2&quot;;
    
    angular.element(document.getElementById(&#39;wrapper&#39;)).append(&#39;&lt;directive_name&gt;&lt;/directive_name&gt;&#39;);

Is it possible to pass an argument at the same time so the content of my directive template could be linked to one scope or another?

here is the directive:

    app.directive(&quot;directive_name&quot;, function(){
        return {
            restrict:&#39;E&#39;,
            transclude:true,
            template:&#39;&lt;div class=&quot;title&quot;&gt;&lt;h2&gt;{{title}}&lt;/h3&gt;&lt;/div&gt;&#39;,
            replace:true
        };
    })

What if I want to use the same directive but with $scope.title2?

Angularjs - Pass argument to directive

I&#39;ve read so many different problems with this and none of the solution given seem to fit my use case.  I started by simply putting target=&quot;_top&quot; on all my links, but that actually forces my app to reload which wont work.  I&#39;ve also seen people say they use **autoscroll=&quot;true&quot;** but that only seems to work if its within my **ui-view**.  

The issue with this is that in my index.html file I have fixed nav and other static elements that are above my first ui-view.  This means when I go to other pages I lose the navigation as the page loads past those elements.  I&#39;ve also tried putting this on the body with:

    &lt;body autoscroll=&quot;true&quot;&gt;
    &lt;/body&gt;

This doesn&#39;t seem to do anything either.  So the question is, how can I make sure that new pages (new route changes from ui-router) result in starting at the top of the page? THANKS!

Autoscroll to TOP with ui-router and Angularjs


I have an input which filters a ng-repeat list on change. The repeat contains a lot of data and takes a few seconds to filter through everything. I would like their to be 0.5 second delay before I start the filtering process. **What is the correct way in angular to create this delay?**

**Input**

     &lt;input ng-model=&quot;xyz&quot; ng-change=&quot;FilterByName()&quot; /&gt;

**Repeat**

     &lt;div ng-repeat&quot;foo in bar&quot;&gt;
          &lt;p&gt;{{foo.bar}}&lt;/p&gt;
     &lt;/div&gt;

**Filter Function**

     $scope.FilterByName = function () {
          //Filtering Stuff Here
     });

Thanks 

 

Angular ng-change delay

I&#39;m having a problem with trying to use Angular&#39;s `*ngFor` and `*ngIf` on the same element. 

When trying to loop through the collection in the `*ngFor`, the collection is seen as `null` and consequently fails when trying to access its properties in the template.

&lt;!-- language: lang-ts --&gt;

    @Component({
      selector: &#39;shell&#39;,
      template: `
        &lt;h3&gt;Shell&lt;/h3&gt;&lt;button (click)=&quot;toggle()&quot;&gt;Toggle!&lt;/button&gt;
        
        &lt;div *ngIf=&quot;show&quot; *ngFor=&quot;let thing of stuff&quot;&gt;
          {{log(thing)}}
          &lt;span&gt;{{thing.name}}&lt;/span&gt;
        &lt;/div&gt;
      `
    })

    export class ShellComponent implements OnInit {
      
      public stuff:any[] = [];
      public show:boolean = false;
    
      constructor() {}
    
      ngOnInit() {
        this.stuff = [
          { name: &#39;abc&#39;, id: 1 },
          { name: &#39;huo&#39;, id: 2 },
          { name: &#39;bar&#39;, id: 3 },
          { name: &#39;foo&#39;, id: 4 },
          { name: &#39;thing&#39;, id: 5 },
          { name: &#39;other&#39;, id: 6 },
        ]
      }
      
      toggle() {
        this.show = !this.show;
      }
      
      log(thing) {
        console.log(thing);
      }
    
    }

I know the easy solution is to move the `*ngIf` up a level but for scenarios like looping over list items in a `ul`, I&#39;d end up with either an empty `li` if the collection is empty, or my `li`s wrapped in redundant container elements.

Example at this [plnkr][1].

Note the console error:

    EXCEPTION: TypeError: Cannot read property &#39;name&#39; of null in [{{thing.name}} in ShellComponent@5:12]

Am I doing something wrong or is this a bug?

  [1]: http://plnkr.co/edit/C5tZ8mD3iWczVvWkWycH?p=preview

*ngIf and *ngFor on same element causing error

I&#39;m confused a bit. I need to hide block if result have one of several cases. But seems it not working correctly...

    &lt;div *ngIf=&quot;currentStatus !== &#39;open&#39; || currentStatus !== &#39;reopen&#39; &quot;&gt;
    
        &lt;p padding text-center class=&quot;text-notification&quot;&gt;{{message}}&lt;/p&gt;
    
    &lt;/div&gt;

It&#39;s just appeared with other condition. It doesn&#39;t work neither 1 condition nor for 2. Also tried `*ngIf=&quot;currentStatus !== (&#39;open&#39; ||  &#39;reopen&#39;) &quot;` but it&#39;s works ok only for 1 case. 

angular 4: *ngIf with multiple conditions

How would I have multiple cases in an `*ngIf` statement? I&#39;m used to Vue or Angular 1 with having an `if`, `else if`, and `else`, but it seems like Angular 4 only has a `true` (`if`) and `false` (`else`) condition.

According to the documentation, I can only do:

    &lt;ng-container *ngIf=&quot;foo === 1; then first else second&quot;&gt;&lt;/ng-container&gt;
    &lt;ng-template #first&gt;First&lt;/ng-template&gt;
    &lt;ng-template #second&gt;Second&lt;/ng-template&gt;
    &lt;ng-template #third&gt;Third&lt;/ng-template&gt;

But I want to have multiple conditions (something like):

    &lt;ng-container *ngIf=&quot;foo === 1; then first; foo === 2; then second else third&quot;&gt;&lt;/ng-container&gt;
    &lt;ng-template #first&gt;First&lt;/ng-template&gt;
    &lt;ng-template #second&gt;Second&lt;/ng-template&gt;
    &lt;ng-template #third&gt;Third&lt;/ng-template&gt;

But I&#39;m ending up having to use `ngSwitch`, which feels like a hack:

    &lt;ng-container [ngSwitch]=&quot;true&quot;&gt;
      &lt;div *ngSwitchCase=&quot;foo === 1&quot;&gt;First&lt;/div&gt;
      &lt;div *ngSwitchCase=&quot;bar === 2&quot;&gt;Second&lt;/div&gt;
      &lt;div *ngSwitchDefault&gt;Third&lt;/div&gt;
    &lt;/ng-container&gt;

Alternately, it seems like a lot of the syntaxes I&#39;ve got used to from Angular 1 and Vue aren&#39;t supported in Angular 4, so what would be the recommended way to structure my code with conditions like this?




Content Type	Original Author	Original Content on Stackoverflow
Question	user3289197	View Question on Stackoverflow
Solution 1 - Angularjs	Sachin Sudhakar Sonawane	View Answer on Stackoverflow
Solution 2 - Angularjs	Raj	View Answer on Stackoverflow
Solution 3 - Angularjs	coloma1984	View Answer on Stackoverflow
Solution 4 - Angularjs	Rizwan	View Answer on Stackoverflow
Solution 5 - Angularjs	aslantorret	View Answer on Stackoverflow
Solution 6 - Angularjs	M Usman Nadeem	View Answer on Stackoverflow

Angular ng-if not true

Angularjs Problem Overview

Angularjs Solutions

Solution 1 - Angularjs

Solution 2 - Angularjs

Solution 3 - Angularjs

Solution 4 - Angularjs

Solution 5 - Angularjs

Solution 6 - Angularjs

How To Check Response.statusCode in sendSynchronousRequest on Swift

What's the benefit of std::back_inserter over std::inserter?

Attributions