To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=72116





------- Additional comments from [EMAIL PROTECTED] Fri Dec  1 06:46:18 -0800 
2006 -------
Yeah, just the WM_CLASS res_name.

I've the same goal as everyone else, that there's a consistent atk name for all
the OOo components that are typically launched from soffice -something.

The atk name seems to be just pulled from the WM_CLASS name. And the default
name for gtk apps for the wmclass_name defaults to the prgname, i.e.

static void
gtk_window_init (GtkWindow *window)
{
  ...
  window->wmclass_name = g_strdup (g_get_prgname ());
  window->wmclass_class = g_strdup (gdk_get_program_class ());
  ...
}

The reason that I care, is that without g_set_prgname the default prgname is the
name of the binary, typically soffice.bin, but we have some custom binary
launchers for OOo of swriter.bin, simpress.bin (in issuezilla somewhere or
other) etc which optimize the launching of those components and I want the name
to be the same regardless of which custom launcher is used.

so I suggested using X11SalData::getFrameResName to set the prgname as that ends
up as the wmclass_name by default. It seemed a good idea to make the gtk vclplug
consistent with the traditional gen plugin so that OOo had the same WM
properties regardless of the plugin in use.

So I don't really care what the WM_CLASS res_name is, I just wanted it to not be
different if launched from swriter.bin vs simpress.bin

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to