Re: Remaining selection/clipboard problems: How to proceed

2007-01-13 Thread Bo Peng
I am not going to do further changes, so if anybody wants fake selection on windows, persistent selection or something else please take care of that yourself. Thank you very much. I get the persistent selection patch and will try it later. I can not work on it soon because I will be extremely bu

Re: Remaining selection/clipboard problems: How to proceed

2007-01-13 Thread Georg Baum
Now that the clipboard works again on all platforms I give here a summary of the current status. Am Freitag, 5. Januar 2007 17:05 schrieb Georg Baum: > Let's start with our internal clipboard stack: This is advertised to the > user in the "paste recent" menu. If you know this it suddenly makes

Re: Remaining selection/clipboard problems: How to proceed

2007-01-08 Thread Georg Baum
Am Montag, 8. Januar 2007 10:03 schrieb Jean-Marc Lasgouttes: > I am OK with the fact that the list only contains (contained?) stuff > copied from within LyX, since this is coherent. That is still the case. > Concerning tables and maths, I would prefer them to be added, of > course. I did that.

Re: Remaining selection/clipboard problems: How to proceed

2007-01-08 Thread Jean-Marc Lasgouttes
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes: Georg> Am Freitag, 5. Januar 2007 18:00 schrieb Jean-Marc Lasgouttes: >> I like the current behaviour personally. It may need a rename, but >> I do not think it is wrong. Georg> Just to be clear: You mean the fact that copied-only stuff also

Re: Remaining selection/clipboard problems: How to proceed

2007-01-06 Thread Enrico Forestieri
On Sat, Jan 06, 2007 at 12:25:55PM +0100, Georg Baum wrote: > If you are not talking about X11 applications on X11, but about X11 > applications displayed on windows, using an X server that copies the > selection to the clipboard: Then you simply see that the selection can't > be completely emu

Re: Remaining selection/clipboard problems: How to proceed

2007-01-06 Thread Georg Baum
Am Samstag, 6. Januar 2007 01:17 schrieb Enrico Forestieri: > If I understand correctly, you would like to treat the selection as a > sort of internal clipboard which is allowed to be filled by a simple > selection and whose contents can be pasted with middle-button. That is how I understood it,

Re: Remaining selection/clipboard problems: How to proceed

2007-01-06 Thread Georg Baum
Am Freitag, 5. Januar 2007 21:25 schrieb Bo Peng: > > Sure you are welcome to implement it as a configurable option ;-) > > The problem I have with this is that > > OK. If this will make both of us happy. Of course I have the right to > set the default if I am writing the code. :-) I don't think

Re: Remaining selection/clipboard problems: How to proceed

2007-01-06 Thread Georg Baum
Am Freitag, 5. Januar 2007 18:00 schrieb Jean-Marc Lasgouttes: > I like the current behaviour personally. It may need a rename, but I > do not think it is wrong. Just to be clear: You mean the fact that copied-only stuff also appears in the stack, or the fact that only contents coming from LyX,

Re: Remaining selection/clipboard problems: How to proceed

2007-01-05 Thread Enrico Forestieri
On Fri, Jan 05, 2007 at 02:25:28PM -0600, Bo Peng wrote: > > Sure you are welcome to implement it as a configurable option ;-) > > The problem I have with this is that > > OK. If this will make both of us happy. Of course I have the right to > set the default if I am writing the code. :-) > > An

Re: Remaining selection/clipboard problems: How to proceed

2007-01-05 Thread Enrico Forestieri
On Fri, Jan 05, 2007 at 11:23:10AM -0600, Bo Peng wrote: > > Fake X selection for windows and Mac: The patch I originally sent is not > > needed anymore if the patch x.diff in this message is applied, since then > > the internal selection is always used if available. If we want to paste > > the cl

Re: Remaining selection/clipboard problems: How to proceed

2007-01-05 Thread Enrico Forestieri
On Fri, Jan 05, 2007 at 06:00:55PM +0100, Jean-Marc Lasgouttes wrote: > > "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes: > >> Fake X selection for windows and Mac: The patch I originally sent > >> is not needed anymore if the patch x.diff in this message is > >> applied, sinc

Re: Remaining selection/clipboard problems: How to proceed

2007-01-05 Thread Bo Peng
Sure you are welcome to implement it as a configurable option ;-) The problem I have with this is that OK. If this will make both of us happy. Of course I have the right to set the default if I am writing the code. :-) Anyway, I will have to wait for Georg to finish his selection cleanup, and f

Re: Remaining selection/clipboard problems: How to proceed

