I have bit of prior experience on working with application as
LSUIElement andd seems to be a better option.
Due to time constraint , as a workaround, I made the window :
canBecomeKeyWindow to NO and ordering it to front with no title bar
makes things better.
I will make the changes as requi
On Mon, Feb 16, 2009 at 5:57 AM, rajesh wrote:
> I need panel(From AppX) act as a inspector in AppY.
Not gonna happen unless AppX is an LSUIElement; if AppX is a regular
application, you can't do it. You could perhaps create a a third
LSUIElement application and communicate between it and AppX/A
My first reaction to such a feature was same as your point, but I
can't help the way it is.
I took it for granted to implement it anyway and save some time from
arguing about the design.
I'l give a background why the requirement demand is so evil.
replace "AppY" with one of those applicatio
On 16 Feb 2009, at 9:57 pm, rajesh wrote:
In one of my applications(Say AppX) I have a floating panel, and
there is a AppY with a menu item which tell the AppX to show the
panel.
The obvious problem is panel show up but when click is performed on
it , it makes the entire application(AppX)
Hi All,
In one of my applications(Say AppX) I have a floating panel, and
there is a AppY with a menu item which tell the AppX to show the panel.
The obvious problem is panel show up but when click is performed on
it , it makes the entire application(AppX) active and pushing the AppY
back.
