On Thu, Dec 05, 2002 at 03:53:46PM +, Angus Leeming wrote:
> I think I prefer mine because it's guaranteed to do the right thing in all
> cases.
At the expense of abusing the lyx core.
> (At least use the toolkit. Get rid of XWorkArea::enter and use the thing
> below. Together with similar
it works fine with busy cursor simply
> because of the fl_deactivate_all_forms() in prohibitInput - we never see
> enter/leave events. This is still a hack, but it's xforms/ only, so
> super.
>
> (of course this means we must deal with unbalanced enter/leaves, I
> think)
>
On Thu, Dec 05, 2002 at 03:04:11PM +, Angus Leeming wrote:
> I'm very happy to use your approach, but would like to see the code so I can
> compare/contrast ;-)
Here's the minimal bit. Note that it works fine with busy cursor simply
because of the fl_deactivate_all_forms()
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/frontends/LyXView.h,v
retrieving revision 1.18
diff -u -p -r1.18 LyXView.h
--- src/frontends/LyXView.h 1 Dec 2002 22:59:18 - 1.18
+++ src/frontends/LyXView.h 5 Dec 2002 14:41:15 -
@@ -71,6 +71,8 @@
On Thu, Dec 05, 2002 at 03:47:28PM +0100, Lars Gullik Bjønnes wrote:
> | Then the code can stay as it is too, except XWorkArea sets I-beam
> | cursor.
>
> I can live with that as well.
OK. This should work just fine. Unfortunately I made the aI changes in
my tree too, so we'll have to wait for a
John Levon <[EMAIL PROTECTED]> writes:
| On Thu, Dec 05, 2002 at 03:38:27PM +0100, Lars Gullik Bjønnes wrote:
|
| > pI and aI stay as is now.
| >
| > Open up this issue for 1.4.x
|
| Then the code can stay as it is too, except XWorkArea sets I-beam
| cursor.
I can live with that as well.
--
On Thu, Dec 05, 2002 at 03:38:27PM +0100, Lars Gullik Bjønnes wrote:
> pI and aI stay as is now.
>
> Open up this issue for 1.4.x
Then the code can stay as it is too, except XWorkArea sets I-beam
cursor.
john
--
"Trolls like content too."
- Bob Abooey, /.
e latexing etc. and even
| then it is feedback only NOT a correctness thing, and we do that
| already just fine by using the BufferView methods.
|
| So we should :
|
| a) remove most of the remaining uses of prohibitInput()
| b) rename it to indicate, e.g. showBusyCursor()
|
| I suspect that t
correctness thing, and we do that
already just fine by using the BufferView methods.
So we should :
a) remove most of the remaining uses of prohibitInput()
b) rename it to indicate, e.g. showBusyCursor()
I suspect that the deactivation of the workarea via the XFormsView means
that the e
I just comment out the prohibitInput() in MenuInsertLabel, but I still
couldn't type into the buffer. So does this mean it's not needed ?
Some cases of prohibitInput() (only a few remain) don't even have the
possibility of a dialog, so are definitely pointless, right ?
thanks
jo
10 matches
Mail list logo
