On Fri, 15 Jul 2005 14:30:49 -0500 Ron Lau <[EMAIL PROTECTED]> babbled:

> Hi,
> 
> I have an eap file 'pyrrho.eap'
> 
> if I do a :
> 
> $ e_util_eapp_edit pyrrho.eap
> 
> the Eapp Editor gui launches, and it shows the correct Icon (pyrrho.png)
> and:
> 
> 
> App name: Pyrrho Eterm
> Generic info:
> Comments:
> Executable: Eterm -t pyrrho
> Window name:
> Window class Pyrrho-Eterm
> 
> 
> If I launch this eap file from the ibar, the icon in the window border
> is not 'pyrrho.png'.  If I launch the eap gui editor from the window
> border menu 'Edit Icon', the dialog boxes list:
> 
> App name: Eterm
> Generic info:
> Comments:
> Executable: Eterm
> Window name:
> Window class Eterm
> 
> 
> What did I do wrong?

because the only way to KNOW where that window comes from is to look at its
properties. generally most apps set a WM_CLASS property (win name, win class)
run xprop and click on a window and look for WM_CLASS - thats what the app sets.
e uses this to MATCH the window to the .eap - in x remember its CLIENT-SERVER.
the window in x is completely separate from the process and you need to jump
through hoops to try at best to sometimes figure it out. so what u want is to
use Etemr's optiosn to set a different name and set this in the window name
field.

ie
Executable: Eterm -n Pyrrho
Window name: Pyrrho
Window class: Eterm



-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler)    [EMAIL PROTECTED]
裸好多                              [EMAIL PROTECTED]
Tokyo, Japan (東京 日本)


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
enlightenment-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Reply via email to