Lines Matching full:we
35 // We'll parse it manually, as it's pretty simple.
51 * component we're checking should be specified, not the component to check
92 // If there are sub-filters, we need to find at least one component
99 // We had a match, so this comp-filter succeeds
105 // If we got here it means there were sub-comp-filters or
112 // If we got here it means we got through all comp-filters alive so the
122 * property we're checking should be specified, not the property to check
163 // If there are sub-filters, we need to find at least one property
171 // We had a match, so this prop-filter succeeds
177 // If we got here it means there were sub-param-filters or
184 // If we got here it means we got through all prop-filters alive so the
194 * parameter we're checking should be specified, not the parameter to check
224 // If there are sub-filters, we need to find at least one parameter
229 // We had a match, so this param-filter succeeds
235 // If we got here it means there was a text-match filter and there
241 // If we got here it means we got through all param-filters alive so the
251 * or parameter we need to validate.
299 // If the valarm is wrapped in a recurring event, we need to
312 // We need to check from these expanded alarms, which
313 // one is the first to trigger. Based on this, we can
314 // determine if we can 'give up' expanding events.
332 // We store the first alarm as a means to
333 // figure out when we can stop traversing.
345 // which means we can assume there was no match.