2007-01-05 Thread Abdelrazak Younes
Bo Peng wrote: Please note that the X selection protocol is supposed to be asynchronous i.e. copy should happen at paste time. The X selection is not an additional clipboard. I agree with you completely here, but again, you are talking about tech details, and I am talking about user experience.

Re: Remaining selection/clipboard problems: How to proceed

2007-01-05 Thread Abdelrazak Younes
Bo Peng wrote: > There is another simple mental model: selection, copy to selection > buffer. middle-button paste, paste from selection buffer. This model > may be easier to understand since it is what clipboard does. I don't like that, but I can live with that, leT's see what other think. it

Re: Remaining selection/clipboard problems: How to proceed

2007-01-05 Thread Bo Peng
Please note that the X selection protocol is supposed to be asynchronous i.e. copy should happen at paste time. The X selection is not an additional clipboard. I agree with you completely here, but again, you are talking about tech details, and I am talking about user experience. We (users) do n

Re: Remaining selection/clipboard problems: How to proceed

2007-01-05 Thread Abdelrazak Younes
Georg Baum wrote: Am Freitag, 5. Januar 2007 18:23 schrieb Bo Peng: Persistent selection is against the "simple mental model": The equation "selection == highlighted text on screen" would not be true anymore. There is another simple mental model: selection, copy to selection buffer. middle-bu

Re: Remaining selection/clipboard problems: How to proceed

2007-01-05 Thread Bo Peng
> There is another simple mental model: selection, copy to selection > buffer. middle-button paste, paste from selection buffer. This model > may be easier to understand since it is what clipboard does. I don't like that, but I can live with that, leT's see what other think. it worth pointing o

Re: Remaining selection/clipboard problems: How to proceed

2007-01-05 Thread Bo Peng
> 2. if this is going to be implemented, do so also under X11. What do you mean by 2? Pasting the clipboard if the selection is empty? That would destroy the simple selection model. Enrico's argument was that this model does not apply to windows. Although I don't agree I could live with that, but

Re: Remaining selection/clipboard problems: How to proceed

2007-01-05 Thread Georg Baum
Am Freitag, 5. Januar 2007 18:27 schrieb Bo Peng: > > I personally like it and I am sure others will (and Enrico will be the > > first ;-)). But I could live without and just using mouse-click plus Ctrl-v. > > OK. I can step back a little bit: > > 1. if this behavior is undefined in freedesktop.

Re: Remaining selection/clipboard problems: How to proceed

2007-01-05 Thread Georg Baum
Am Freitag, 5. Januar 2007 18:23 schrieb Bo Peng: > For MS Word, > > 1. consecutive identical copies is put to clipboard stack only once > (clipboard content is compared against the top item) > 2. copy from external application is copied to this stack > 3. no paste is necessary, of course word has

Re: Remaining selection/clipboard problems: How to proceed

2007-01-05 Thread Georg Baum
Am Freitag, 5. Januar 2007 17:35 schrieb Abdelrazak Younes: > Internally, when using multiple views, I am strongly against > un-selecting a selected text when this selected text is pasted onto the > other view. Externally (when a SelectionClear event is received) I could > live with a deselectio

Re: Remaining selection/clipboard problems: How to proceed

2007-01-05 Thread Bo Peng
I personally like it and I am sure others will (and Enrico will be the first ;-)). But I could live without and just using mouse-click plus Ctrl-v. OK. I can step back a little bit: 1. if this behavior is undefined in freedesktop.org, it is ok to me. 2. if this is going to be implemented, do so

Re: Remaining selection/clipboard problems: How to proceed

2007-01-05 Thread Bo Peng
Let's start with our internal clipboard stack: This is advertised to the user in the "paste recent" menu. If you know this it suddenly makes sense that a middle mouse button press pushes the current selection to the internal clipboard. So this is not a hack, but done on purpose. This is only done

Re: Remaining selection/clipboard problems: How to proceed

2007-01-05 Thread Jean-Marc Lasgouttes
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes: >> The next question: The clipboard stack is not really a "paste >> recent" stack: If you copy something in LyX without pasting it is >> nevertheless added, and anything that is pasted but comes from >> outside (selection or clipb

Re: Remaining selection/clipboard problems: How to proceed

2007-01-05 Thread Abdelrazak Younes
Georg Baum wrote: I think that I now fully understand how the selection is handled in LyX. /me too ;-) I have now documented the current code, and fixed some bugs, see the cvslog postings or read the code for details. Since there have been several opinions how selection should work I'll out

