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 applications from Adobe , like
InDesign , using a plugin we were able to put in the menu to show this
panel.
It acts as the Information Panel from the AppX.
That was a dead end discussion and I have to put the said thing in
action , thats the reason I was asking for "Workaround" but not for
the "Solution" instead.
Thanks
~Rajesh
On Feb 16, 2009, at 12:11 PM, Graham Cox wrote:
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) active and pushing the
AppY back.
I need panel(From AppX) act as a inspector in AppY.
I went through "Windows Programming Guide" ( http://developer.apple.com/documentation/Cocoa/Conceptual/WinPanel/Concepts/ChangingMainKeyWindow.html
)and some google search .
Is there any workaround for this problem ? ( Carbon scares me ).
The elephant in the room here is "why do you need to do this in two
different apps". This is a fundamentally unsupported type of design,
so while there could be a workaround, why do you need to do it this
way at all?
That said if both apps are designed to work hand-in-hand you could
do it using DO or similar, but the window/application activation
behaviour you have described is fundamental to the way Macs work,
you can't fix that (as it ain't broke).
Anecdotally, I was forced to use an app that worked this way
recently (an off-site backup tool) and it was probably the worst Mac
app I've ever had the misfortune to come across, because of
precisely this kind of broken design. It didn't need to be that way,
it was just a very badly conceptualized port from Windows. The
company peddling it couldn't even make it work and in the end we
readily ditched them for another vendor. Cautionary tale.
--Graham
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
