From: Simon Britnell <simon.britnell@pe...> - 2001-03-25 20:35:03
I had a play with applet resizing over the weekend. We need to add a call
to run_applet to resize the widget containing the socket as well as the
socket. I haven't sent a patch because of the following issue:
What size do we resize to?
I was going to write some code intercepting a window create message to find
the size of the applet window, but that adds a lot of issues about timeouts
and threading which would make the code much more complex and seems to make
the --inside code redundant.
I was also thinking that we could set the applet size to be the same as the
size of the "not running" icon. This would keep the advantages of --inside
and give a measure of control over the actual presented size of the applet.
Finally, we could have a little bit of config information stored including
window size and x,y offset of application under the window. This would allow
us to show an arbitrary part of an underlying app. It would also be
easy(ish) to setup a control panel with a slider to adjust the size and
offset than the icon idea above. This, of course, will add some code to the
filer unless the applet adjustment is setup as a seperate executable.
Another todo item is to add a "stop applet" feature to the icon menu, but
that's somewhat down my list of priorities.
Once I have a decision on what to do about size, I'll make the necessary
changes and post a patch.
From: Thomas Leonard <tal00r@ec...> - 2001-03-26 10:20:53
On Mon, Mar 26, 2001 at 08:27:33AM +1200, Simon Britnell wrote:
> I had a play with applet resizing over the weekend. We need to add a call
> to run_applet to resize the widget containing the socket as well as the
> socket. I haven't sent a patch because of the following issue:
Ah... don't worry about it, it's working now ;-)
(my own fault - that set_usize() for the socket prevented it resizing to
fit the applet later...)
> Another todo item is to add a "stop applet" feature to the icon menu, but
> that's somewhat down my list of priorities.
You can always use System to kill it, too.
Actually, we have a bigger problem with menus - the applet can intercept
button events and bring up its own menu. Currently, you have to click
*just* outside the applet's border to get the panel menu!
Thomas Leonard http://rox.sourceforge.net