Remaining selection/clipboard problems: How to proceed

2007-01-05 Thread Georg Baum
I think that I now fully understand how the selection is handled in LyX. I have now documented the current code, and fixed some bugs, see the cvslog postings or read the code for details. Since there have been several opinions how selection should work I'll outline here the possible options. Le

Re: plain text output - how to proceed

2006-09-10 Thread Georg Baum
Am Sonntag, 10. September 2006 10:40 schrieb Peter Kümmel: > But there are warnings when compiling with msvc: > > stream6.cpp(252) : warning C4244: 'return' : conversion from 'ascii_ctype_facet::char_type' to 'char', possible loss of data > stream6.cpp(253) : warning C4244: 'argument' : conversio

Re: plain text output - how to proceed

2006-09-10 Thread Peter Kümmel
Your code is correct! It were my wrong editor settings, after enabling autodetection of UTF8 it looks correct, see png. But there are warnings when compiling with msvc: stream6.cpp(252) : warning C4244: 'return' : conversion from 'ascii_ctype_facet::char_type' to 'char', possible loss of data s

Re: plain text output - how to proceed

2006-09-09 Thread Enrico Forestieri
On Sat, Sep 09, 2006 at 05:50:42PM +0200, Georg Baum wrote: > I believe that this version should work on any OS. I can confirm that with mingw and cygwin the same output as your is generated. -- Enrico

Re: plain text output - how to proceed

2006-09-09 Thread Peter Kümmel
Georg Baum wrote: > Am Dienstag, 5. September 2006 14:35 schrieb Abdelrazak Younes: >> Peter Kümmel wrote: >>> In my ordinary text editor (ultraedit) it doen't loock like a text > file. >> Same for me in wordpad... attached the file. > > Can you please try this updated test program? The screen ou

Re: plain text output - how to proceed

2006-09-09 Thread Georg Baum
Am Dienstag, 5. September 2006 14:35 schrieb Abdelrazak Younes: > Peter Kümmel wrote: > > In my ordinary text editor (ultraedit) it doen't loock like a text file. > > Same for me in wordpad... attached the file. Can you please try this updated test program? The screen output should look like in

Re: plain text output - how to proceed

2006-09-05 Thread Enrico Forestieri
On Tue, Sep 05, 2006 at 02:09:25PM +0200, Georg Baum wrote: > Enrico Forestieri wrote: > > > Georg, I tried your test program on cygwin and, after adding an > > "#include " line, it fails to compile as follows: > > > > $ g++ stream2.cpp -o stream2 > > stream2.cpp: In function `int main()': > > s

Re: plain text output - how to proceed

2006-09-05 Thread Enrico Forestieri
On Tue, Sep 05, 2006 at 02:26:55PM +0200, Peter Kümmel wrote: > Georg Baum wrote: [...] > > std::wcerr should be declared in iostream. If gcc on cygwin does not have it > > then it is not standard conforming. Possibly. The wide stream versions are #ifdef'd out in iostream: #ifdef _GLIBCXX_USE_WC

Re: plain text output - how to proceed

2006-09-05 Thread Abdelrazak Younes
Peter Kümmel wrote: Georg Baum wrote: Abdelrazak Younes wrote: Ah... with this change I have then the same output as yours: test: abcd 228246252 20 e4 f6 fc 196214220 20 c4 d6 dc abcd That looks good, but the generated file is more interesting. Does it contain abcd äöü äöü abcd

Re: plain text output - how to proceed

2006-09-05 Thread Peter Kümmel
Georg Baum wrote: > Enrico Forestieri wrote: > >> Georg, I tried your test program on cygwin and, after adding an >> "#include " line, it fails to compile as follows: >> >> $ g++ stream2.cpp -o stream2 >> stream2.cpp: In function `int main()': >> stream2.cpp:230: error: `wcerr' is not a member of

Re: plain text output - how to proceed

2006-09-05 Thread Georg Baum
Enrico Forestieri wrote: > Georg, I tried your test program on cygwin and, after adding an > "#include " line, it fails to compile as follows: > > $ g++ stream2.cpp -o stream2 > stream2.cpp: In function `int main()': > stream2.cpp:230: error: `wcerr' is not a member of `std' > stream2.cpp:238: er

Re: plain text output - how to proceed

2006-09-05 Thread Enrico Forestieri
On Mon, Sep 04, 2006 at 10:46:43PM +0200, Georg Baum wrote: > Peter and Abdel, can you please test whether the attached test program > works (or could be made to work) on windows with lyx::char_type == > boost::uint32_t? > > If yes, then I'd like to put the attached patch in and proceed with >

