Periodical ajax call causes dragging element to disappear.

I'm trying to get a working prototype of a drag/drop interface, which needs to update panels every second.  The problem I am having is that when the setTimeout function runs the pxyActions_Click method, the presently dragging DOM element disappears. :(  Any ideas to implement a “startDrag” event that suspends ajax calls?

protected function pxyActions_Create() {
    $this->pxyActions = new QControlProxy($this, 'pxyActions');
    $this->pxyActions->AddAction(new QClickEvent(), new QAjaxAction('pxyActions_Click'));
    $this->pxyActions_Click();
}
        
public function pxyActions_Click() {
    $this->RereshCallList();
    QApplication::ExecuteJavaScript("window.setTimeout(\"qc.pA('PageForm', 'pxyActions', 'QClickEvent', '', 'icoWait');\", 1000);");
}

public function RefreshCallList() {
    foreach ($this->arrCalls as $intCallId => $arrCall) {
        // ... Attempt to load existing child to update, if not create.
        $objLabel = $this->Form->GetControl('lblCall' . $intCallId);

        if (false == is_object($objLabel)) {
            $objLabel = new QLabel($this, 'lblCall' . $intCallId);
            $objLabel->Position = QPosition::Relative;        
            $objLabel->AddControlToMove($objLabel);
            $objLabel->AddAction(new QMoveEvent(), new QAjaxControlAction($this, 'Label_Drop'));
                    
            foreach ($this->Form->pnlListUsers->GetChildControls() as $lblUser) {
                $objLabel->AddDropZone($lblUser);
            }
                    
            $this->AddChildControl($objLabel);
        }
                
        $objLabel->Text = $arrCall['number'];
    }
            
    $this->MarkAsModified();
}
.bc

Mike, you are a great help.  I wish that we could arrange some time for you to come up to Salt Lake and meet our development team and advise us on our progress with the revamp  to your old CSMS system, as well as it's sister projects all now running on QCodo. :)

It has taken me some time to adjust my brain to true OO, but I now fully realize the awesome power of a singular point code-base (instead of juggling JS/PHP/Smarty/Etc.) and totally predictable naming conventions.  The only problem is that the business side expects things too fast!

- Travis

This JS worked out just perfect. Thanks!

Page = {
    CallBack: function() {
        if (qcodo.currentMouseHandleControl == null) {
            qc.pA('PageForm', 'pxyActions', 'QClickEvent', 'Refresh', 'icoWait');
        } else {
            setTimeout('Page.CallBack()', 1000);
        }
    }
}
.bc

Yes, it probably should be -- but I think we can make it a bit cleaner by adding timed calls (or polling) to QForm itself, which would in essence provide “push”-like capability to qcodo.

Definitely a good idea -- feel free to add a ticket in the issue tracker for this.

Hello,

i'm using something similar too for a cms based on qcodo.

One thing we can do is to implements observer/observable pattern.

each object wich as periodical routine(observer) should register itself to qform(observable) (by implementing an interface for instance).

Then in QFORM we could have somthing like an array

$periodicalObservers[$timeToNextAjax] = $ObjectInterface

then while the difference is ok $time > $timeToNextAjax
call the interface method

$ObjectInterface->ProcessPeriodicalRequest($timeTonextAjax);

Where ProcessPeriodicalRequest would be something like.

public function ProcessPeriodicalRequest($frequency)
{
  switch($frequency)
  {
      case 10000:
       //do something each 10s 
      break;
   }
}

what do you think ? this is speed idea i think things can be better. Creating a real component in charge of TimeEvents in qcodo etc.