Re: [Inkscape-devel] Status bar help texts visibility
by Daniel Stiefelmaier
>>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 :)
caliga
18 years, 2 months
WEBFORM
by Caliga
Please note, that the submitter may not read this list
name: Caliga
email: inkscape@...985...
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.
Caliga
18 years, 2 months
Re: [Inkscape-tester] Inkscape UI analysis
by Alexandre Prokoudine
On 9/29/05, cedric GEMY <radar.map35@...8...> wrote:
> If people have ideas, remark or anything to say about this please, go ahead.
100% large screenshots please ;-)
Alexandre
18 years, 2 months
SPDesktop
by MenTaLguY
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...
-mental
18 years, 2 months
SPDesktop
by MenTaLguY
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
automatically collected.
(GC::Managed defaults to SCANNED and AUTO)
-mental
18 years, 2 months
UI::View::Edit
by MenTaLguY
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...
-mental
18 years, 2 months
build error on OS X
by Jon A. Cruz
It's a bit late, but just before heading off to bed I started getting
this error:
if g++-3.3 -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/X11R6/include -I/usr/
X11R6/include/freetype2 -DORBIT2=1 -I/sw/include/glib-2.0 -I/sw/lib/
glib-2.0/include -I/sw/include/orbit-2.0 -I/sw/in\
clude/bonobo-activation-2.0 -I/sw/include/gconf/2 -I/sw/include/
libbonobo-2.0 -I/sw/include/gnome-vfs-2.0 -I/sw/lib/gnome-vfs-2.0/
include -I/usr/X11R6/include -I/usr/X11R6/include/freet\
ype2 -DPOTRACE=\"potrace\" -I/sw/include/glib-2.0 -I/sw/lib/
glib-2.0/include -I/sw/include/pango-1.0 -I/usr/X11R6/include -I/usr/
X11R6/include/freetype2 -I/sw/include/gtk-2.0 -I/sw/inclu\
de/atk-1.0 -I/sw/lib/gtk-2.0/include -I/sw/include/gtkspell-2.0 -I/sw/
include/sigc++-2.0 -I/sw/lib/sigc++-2.0/include -I/sw/include/libxml2
-I/sw/include -I/sw/include/glibmm-2.4 -I/sw/lib\
/glibmm-2.4/include -I/sw/include/pangomm-1.4 -I/sw/include/atkmm-1.6
-I/sw/include/gdkmm-2.4 -I/sw/lib/gdkmm-2.4/include -I/sw/include/
gtkmm-2.4 -I/sw/lib/gtkmm-2.4/include -I../cxxtest\
-Wall -W -Wpointer-arith -Wcast-align -Wsign-compare -
Woverloaded-virtual -Wswitch -Wno-unused-parameter -
D__LONG_DOUBLE_128__ -g -O0 -I/sw/include -MT dialogs/docker.o -MD -
MP -MF "d\
ialogs/.deps/docker.Tpo" -c -o dialogs/docker.o `test -f 'dialogs/
docker.cpp' || echo './'`dialogs/docker.cpp; \
then mv -f "dialogs/.deps/docker.Tpo" "dialogs/.deps/docker.Po"; else
rm -f "dialogs/.deps/docker.Tpo"; exit 1; fi
gc-managed.h: In constructor `Inkscape::NSApplication::Editor::Editor
(int,
char**, bool)':
gc-managed.h:55: error: `static void*
Inkscape::GC::Managed<default_scan,
default_collect>::operator new(long unsigned int,
Inkscape::GC::ScanPolicy =
default_scan, Inkscape::GC::CollectionPolicy = default_collect)
[with
Inkscape::GC::ScanPolicy default_scan = SCANNED,
Inkscape::GC::CollectionPolicy default_collect = AUTO]' is
inaccessible
application/editor.cpp:47: error: within this context
gc-managed.h: In destructor `virtual
Inkscape::NSApplication::Editor::~Editor()
':
gc-managed.h:67: error: `static void Inkscape::GC::Managed<default_scan,
default_collect>::operator delete(void*) [with
Inkscape::GC::ScanPolicy
default_scan = SCANNED, Inkscape::GC::CollectionPolicy
default_collect =
AUTO]' is inaccessible
application/editor.cpp:78: error: within this context
make[2]: *** [application/editor.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
I'm not sure if it's coming up on other platforms the same, so I just
tossed this out in case it's handy.
I'll probably not get a chance to attack it myself till later
tomorrow night.
18 years, 2 months
duplicate menu label
by Arpad Biro
Hi,
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.
Arpad Biro
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
18 years, 2 months
Re: New Inkscape Goals?
by Alan Horkan
> 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.
- Alan
18 years, 2 months
