Bug #37725

Set Dispatched on Request after FormRuntime run

Added by Marc Neuhaus about 3 years ago. Updated 8 months ago.

Status:New Start date:2012-06-04
Priority:Should have Due date:
Assigned To:- % Done:

0%
Category:-
Target version:-

History

#1 Updated by Bastian Waidelich about 3 years ago

  • Status changed from New to Accepted

#2 Updated by Bastian Waidelich almost 2 years ago

  • Status changed from Accepted to Needs Feedback

Hey Marc,

sorry, that is a long time ago.. But can you recall what this was about exactly?

#3 Updated by Marc Neuhaus almost 2 years ago

hmm, i think it was about not "finishing" the request through "setDispatched" in the FormRuntime.
i'm not even sure anymore why this bothered me ^^

#4 Updated by Bastian Waidelich almost 2 years ago

  • Status changed from Needs Feedback to Accepted

Marc Neuhaus wrote:

hmm, i think it was about not "finishing" the request through "setDispatched" in the FormRuntime.
i'm not even sure anymore why this bothered me ^^

Now that you mention it - I think it was related to the Expose or the debug toolbar.. Anyways, I'll have a look asap

#5 Updated by Marc Neuhaus almost 2 years ago

Yea! now i remember.

I used the Signal emitted by setDispatsched to collect dispatched Request for the DebugToolbar :)

#6 Updated by Bastian Waidelich 8 months ago

  • Status changed from Accepted to New
  • Assigned To deleted (Bastian Waidelich)

Sorry, I didn't get around digging into that one.. I unassign myself for now so no-one feels blocked to push a patch. Might be the issue is resolved in the latest version

Also available in: Atom PDF