John Levon <[EMAIL PROTECTED]> writes:
| On Thu, Dec 05, 2002 at 01:56:33PM +0000, Angus Leeming wrote:
|
| > I would of course be happy to change only XWorkArea, but the cursor glyph
| > depends also on whether input is prohibitted or not and /that/ is controlled
| > by LyXView. That, therefore, is the right place to set the glyph and so
| > necessitates going through dispatch.
|
| That *sucks*. Can you get to the workarea widget from the view ? This is
| SO a toolkit-only thing, and any LFUN is strictly a very ugly hack.
It is absolutetly _not_ a toolkit-only thing, since it is the core
that desices if input is prohibited or not, or that LyX is busy.
| I'll take him on :)
Ha, I'll lick you...
(hmm da hmm)
| > Wait for my patch; I've left you with this in QtView.h ;-)
| > /// FIXME. Not yet implemented.
| > virtual void setCursor(bool editing) const {}
|
| I've already fixed I-beam. I'm not interested in any ugly prohibitInput
| thing. For starters, most uses of it are entirely unecessary.
That is a completely different case and have no bearing on this issue
_now_.
| I am less than happy about exposing xforms brokenness in this API.
It is not xforms specific.
| First we should audit prohibitInputs and remove the unnecessary ones
| (there are several). Then we should refactor until qt doesn't have to
| see prohibitInput at all.
First we should make things work as they always have, pI and AI should
not be fiddled with at this time.
--
Lgb
