> QBrowseBox ... is there a good reason you didn't extend / base it on
> iconpalette.C ?
the reason I used it was that is was also used in klyx for the toolbars. on a
toolbar button click it can popup wait for a click and dissapear. so i guess
i was anticipating on it to be used as well for the
On Wed, Nov 13, 2002 at 06:44:17PM +1000, Allan Rae wrote:
> P.S. I may have time to look at temp_bullets -> controller
> tomorrow and maybe even make Qt port work in the "standard" manner if
> someone hasn't got it doing that by then.
Would be nice if you did that...
Andre'
--
Those who desire
On Wed, 13 Nov 2002, Andre Poenitz wrote:
> On Wed, Nov 13, 2002 at 06:32:08PM +1000, Allan Rae wrote:
> > I'm still unsure what that gets us. You know what the math parser
> > does. I don't -- other than to guess it creates math insets which
> > Bullets are not (they aren't even insets).
>
> It
On Wed, Nov 13, 2002 at 06:32:08PM +1000, Allan Rae wrote:
> I'm still unsure what that gets us. You know what the math parser
> does. I don't -- other than to guess it creates math insets which
> Bullets are not (they aren't even insets).
It basically creates a MathArray, i.e. a some container.
On Wed, 13 Nov 2002, Andre Poenitz wrote:
> On Wed, Nov 13, 2002 at 05:59:56PM +1000, Allan Rae wrote:
> > On Wed, 13 Nov 2002, Andre Poenitz wrote:
> >
> > > Can't we (ab)use mathed for the bullets? The validate() would come for
> >
> > How?
>
> Don't know. I don't really know where and how the b
On Wed, Nov 13, 2002 at 05:59:56PM +1000, Allan Rae wrote:
> > Can't we (ab)use mathed for the bullets? The validate() would come for
>
> How?
With current CVS Bullet validation might be implemented as
#include "mathed/math_data.h"
Bullet::validate(LaTeXFeatures & features) const
{
asA
On Wed, Nov 13, 2002 at 05:59:56PM +1000, Allan Rae wrote:
> On Wed, 13 Nov 2002, Andre Poenitz wrote:
>
> > Can't we (ab)use mathed for the bullets? The validate() would come for
>
> How?
Don't know. I don't really know where and how the bullets are drawn...
> If you want real strings all the
On Wed, 13 Nov 2002, Andre Poenitz wrote:
> Can't we (ab)use mathed for the bullets? The validate() would come for
How?
> free, and we could store real strings as the parser is already there.
Hmmm... we have strings now. It's just we choose to let the user have
free rein -- and what works now
On Wed, Nov 13, 2002 at 05:37:48PM +1000, Allan Rae wrote:
> Or as a minimal tweak move the params.temp_bullets to the
> dialog/controller.
This sounds ok to me.
Andre'
--
Those who desire to give up Freedom in order to gain Security,
will not have, nor do they deserve, either one. (T. Jefferso
On Wed, 13 Nov 2002, Andre Poenitz wrote:
> On Wed, Nov 13, 2002 at 01:22:53PM +1000, Allan Rae wrote:
> > It's what is already done. The temporary variables could have been
> > kept in the dialog implementation but by keeping them in the buffer
> > params when you switch buffers you got (past te
On Wed, Nov 13, 2002 at 01:00:48PM +1000, Allan Rae wrote:
> Indeed there are 216 bullets and while the majority of these are
> either dingbats from the pifont package or available by default from
> latex there are a number of other symbols that were collected from
> different packages. The closes
On Wed, Nov 13, 2002 at 01:22:53PM +1000, Allan Rae wrote:
> It's what is already done. The temporary variables could have been
> kept in the dialog implementation but by keeping them in the buffer
> params when you switch buffers you got (past tense because it looks
> like someone has changed it)
On Tue, 12 Nov 2002, Edwin Leuven wrote:
> Allan,
>
> What are these for in bufferparams?
>
> boost::array temp_bullets;
>
> Sorry if I am being thick.
They are used as temporary storage by the GUI frontend -- well XForms
anyway as seen here:
void FormDocument::ChoiceBulletSize(FL_OBJECT * ob, l
On Tue, 12 Nov 2002, Edwin Leuven wrote:
> > > I can preview newfile9 but not newfile10. Does anyone know what is wrong
> > > here?
> >
> > \usepackage{pifont}
> > (for \ding{118}) is missing in the preamble.
> ah!
>
> > XForms' dialog inserts it.
>
> no it doesn't. these bullets are usually not s
On Tue, 12 Nov 2002, Edwin Leuven wrote:
> On Tue Nov 12, 2002 05:22, Allan Rae wrote:
> > The thing is the bullet tabs were always supposed to have the current
> > bullet "pushed" for whatever level you were setting (ie. the
> > pseudo-push-button was supposed to be indented but that never worked
On Mon, Nov 11, 2002 at 01:14:26AM +0100, Edwin Leuven wrote:
> For some reason QBrowseBox doesn't get mouse focus. It does when one hold the
QBrowseBox ... is there a good reason you didn't extend / base it on
iconpalette.C ?
> I need to set the bullet codes. for now I have put them in the new
On Tue, Nov 12, 2002 at 11:47:59AM +, Edwin Leuven wrote:
>
Indeed.
Andre'
--
Those who desire to give up Freedom in order to gain Security,
will not have, nor do they deserve, either one. (T. Jefferson)
> > I can preview newfile9 but not newfile10. Does anyone know what is wrong
> > here?
>
> \usepackage{pifont}
> (for \ding{118}) is missing in the preamble.
ah!
> XForms' dialog inserts it.
no it doesn't. these bullets are usually not saved as strings. at the moment
qt saves them as strings. if
Am Dienstag, 12. November 2002 11:57 schrieb Edwin Leuven:
> I can preview newfile9 but not newfile10. Does anyone know what is wrong
> here?
\usepackage{pifont}
(for \ding{118}) is missing in the preamble. XForms' dialog inserts it.
Jürgen.
I've commited the stuff I had. Remaining issue is the one below...
On Tue Nov 12, 2002 10:57, Edwin Leuven wrote:
> I can preview newfile9 but not newfile10. Does anyone know what is wrong
> here?
>
> Thanks, Ed.
I can preview newfile9 but not newfile10. Does anyone know what is wrong here?
Thanks, Ed.
#LyX 1.2 created this file. For more info see http://www.lyx.org/
\lyxformat 220
\textclass amsart-seq
\language english
\inputencoding auto
\fontscheme default
\graphics default
\paperfontsize 11
\spacing o
Allan,
What are these for in bufferparams?
boost::array temp_bullets;
Sorry if I am being thick.
Thanks, Ed.
On Tue, Nov 12, 2002 at 10:32:13AM +, Edwin Leuven wrote:
> > Should be changed, though. Adds simplicity and flexibility...
I meant "Should be changed - but not now".
> would make my life a bit simpler yes. although for the moment the bulletLaTeX
> doesn't preserve the size:
>
> \bulletLaT
On Tue Nov 12, 2002 08:54, Andre Poenitz wrote:
> On Tue, Nov 12, 2002 at 09:48:16AM +, Edwin Leuven wrote:
> > I was wondering btw why you didn't store the bullet as a string in
> > general. what's the advantage of storing it as a font/char combination?
>
> Probably no parser for the string ex
> Still problems with QBrowseBox?
nope :-)
>If so, then why not apply what you have
> (it's broken anyway), then I can probably have a look (note that I have not
> tested my patch from yesterday with your recent changes).
I'll apply then...
On Tue, Nov 12, 2002 at 09:48:16AM +, Edwin Leuven wrote:
> I was wondering btw why you didn't store the bullet as a string in general.
> what's the advantage of storing it as a font/char combination?
Probably no parser for the string exist(s|ed)...
Should be changed, though. Adds simplicity
Edwin Leuven wrote:
> Applying bullets is still rotten though, so I won't apply for the moment.
Still problems with QBrowseBox? If so, then why not apply what you have (it's
broken anyway), then I can probably have a look (note that I have not tested
my patch from yesterday with your recent chan
On Tue Nov 12, 2002 05:22, Allan Rae wrote:
> The thing is the bullet tabs were always supposed to have the current
> bullet "pushed" for whatever level you were setting (ie. the
> pseudo-push-button was supposed to be indented but that never worked
> because of limitations in the image map thingy.
On Mon, 11 Nov 2002, Andre Poenitz wrote:
> On Mon, Nov 11, 2002 at 01:33:04PM +, Edwin Leuven wrote:
> > > Does this count as comment? ;-)
> >
> > I guess not ;-)
> >
> > At the moment the various bullets are put/defined in static strings
> > within the Bullet class. If you have a look in Bul
> Fix attached.
Thanks!
Applying bullets is still rotten though, so I won't apply for the moment.
Cheers, Ed.
Edwin Leuven wrote:
> For some reason QBrowseBox doesn't get mouse focus.
Fix attached.
(Have a look at
http://doc.trolltech.com/3.0/qscrollview.html#details
for details)
Regards,
Jürgen.
Index: src/frontends/qt2/QBrowseBox.C
===
RC
> Your bulletstring.[hC] approach looks ok to me.
I'll commit then.
Thanks, Ed.
On Mon, Nov 11, 2002 at 01:51:43PM +, Edwin Leuven wrote:
> > You need the strings?
>
> yep
Your bulletstring.[hC] approach looks ok to me.
Andre'
--
Those who desire to give up Freedom in order to gain Security,
will not have, nor do they deserve, either one. (T. Jefferson)
> I wonder why such a bullet can't be a thin wrapper around a std::string
> like "\ding{49}"? Is this just a performance enhancement?
don't ask me
> You need the strings?
yep
On Mon, Nov 11, 2002 at 01:33:04PM +, Edwin Leuven wrote:
> > Does this count as comment? ;-)
>
> I guess not ;-)
>
> At the moment the various bullets are put/defined in static strings
> within the Bullet class. If you have a look in Bullet.C you will see this
> in bulletEntry(int,int).
I
> Does this count as comment? ;-)
I guess not ;-)
At the moment the various bullets are put/defined in static strings within the
Bullet class. If you have a look in Bullet.C you will see this in
bulletEntry(int,int).
Thing is that I need them so that users can set custom bullets using the UI.
On Mon, Nov 11, 2002 at 01:05:00PM +, Edwin Leuven wrote:
> > 2. the bullets
> >
> > I need to set the bullet codes. for now I have put them in the new files
> > bulletstrings.[Ch]. I don't know what is best. move them out of bullet.[Ch]
> > to tex-strings[Ch]?
>
> could someone comment on thi
> 2. the bullets
>
> I need to set the bullet codes. for now I have put them in the new files
> bulletstrings.[Ch]. I don't know what is best. move them out of bullet.[Ch]
> to tex-strings[Ch]?
could someone comment on this before I commit (it's not qt related)
Thanks, Ed.
Ok, a first go at the bullets in the qt document dialog.
Some issues are still unresolved:
1. mouse focus.
For some reason QBrowseBox doesn't get mouse focus. It does when one hold the
left mouse butten pressed. If I put the widget in a popupmenu outside lyx
there is no such problem. Qt exper
39 matches
Mail list logo
