Lines Matching defs:it

767 		// because it gets saved on the boot disk but the above checks
911 std::set<thread_id>::iterator it;
912 for (it = addPosesThreads.begin(); it != addPosesThreads.end(); it++) {
914 wait_for_thread(*it, NULL);
1268 // the entries that it adds
1306 // Also, this class represents the entire BMessenger, not just it's
1712 // want it on the desktop or in the disks window.
1854 // the viewBounds top, it means the view is scrolled
1861 // the draw and do it later
1927 // pose adopts model and deletes it when done
2737 // column exists so remove it from list
2969 // got it, bail
2973 // if we're in one of the icon modes and it's a newly created item
2997 // info was read properly but it's not for this directory
3149 // it is going out of view for example
3154 // so it needs to be changed anyways!
3560 // remove pose from VSlist so it doesn't "bump" into itself
3606 // position, give up and simply place it towards the top left.
3675 // it's time to check the Deskbar frame again
3744 // found one and it is different from the current
3768 // place it onscreen
3779 // add it at the new location
3895 // than the actual index of the pose we search, thus missing it
3896 // and failing to remove it. This having severe implications
3897 // everywhere in the code as it is asserted that it must be always
4355 // try picking it up from the message
4451 // reset system cursor in case it was altered by drag and drop
4515 // the targetDirectory to it, else set it to this pose view
4606 // here is a file for the drag initiator, it is up to it now
4607 // to stuff it with the goods
4613 // we had the user pick a specific type from a menu, use it
4624 // we had the user pick a specific type from a menu, use it
5424 // is 'some_folder' and watch it, expecting the creation of
5468 // if it's a query notification then we're just being told we
5470 // but it's a node monitor notification then that means our query
5476 // it is impossible to watch for ENTRY_REMOVED in
5492 // What happens when a node and a symlink to it are in the
5611 // if we have trouble setting up model then we stuff it into
5612 // a zombie list in a half-alive state until we can properly awaken it
5662 // get the inode of the root and check if we got a notification on it
5878 // if node is busy, wait a little, it may be in the
5960 // we received an attr changed notification for a zombie model, it means
5961 // that although we couldn't open the node the first time, it seems
5962 // to be fine now since we're receiving notifications about it, it might
5963 // be a good time to convert it to a non-zombie state. cf. test in #4130
6240 "the Trash. Would you like to delete it instead? "
6951 // TODO: we might want to change this to make it always work
7020 // find the upper-left pose (I know it's ugly!)
7264 // we now need to update the pose view's selection list by clearing it
7300 // turn on auto scrolling if it's not yet on
7308 // reset cursor in case we set it to the copy cursor
7372 // and B_MOUSE_IDLE message doesn't pass it
7445 // only clear selection if we are not extending it
7594 // make sure pose is selected, it could have been deselected as part of
7946 // Remember fSelectionPivotPose because ClearSelection() NULLs it
7947 // and we need it to be preserved.
8072 // remove it from list no matter what since it might be in list
8423 // the new add_poses thread will then set fAddPosesThread to its ID and it
8661 // add information about the child, so that we can select it
9014 // (ie why it wasn't calling ScrollTo(point) simply). Although
9015 // it cannot have been tested, since it was broken before, I am
9812 // new target is valid, select it
9972 // like Select/IsSelected in BPose and let it handle this case internally