>>I would say, if a help line doesn't fit, it shopuld elipsize in
>>tghe end and an unfolding/folding button should appear. Yes, it
>>would be neat to have it as RFE.
>Hmm, I favor the elipsis + tooltip approach. It's what most other
>stuff does these days in similar situations.
In CorelDraw you can simply "drag" the edge of the status bar higher, so
that it has 2 or more lines. Winamp slides long texts to the left and
right, similar to some car radios :)
Please note, that the submitter may not read this list
submitted the following:
I changed the webform, so that it is now only sent to the list. Therefore, all website editors should read the list...
Please remember to add a CC to the original submitter if you answer to the webform.
I just committed a conversion of the whole UI::View::View hierarchy over
to the collector -- you can't do leaf classes individually and have it
work right. Has to be everything in the hierarchy.
Not 100% sure I got the code straight because it was a very quick job,
but I think so. I'll keep testing.
Important thing for everyone to realize: just like refcounted GObjects
and so forth, GC::Anchored objects start with a "refcount" of one. No
need to refcount them a second time after you create them. I've made
this even more explicit in the CG::Anchored documentation which I would
encourage everyone to read...
I just had a look at the SPDesktop code and noticed that you're not
inheriting from GC::Anchored anymore.
That's not safe. Without the anchor, how is the garbage collector
supposed to know that the SPDesktop shouldn't be collected while
the desktop widget still references it? Remember that the desktop
widget isn't and can't be managed by the collector itself...
If you do switch to manual allocation with the collector like that
in the future, please also switch to GC::Managed<GC::SCANNED,
GC::MANUAL> instead of GC::Managed<>, so the object won't get
(GC::Managed defaults to SCANNED and AUTO)
Okay, whoever decided to derive a view class from Gtk::Window ... that
was NOT a good idea.
I'm open to suggestions how to split Gtk::Window away from it quickly,
because among other things that is preventing us from migrating the
UI::View::View hierarchy to the collector.
The build is broken until this gets fixed...
In the View menu there are two "Show/Hide D_ialogs" entries - one of
them is a submenu, the other is a normal menu entry. The submenu
label should be something else.
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
> vector transforaitons need to be added to prove inkscape is the best
> illustraion package in the world ( it already is but these features are
> a must )
Please don't say things like that or I'll insist you prove it...
... and smack you with a great big fish because talk like that is feeding
the trolls and asking for trouble. Bad, bad, bad.
We look ignorant if we do not know the flaws in Inkscape and if you make
grandiose claims like that you can be damned sure there will be no
shortage of people willing to point them out. Pride comes before a fall.
Don't make the users angry, you wont like them when they are angry.
Don't underestimate the importance of a vibrant community and good word of
mouth. I have seen other projects go sour and developers discouraged from
working on the software because of constant criticism brought on by
unrealistic claims. Careless talk has consequences, better to undersell
inkscape and let the program speak for itself.