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
90 // If there are sub-filters, we need to find at least one component
97 // We had a match, so this comp-filter succeeds
103 // If we got here it means there were sub-comp-filters or
110 // If we got here it means we got through all comp-filters alive so the
120 * property we're checking should be specified, not the property to check
159 // If there are sub-filters, we need to find at least one property
167 // We had a match, so this prop-filter succeeds
173 // If we got here it means there were sub-param-filters or
180 // If we got here it means we got through all prop-filters alive so the
190 * parameter we're checking should be specified, not the parameter to check
220 // If there are sub-filters, we need to find at least one parameter
225 // We had a match, so this param-filter succeeds
231 // If we got here it means there was a text-match filter and there
237 // If we got here it means we got through all param-filters alive so the
247 * or parameter we need to validate.
295 // If the valarm is wrapped in a recurring event, we need to
308 // We need to check from these expanded alarms, which
309 // one is the first to trigger. Based on this, we can
310 // determine if we can 'give up' expanding events.
328 // We store the first alarm as a means to
329 // figure out when we can stop traversing.
341 // which means we can assume there was no match.