I'm running into a conflict between your Face Window plugin and Aerosys' WYSIWYG Custom Menus plugin, specifically with padding. Aerosys' Main Menu plugin set global padding for all windows. It appears the global window padding setting in the Main Menu plugin overrides the padding set in the Face Window plugin.
I've tried a bunch of troubleshooting steps. It's clear that changing the padding setting in Aerosys' Main Menu global window settings affects the face window. Whatever number the global padding is changed to is clearly reflected in the position of the image in the face window. If it's set to 0, the image is aligned in the top left corner (no padding added).
I'm trying to use Face Window to put the bottom edge of a portrait image against the message window. It's working, except for this padding issue. If I turn off the global padding in Custom Menus, it messes up the menu templates because not all windows allow you to set custom padding. If I turn it on, I get this additional padding I cannot compensate for. I tried deleting the portion of the window width/height formula that adds padding in the Face Window script but that doesn't stop Custom Menu from adding padding to the face window. Changing the window to transparent doesn't help because the face window just knocks out the window below and you get an ugly cutout where the transparent padding overlaps the message window.
I'm trying to figure out the easiest way to resolve this conflict, not knowing very much about programing or scripting myself. I'm guessing the reason this happens is because the new face window is using the base window code, and Custom Menus is editing the padding to that code that then gets pushed into the face window regardless of the padding settings in . I would appreciate if you have advice how to proceed with what looks like a simple fix that I just cannot figure out.
