aboutsummaryrefslogtreecommitdiffstats
path: root/pages/develop/api/efl/net/control/technology/method/scan.txt
blob: c7329e64792698dc6481972f910cec2dba2d61c9 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
~~Title: Efl.Net.Control.Technology.scan~~
===== Description =====

%%Explicitly trigger a scan.%%

%%The scan will happen asynchronously in the background, with the results being delivered by events in the technology, %%[[:develop:api:efl:net:control|Efl.Net.Control]]%% or %%[[:develop:api:efl:net:control:access_point|Efl.Net.Control.Access_Point]]%% associated with the technology. For example, scan on WiFi will add and delete access points.%%

%%It is worth to mention that explicit scans should be avoided. Rare cases are when user requested them, like entering a configuration dialog which demands fresh state. Otherwise prefer to let the system passively do scans in a timely manner.%%

//Since 1.19//
{{page>:develop:api-include:efl:net:control:technology:method:scan:description&nouser&nolink&nodate}}

===== Signature =====

<code>
scan {
    return: ptr(Eina.Future);
}
</code>

===== C signature =====

<code c>
Eina_Future *efl_net_control_technology_scan(Eo *obj);
</code>

===== Implemented by =====

  * **Efl.Net.Control.Technology.scan**