Ran reformat-code on the tree.
Also merged in Azundris' Escreen patch. It's disabled by default for
the moment pending further testing, but you can enable it manually by
defining ESCREEN.
SVN revision: 6202
Reverted Charles Clancy's shading patch (from the 21st) since it
breaks 24bpp on Linux. Hopefully there is a better fix.
Fixed an ASSERT failure in the buttonbar redraw pointed out by
Laurence J. Lane <ljlane@debian.org>.
Also made multiple buttonbars work properly.
SVN revision: 6182
Redraw the buttonbar properly when moved. Spotted by Azundris
<hacks@azundris.com>.
Also fixed the display of underlining with fonts lacking descent.
SVN revision: 6166
Use safe_print_string() to decode string defines before printing them
in --version output. This fixes Debian bug #143328, submitted by
Tom Gilbert <tom@linuxbrit.co.uk>.
Also removed '~' from the CUTCHARS compiled-in default. (It had
already been removed from the themes.) Makes double-click selection
of URL's easier. Requested by Laurence J. Lane <ljlane@debian.org>.
SVN revision: 6152
I would love to know precisely what combination of cosmic catastrophes
conspired to cause me to not do a test build before committing.
Thanks catalyst.
SVN revision: 5900
Fixed a little-endian bug with 24-bit XImages, added a bit to
init_locale() in an effort to replicate the behavior of the Athena
widgets, and added a -b option to Esetroot based on a patch from
Oliwier Ptak <supergrass@gmx.net>.
SVN revision: 5792
Patches from Paul Brannan <pbranna@clemson.edu>, Klaus Elsbernd
<elsbernd@dfki.uni-kl.de>, and Derrick Moser
<d2moser@calum.csclub.uwaterloo.ca> which appeared while I was away.
Fixes for mouse wheel reporting and reset handling (Paul), Solaris
portability (Klaus), and XIM (Derrick).
Getting ready to release 0.9.2 soonish.
SVN revision: 5745
Fixed a couple remaining bugs in 0.9.1, including that really
annoying problem people keeping whining about where Eterm won't build
without Imlib2. It will now. :P
SVN revision: 5543
All the docs and themes should now be up-to-date. Unless a
showstopping bug turns up in the near future, this is pretty much it
for 0.9.1. Now we just need some testing to make sure there's
nothing horridly wrong.... So you all can test while we finish up
the web site and the backgrounds. :-)
SVN revision: 4919
There is now a new mechanism for dealing with the background image
collection, including a new update script. Please read the newly-
rewritten bg/README.backgrounds for details.
Also, I'm trying to flesh out the Contributors list in that file, but
my memory isn't cooperating. So if you contributed one of the
backgrounds, or know someone who did, please let me know.
SVN revision: 4810
Finally got the selection stuff cleaned up. Hopefully this will be
the last time I have to deal with it for awhile. While I was at it,
I implemented incremental selection transfers. Unfortunately, it
doesn't seem like too many people support it. kedit doesn't, and it's
broken in Emacs (*grumble*). Works in gvim though.
SVN revision: 4784
VA bought some licenses for Insure++, so I've been using it to audit
Eterm. These are just the initial results of the collaboration; there
will most likely be more. So far things are looking pretty good. I
just wish Insure++ had more helpful messages. I'd really love to be
able to track down those reads/writes involving freed pointers that
it claims to have found in Imlib2....
I also had to try and make the build work without MMX. I did so; I
just hope it still works *with* MMX.... =)
SVN revision: 3895
Thanks to continuing help from Sung-Hyun Nam <namsh@lgic.co.kr>, I
finally figured out the double-buffering problem people were seeing.
And as it turns out, his original patch was correct. So now it's
fixed. Many thanks for his assistance.
SVN revision: 3847
Fixed the error message bug I noticed. There's also a big5 fix from
Chung-Yen Chang <candyz@cle.linux.org.tw>, and I got rid of some
tiny memory leaks in the X data, the first of which was noticed by
zed@linuxpower.org.
SVN revision: 3844
Several small changes, like freeing pixmaps which won't be needed
later, reducing the default Imlib2 cache size to 0 bytes (we don't
really use it well), and an image path bugfix spotted by Teodor
Zlatanov <tzz@iglou.com>.
The big change, of course, is the disappearance of libmej and the new
dependency on libast, which is now distributed separately.
SVN revision: 3793
When shaded, rely on Enlightenment rather than X for accurate x/y
position information. This fixes a bug pointed out by Gnea
<gnea@rochester.rr.com>.
SVN revision: 3509
I'm working on some deallocators now. The idea is that when Eterm
exits and memory debugging is on, several routines get called to free
the in-use memory (menus, font cache, etc.) that we still know about.
Anything left after that would be either unavoidable leaks (like
environment variables...read the putenv() man page sometime...sigh)
or genuine memory leaks that need fixing. I'm down to about 4.5K of
leftover malloc'd memory now. Making progress....
SVN revision: 3295
Massive reorganization/rewrite to libmej. It should now be 100%
independent of Eterm. There still may be some gremlins in the memory
debugging code, so don't use too high a number with --debug....
SVN revision: 3282
Color modifiers for images now work once again. Please report any
problems you find with them as soon as possible; I want to get 0.9.1
out the door in the fairly near future since the TODO list for 0.9.2
is already sizeable.
SVN revision: 3241
I think I've finally fixed all those XPolyText8() errors with pixmap
support disabled. Solid color mode buttonbars seem to work now also.
SVN revision: 2907
My attempt to track down the strange X errors have revealed that a
pixmap given to me by Imlib2 is getting freed somehow behind my back.
Probably because this part of Imlib2 hadn't been tested before Eterm
was converted. =P
It doesn't seem to happen in XFree86 4.0; I'm wondering if XFree 4 is
smart enough to detect double-frees of old XID's and just ignore them?
Well, I'm going to have to add some debugging code to Imlib2 and see
if I can track down where it's freeing my pixmaps. But I have some
errands to run first, so I'm going to commit this for now. It
shouldn't actually change any functionality.
SVN revision: 2722
Added new shade/tint routines, including some done in MMX assembly, by
Willem Monsuwe <willem@stack.nl>. Thanks Willem! These should prove
to be faster than the old stuff, probably by quite a bit.
SVN revision: 2595
After getting sick of hearing people whining about the obscure error
messages that resulted from trying to build without pixmap support, I
hacked it until it at least built without it. I also added warnings
to configure.in so that people would know if that happened.
It's still not very happy running that way, which is something I need
to fix. But hopefully it will stop the whining.
Yeah, right. =P
SVN revision: 2590
Added the pixmap beveling support back in so that the glass theme will
work again. Once again, you poor 8 bpp saps are SOL.
I also added the icon support back in, along with a new built-in icon
courtesy of Brian McFee <keebler@sandwich.net>.
SVN revision: 2501
I fixed the problem reported by Joakim Bodin <bodin@dreamhosted.com>
with spawned processes. Also fixed Esetroot as reported by Wayne
Johnson <bigman1@alltel.net>.
Support for buttons higher than 5 was also added to the action
bindings code for those (like me) with IntelliMouse Explorers and
XFree86 4.0. :-)
SVN revision: 2494
This is the initial commit with Imlib2 support. READ THIS CAREFULLY.
There is important information in this commit message that will keep
you from getting screwed.
First off, support for Imlib 1.x is GONE. It is no longer supported
as of now. If you want to continue using it, do NOT install this
version. I tried to support both for awhile, but the code ended up
being way too ugly and hackish. Imlib2 is the future. And trust me,
when you see what we do with this future, you'll be happy for the
switch.
The good news is that most of the basics work. Transparency still
works, and the basic image stuff works. Most users won't notice any
major problems, so long as your Imlib2 is 100% up-to-date.
However, a few things still don't work:
1. Auto mode is a bit broken. You'll get X errors in XFree86 4.0.
Don't use it if you're running XFree 4.
2. Color modifiers for images don't work. At all.
3. Transparency shading/tinting will not work in 8bpp or lower. Life
blows sometimes. Sorry. Time for a real video card. :-)
4. The built-in icon is broken.
5. You WILL need to update your theme.cfg files. The borders on the
horizontal and vertical bar images were incorrect when combined with
the new anti-aliased scaling. The horizontal bars should have a right
border of 3. Vertical bars should have a bottom border of 3. The
menu images should have both right *and* bottom borders of 3. You can
either make those changes by hand, or use the --with-theme-update
option to autogen.sh. Your call.
I think that covers everything I've run into. I will point out that
I don't really take advantage of a lot of the Imlib2 features just
yet. My first priority is to make all the stuff that worked before
work again (or at least the important stuff). Then I'll work on
new features.
So there it is. If you're not ready for it, don't use it. But if you
are, I hope you like it.
SVN revision: 2478
Tint by number or color, and shade by percentage, are now available
via the "\e]6;2;" escape sequence. For example, "\e]6;2;shade;10\a"
will shade the background by 10%. "\e]6;2;tint;lightblue\a" will give
the background a light blue tint. "\e]6;2;shade;sa;30\a" will give a
30% shade to the scrollbar anchor.
SVN revision: 2370
Some further fixes for inline functions, 2 new winop actions, brand
new and improved profiling macros, some miscellaneous fixes for SGI
from Kimball Thurston <kimball@sgrail.com>, and more robust checking
in the pasting code.
SVN revision: 2235
Added a new option. -0 (that's a zero) or --itrans will invoke the
immotile optimization for transparency, so named because it works best
on windows that don't move around much on the desktop. It works even
better for windows that are sticky between desktops. So if you have
logging windows (running tail -f and the like) that are shaded/tinted,
you definitely want to have this. It will even benefit ordinary Eterm
windows, provided you don't move them around a lot. Eterms that do
not change desktops may be better off with the other way; Eterms that
are not shaded or tinted at all will not behave any differently.
Here's the technical explanation for those who are interested. The
old (and still the default) behavior is for Eterm to check to see if
any color modifiers are applied to the image_bg class, and if so, to
make a copy of the *entire* desktop image which is then shaded/tinted
appropriately. It then snapshots a portion of that for the actual
background. This way, if the Eterm window is moved, all the shading
and tinting will have already been done, so all it has to do is grab
another portion of the desktop and use it. However, this involves a
LOT of calculations (one per pixel of the desktop pixmap) on startup
and at every desktop switch.
The immotile optimization is intended to reverse that logic by
optimizing for windows that do not move (hence the term "immotile").
It takes the snapshot of the desktop pixmap and applies any shading
or tinting *after* taking the portion it needs. This requires much
fewer calculations on startup and when changing desktops, but the
entire set of calculations must be repeated whenever the window is
moved. This is fine for small windows or windows that don't move
very often, but that's not always the case. So it is to your
advantage to pick one or the other depending on how you use each
particular theme or window.
Two notes. One, keep in mind that the -0/--itrans option doesn't
*activate* transparency; you still need -O/--trans for that. Two,
this does not affect Eterms with no color modifiers applied to the
background. In that case, Eterm still references the existing
desktop pixmap to save memory.
SVN revision: 2191
This is the first public availability of the work thus far on Eterm
0.9.1. There's quite a bit of new stuff here.
* Added scrollbar thumb support.
* Completely redid the terminfo/termcap stuff. The terminfo file is
now compiled (by tic) and installed by default (unless you specify
--without-terminfo). The config files still say xterm, though,
because some programs (like SLang and GNU mc) use the silly algorithm
of "Is $TERM set to xterm?" to detect mouse reporting support in a
terminal. =P But if you don't ever use xterm, you can use Eterm's
termcap and just name it "xterm" instead. Thanks to Marius Gedminas
<mgedmin@takas.lt> for his patch that started this whole revamp.
* Added the kEsetroot script for KDE users from Dax Games
<dgames@isoc.net>.
* You can now configure the Home and End emulation via --with-home=
and --with-end= options to configure. The --with-terminfo option is
also new, and --enable-xim is now the default.
* Added a new image state, disabled, for when Eterm loses focus. This
is supported by all widgets (well, all those that could possibly be
on screen when Eterm lost focus), even the background image. So you
could actually have all your images darken on focus out and restore
to normal on focus in.
* Widget colors formerly dealt with as colors (menu text color,
scrollbar color, etc.) are now handled by the imageclasses. Each
image state can have a foreground and background color defined. The
current exception is the background image; I hope to add that later.
The foreground is the text color and the background is the object
color (for solid color mode). So menu text color is set by the menu
imageclass. And again, for unfocused colors, use the disabled state
of the imageclass.
* Proportionally-spaced fonts are now handled much better. They are
still forced into evenly-spaced columns (it's a terminal for crying
out loud!) but at least you don't end up with Eterm's wider than your
screen. :-)
* Home on refresh is gone, as is home on echo. It's now much simpler.
There are two options: home on output, and home on input, the former
being a combination of echo and refresh. Also, keypresses that don't
necessarily have corresonding output can trigger a home on input,
like Ctrl-End or whatever...ones that don't have special meaning.
Credit to Darren Stuart Embry <dse@louisville.edu> for pointing out
this issue and the one with "m-" in font names.
* I finally got around to re-merging the new parser stuff from my
work on the Not Game. Closed up some old potential behavior quirks
with theme parsing.
* Added a new escape sequence to fork-and-exec a program. Also added
a scrollback search capability to highlight all occurances of a string
in your scrollback buffer. Use the new "Etsearch" utility to access
it. "Etsearch string" to search for a string, then "Etsearch" by
itself to reset the highlighting.
* And of course, the biggie. Eterm now supports a completely-
customizeable buttonbar. Not a menubar, a buttonbar. It can have an
arbitrary number of buttons, and each button can perform an action,
just like a menuitem. So a button could bring up a menu (like a
menubar) or launch a program (like a launchbar) or perform an
operation (like a toolbar). Each button can have an icon, text, or
both. And you can have buttons left- or right-justified in the
buttonbar. You will eventually be able to have an arbitrary number
of buttonbars, but I'm still working on that.
As with any change this big, things could very easily be broken. So
beware. :-) I have tested this myself, and everything seems to work,
but I can't test every possibility. Let me know if you find anything
that's broken, and enjoy!
SVN revision: 2048