James:
Thanks for the information about right-clicking on the sheet tabs to bring
up a menu of sheets. Another best-kept secret (and a useful one at that).
This pretty much obsoletes the spin button and tabs, no? Perhaps just a
clickable header for each sheet would look a little cleaner. (i.e
entations (thus the LADDER sheet).
However, the current UI is good enough for me, with just four adjustments
I'm too {laz|bus}y to code for the moment [more urgent would be to
convert my recent objects to the new properties code], so please ignore at
will :
1) a way to select the
There is already something like this. Right click on the notebook tabs to
get a menu of all sheets. Selecting from it will change to the
appropriate sheet. I use it quite a lot to change sheets because
scrolling the notebook tabs is fairly slow. Changing over to an option
menu in place of the
On Fri, 18 Feb 2000 [EMAIL PROTECTED] wrote:
> IMHO:
>
> Multiple sheets are needed, but only one sheet should be displayed at a time
> within the current frame. Remove the tabs as they tend to give the
> appearance of clutter (and some are hard to understand). Use a drop-down
> selector up to
Previous discussion:
blah, blah, blah ...
>> I was talking with James Cape (of the GNOME UI improvement project) about
>> the dia toolbox (the current situation with a notebook containing heaps
>> of sheets is becomming a problem, UI wise). His suggestion was to have a
>> seperate window for ea
On Fri, 18 Feb 2000, [EMAIL PROTECTED] wrote:
> I thought I might post an update on what I am doing on dia at the moment.
>
> I have commited Lars's properties support patches for the standard
> objects in dia now, so there are a few more objects to try the properties
> stuff on.
Thanks!
> I h
I thought I might post an update on what I am doing on dia at the moment.
I have commited Lars's properties support patches for the standard objects
in dia now, so there are a few more objects to try the properties stuff
on.
I have also changed the selector widgets for int and real properties ov
I have made a few more checkins to do with the property code. First of
all, I added some code to help write property set/get routines using a
table of offsets for properties. Also, now object.h and element.h provide
some macros so you can add the obj_pos, obj_bb, elem_corner, elem_width
and elem
On Mon, 7 Feb 2000, James Henstridge wrote:
> Sometimes a simple offset is not enough -- for instance, with flowchart
> box, one property corresponds to box->text->height, which can't be
> described as an offset in the box structure (although, in this case maybe
> making the Text structure a sin
> Are these masses of tests (in box_[sg]et_props()) really necessary ?
> What about having struct type (ObjectType *) and field offset fields in
> PropDescription, and then let a pair of object_auto[sg]et_props()
> functions handle that automatically ? [there will probably be a need for
> macros
On 5 Feb 2000, Lars Clausen wrote:
> On Sat, 5 Feb 2000, [EMAIL PROTECTED] wrote:
>
> > I just thought I would post something about the code I am working on in
> > dia at the moment -- the properties interfaces.
> >
> > These interfaces give a standard way to programatically get or set
> > prop
On Sat, 5 Feb 2000, Cyrille Chepelov (home) wrote:
> First, congrats, your code passed the "Murphy, first stage" test : it
> worked here (with -march=k6) (I didn't have the time to shake it with
> ElectricFence, though).
>
> On Sat, 5 Feb 2000, James Henstridge wrote:
>
> > I have converted the
On Sat, 5 Feb 2000, [EMAIL PROTECTED] wrote:
> I just thought I would post something about the code I am working on in
> dia at the moment -- the properties interfaces.
>
> These interfaces give a standard way to programatically get or set
> properties (eg. border width, text font, etc) of an ob
First, congrats, your code passed the "Murphy, first stage" test : it
worked here (with -march=k6) (I didn't have the time to shake it with
ElectricFence, though).
On Sat, 5 Feb 2000, James Henstridge wrote:
> I have converted the flowchart/box object over to using the properties
> as a test cas
I just thought I would post something about the code I am working on in
dia at the moment -- the properties interfaces.
These interfaces give a standard way to programatically get or set
properties (eg. border width, text font, etc) of an object in dia. For
more information on this, see some of
15 matches
Mail list logo