Re: plain text output - how to proceed

2006-09-05 Thread Georg Baum
Peter Kümmel wrote: > In my ordinary text editor (ultraedit) it doen't loock like a text file. > Also firefox only shows numbers. Both should recognize utf8 text files. >> encoded in utf8? > How do I check? Please send it (in a .zip archive so that it does not get altered), I'll have a look.

Re: plain text output - how to proceed

2006-09-05 Thread Lars Gullik Bjønnes
Peter Kümmel <[EMAIL PROTECTED]> writes: | Georg Baum wrote: | > Abdelrazak Younes wrote: | > | >> Ah... with this change I have then the same output as yours: | >> | >> test: | >> abcd | >> 228246252 | >> 20 e4 f6 fc | >> 196214220 | >> 20 c4 d6 dc | >> abcd | > | > That looks good, but

Re: plain text output - how to proceed

2006-09-05 Thread Peter Kümmel
Georg Baum wrote: > Abdelrazak Younes wrote: > >> Ah... with this change I have then the same output as yours: >> >> test: >> abcd >> 228246252 >> 20 e4 f6 fc >> 196214220 >> 20 c4 d6 dc >> abcd > > That looks good, but the generated file is more interesting. Does it contain > > abcd >

Re: plain text output - how to proceed

2006-09-05 Thread Georg Baum
Georg Baum wrote: > Abdelrazak Younes wrote: > >> Ah... with this change I have then the same output as yours: >> >> test: >> abcd >> 228246252 >> 20 e4 f6 fc >> 196214220 >> 20 c4 d6 dc >> abcd > > That looks good, but the generated file is more interesting. Does it > contain > > abc

Re: plain text output - how to proceed

2006-09-05 Thread Georg Baum
Abdelrazak Younes wrote: > Ah... with this change I have then the same output as yours: > > test: > abcd > 228246252 > 20 e4 f6 fc > 196214220 > 20 c4 d6 dc > abcd That looks good, but the generated file is more interesting. Does it contain abcd äöü äöü abcd encoded in utf8? Geor

Re: plain text output - how to proceed

2006-09-05 Thread Abdelrazak Younes
Peter Kümmel wrote: Abdelrazak Younes wrote: Georg Baum wrote: Peter and Abdel, can you please test whether the attached test program works (or could be made to work) on windows with lyx::char_type == boost::uint32_t? If yes, then I'd like to put the attached patch in and proceed with solution

Re: plain text output - how to proceed

2006-09-05 Thread Peter Kümmel
Abdelrazak Younes wrote: > Georg Baum wrote: >> Peter and Abdel, can you please test whether the attached test program >> works (or could be made to work) on windows with lyx::char_type == >> boost::uint32_t? >> >> If yes, then I'd like to put the attached patch in and proceed with >> solution 2) a

Re: plain text output - how to proceed

2006-09-05 Thread Abdelrazak Younes
Georg Baum wrote: Peter and Abdel, can you please test whether the attached test program works (or could be made to work) on windows with lyx::char_type == boost::uint32_t? If yes, then I'd like to put the attached patch in and proceed with solution 2) above. With two modifications (include

Re: plain text output - how to proceed

2006-09-04 Thread Peter Kümmel
Georg Baum wrote: > Up to now there have been two proposals how to fix the plain text output: > > 1) from Abdel: Still use narrow streams > > virtual int InsetBase::plaintext(Buffer const &, std::ostream & os, > OutputParams const &) const; > > and implement operators for docstring and char_typ

plain text output - how to proceed

2006-09-04 Thread Georg Baum
Up to now there have been two proposals how to fix the plain text output: 1) from Abdel: Still use narrow streams virtual int InsetBase::plaintext(Buffer const &, std::ostream & os, OutputParams const &) const; and implement operators for docstring and char_type output that convert to utf8: s

Re: How to proceed.

2003-02-09 Thread Lars Gullik Bjønnes
Andre Poenitz <[EMAIL PROTECTED]> writes: | As current CVS identifies itself as "1.4.0cvs" I guess development is open? | | Attached a patch to clean up the os specific stuff by moving from classes | and static functions to namespaces. I sent this already some time ago... | | It certainly works

How to proceed.

2003-02-07 Thread Andre Poenitz
As current CVS identifies itself as "1.4.0cvs" I guess development is open? Attached a patch to clean up the os specific stuff by moving from classes and static functions to namespaces. I sent this already some time ago... It certainly works for *nix as I have it in my tree for a while, but I ca