Abdelrazak Younes wrote: >> Hang on. My understanding is that all actions from the dialogs must go >> through >> the LFUN dispatch mechanism and that uses strings.
> More exactly, an action from a View (a dialog) use a controller method. > The Controller method might (best) or might not use the dispatch > machinery depending on the operation. Laughs. You've just made that rule up. That's not the law that I operated under. > When it's absolutely necessary yes. In the case of the Paragraph dialog, > it should be update at each new cursor location. The serialisation is > only good for one-shot dialog showing not for real-time update. Shrug. Why not. It used to work fine. > This is not the point in this case. I don't need this data on > initialisation, I need it on _update_ So? Again, this used to work once upon a merry time. >> So what exactly are you proposing to change with direct calls? > See patch (not finished), Well, I'm not in a position to dictate; you're the one writing the code not me. However, this turns the philosophy that drove the whole frontend/backend separation on its head. The frontends should not touch the core directly at all. That's what the LFUN dispatch mechanism is for. Angus
