From: "Andy Willis" <os2-wireless_users@2rosenthals.com>
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding;
        b=kv6Nzd/pdl1UpM+LzSV+cMWJQbsAAnUIUqxd2qEr8KRNaQuWPcRYMIa09dEjcWBRLEdL488FvI47ze3LieZ9RqvE0zJ4q/XHC4bJkiEER6F29RDoZdZV3sSss36gyFf+x1On3+5LbC17mVfL0zo7UZzhX4/u6kibD81SKmphbpo=
Message-ID: <4595AB4D.6000902@gmail.com>
Date: Fri, 29 Dec 2006 16:57:01 -0700
Reply-To:  abwillis1@gmail.com
User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.9a2pre) Gecko/20061221 SeaMonkey/1.5a
MIME-Version: 1.0
To: OS/2 Wireless Users Mailing List <os2-wireless_users@2rosenthals.com>
Subject: Re: [OS2Wireless]Re: xwlan profile access
References: <list-663628@2rosenthals.com>
In-Reply-To: <list-663628@2rosenthals.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Christian Langanke wrote:
> Jerry,
> 
> I just read your mail about this very unusual setup. I can only congrat 
> you for getting this to work, I never tried this ad-hoc stuff.
> Unfortunately, currently there is no way to send a message to the widget 
> from outside. Communication with WPS objects  (here the xcenter), 
> normally takes place via setup strings, REXX code for this would look 
> somewhat like this;
> 
> rc = SysSetObjectData('<XWP_XCENTER>', 'WIDGET=XWireless LAN 
> Monitor(SETPROFILE=myPofile);');
> 
> This would require two things :first a keyword like WIDGET,telling 
> XCenter that the string has to be passed over to the specified xcenter, 
> second, an interface within the Widget API to receive such strings. None 
> of the two is available, while the first isn't a big deal, but the 
> second would be a major change to XWorkplace. As I think the widget 
> concept of XCenter  needs some overhaul anyway, I don't see much sense 
> in implementing such on top of the current concept, but I am not part of 
> that project anyway.
> 
> There is an alternative, of course, wich I can implement on side of 
> XWLAN though. It would be possible to implement a proprietary inter 
> process communication (IPC) between a utility and the active instance of 
> XWLAN. An internal helper executable xwlprf.exe (not explicitely 
> documented) is already part of the package. Among other actions that can 
> be taken, it was intended to have a meaning to activate a profile before 
> XWLAN gets active. It turned out though that this required the PM being 
> initialized, while the requirement was to activate it in textmode, while 
> processing config.sys, so this feature turned out to be quite useless. 
> Moreover, if you try t set the profile with xwlprf while XWLAN is 
> active, it has to refuse to work, as there is no communication yet 
> implemented between the two, and modifying the XWLAN data directly may 
> only be allowed for one program at a time. But I don't see a reason why 
> an IPC couldn't be implemented to let xwlprf communicate with an active 
> widget. This is a larger change though, and I don't expect it to come 
> soon. Nevertheless I will put it onto my todo list, now that I know of a 
> senseful used case :-)
> 
> bye, Christian
> 
This might be a reason to implement my idea of using the systray 
api's.  Then the xwlan runs as an exec and could minimize to the 
system tray.  Then you bypass the xcenter communication issue.
Andy