Subject: Re: Adding a non-permanent item to the Dock - msg#00084

Previous Message by Date: click to view message preview

Re: Adding a non-permanent item to the Dock

Stuart, It appears you are correct. However, regardless of what value I return from this event, it still expands the window. This is stated in the documentation. Is there a way to remove the event so that it won't get processed by anything else? On Jun 14, 2009, at 2:59 PM, Stuart Smith wrote: Ari Black wrote: Now I'm trying to find the event to catch for when the window is about to be shown again. The closest I got was this: kEventWindowExpand I think you want kEventClassWindow, kEventWindowExpanding. Stuart On 6/13/09 12:02 PM, "carbon-dev-request@xxxxxxxxxxxxxxx" <carbon-dev-request@xxxxxxxxxxxxxxx> wrote: Message: 8 Date: Sat, 13 Jun 2009 07:21:58 -0400 From: Ari Black <sarashinai@xxxxxxxxx> Subject: Re: Adding a non-permanent item to the Dock To: carbon-dev@xxxxxxxxxxxxxxx Message-ID: <D6F16C8E-0E94-405C-8BF6-A51F6F158323@xxxxxxxxx> Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes On 2009-05-31, at 03:17:21, Ari Black wrote: I've been reading the past list messages and primarily the question regarding adding items to the Dock is how to programmatically add an application to the dock (similar to adding to the Window's Start Menu or QuickLaunch), thus having the item remain until it's pulled off by the user. My question is, is it possible, through Accessibility or some other API, to add a non-permanent item (like a minimized window) to the Dock? This item would only be present while my application was running, but it would be independent of any window and of my application's own Dock icon. The problem with the type of solution using the Dock's property list (e.g. <http://www.macosxhints.com/article.php?story=20071101055329470&mode=print ) is that you would have to 'killall' the dock both on application launch and quit and that won't be acceptable as an application behavior. Furthermore, it's not possible to trap a kill signal to your app and so the dock would be left in a state of disrepair if that happens. Secondly, what do you intend to have this pseudo dock item do when it is clicked on and what will the label text show? Maybe the only way is to use a custom window as a proxy. The description would be approximately: - It draws itself according to the shape you would like to see in the dock. - When the app launches (or whenever appropriate) the window is created but is not shown. - The app then sends a 'collapse' event to the window and sets the window to be visible so that its representation is shown in the Dock. - If the dock item of the window is clicked on, then it's handler traps the 'expand' event and does whatever. Philip Aker echo astwta@xxxxxxxxx@nl | tr a-z@. p-za-o.@ Democracy: Two wolves and a sheep voting on lunch. _______________________________________________ Do not post admin requests to the list. They will be ignored. Carbon-dev mailing list (Carbon-dev@xxxxxxxxxxxxxxx) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/carbon-dev/sarashinai%40gmail.com This email sent to sarashinai@xxxxxxxxx Maybe someone can shed some light on this. I've been pursuing Philip suggestion (above) and hit a snag. I have created the window and "collapsed" it to the Dock (an aside, it seems the window has to be shown before it can be collapsed to the dock). Now I'm trying to find the event to catch for when the window is about to be shown again. The closest I got was this: kEventWindowExpand If the window is collapsed, this event is sent by the standard window handler after it has receivedkEventWindowClickCollapseRgn and received true from a call to TrackBox. The default response is to call CollapseWindow, then send kEventWindowExpanded. Note that you will not receive this event before a window is expanded from the dock, since minimized windows in the dock don‚t uses collapse boxes to unminimize. The problem is the comment "since minimized windows in the dock don‚t uses collapse boxes to unminimize". Does anyone know of the event that occurs before the window is shown when its minimized version is clicked on the Dock? Thank you. ------------------------------ _______________________________________________ Do not post admin requests to the list. They will be ignored. Carbon-dev mailing list (Carbon-dev@xxxxxxxxxxxxxxx) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/carbon-dev/sarashinai%40gmail.com This email sent to sarashinai@xxxxxxxxx _______________________________________________ Do not post admin requests to the list. They will be ignored. Carbon-dev mailing list (Carbon-dev@xxxxxxxxxxxxxxx) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/carbon-dev/maillists%40codeha.us This email sent to maillists@xxxxxxxxx

Next Message by Date: click to view message preview

Re: How can we mount and unmount dmg files on MAC OS X?

I believe the current recommended way is to get a plist of options from hdiutil with -plist. On Jun 12, 2009, at 2:48 AM, vvvsn murthy wrote: Thanks for your valuable input. Please tell me whether Disk Arbitration supports all the options provided by command line tool. If so can you please help me by sending any relevant info on it? --- Sincerely, Rosyna Keller Technical Support/Carbon troll/Always needs a hug Unsanity: Unsane Tools for Insanely Great People It's either this, or imagining Phil Schiller in a thong. _______________________________________________ Do not post admin requests to the list. They will be ignored. Carbon-dev mailing list (Carbon-dev@xxxxxxxxxxxxxxx) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/carbon-dev/maillists%40codeha.us This email sent to maillists@xxxxxxxxx

Previous Message by Thread: click to view message preview

Re: Adding a non-permanent item to the Dock

Stuart, It appears you are correct. However, regardless of what value I return from this event, it still expands the window. This is stated in the documentation. Is there a way to remove the event so that it won't get processed by anything else? On Jun 14, 2009, at 2:59 PM, Stuart Smith wrote: Ari Black wrote: Now I'm trying to find the event to catch for when the window is about to be shown again. The closest I got was this: kEventWindowExpand I think you want kEventClassWindow, kEventWindowExpanding. Stuart On 6/13/09 12:02 PM, "carbon-dev-request@xxxxxxxxxxxxxxx" <carbon-dev-request@xxxxxxxxxxxxxxx> wrote: Message: 8 Date: Sat, 13 Jun 2009 07:21:58 -0400 From: Ari Black <sarashinai@xxxxxxxxx> Subject: Re: Adding a non-permanent item to the Dock To: carbon-dev@xxxxxxxxxxxxxxx Message-ID: <D6F16C8E-0E94-405C-8BF6-A51F6F158323@xxxxxxxxx> Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes On 2009-05-31, at 03:17:21, Ari Black wrote: I've been reading the past list messages and primarily the question regarding adding items to the Dock is how to programmatically add an application to the dock (similar to adding to the Window's Start Menu or QuickLaunch), thus having the item remain until it's pulled off by the user. My question is, is it possible, through Accessibility or some other API, to add a non-permanent item (like a minimized window) to the Dock? This item would only be present while my application was running, but it would be independent of any window and of my application's own Dock icon. The problem with the type of solution using the Dock's property list (e.g. <http://www.macosxhints.com/article.php?story=20071101055329470&mode=print ) is that you would have to 'killall' the dock both on application launch and quit and that won't be acceptable as an application behavior. Furthermore, it's not possible to trap a kill signal to your app and so the dock would be left in a state of disrepair if that happens. Secondly, what do you intend to have this pseudo dock item do when it is clicked on and what will the label text show? Maybe the only way is to use a custom window as a proxy. The description would be approximately: - It draws itself according to the shape you would like to see in the dock. - When the app launches (or whenever appropriate) the window is created but is not shown. - The app then sends a 'collapse' event to the window and sets the window to be visible so that its representation is shown in the Dock. - If the dock item of the window is clicked on, then it's handler traps the 'expand' event and does whatever. Philip Aker echo astwta@xxxxxxxxx@nl | tr a-z@. p-za-o.@ Democracy: Two wolves and a sheep voting on lunch. _______________________________________________ Do not post admin requests to the list. They will be ignored. Carbon-dev mailing list (Carbon-dev@xxxxxxxxxxxxxxx) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/carbon-dev/sarashinai%40gmail.com This email sent to sarashinai@xxxxxxxxx Maybe someone can shed some light on this. I've been pursuing Philip suggestion (above) and hit a snag. I have created the window and "collapsed" it to the Dock (an aside, it seems the window has to be shown before it can be collapsed to the dock). Now I'm trying to find the event to catch for when the window is about to be shown again. The closest I got was this: kEventWindowExpand If the window is collapsed, this event is sent by the standard window handler after it has receivedkEventWindowClickCollapseRgn and received true from a call to TrackBox. The default response is to call CollapseWindow, then send kEventWindowExpanded. Note that you will not receive this event before a window is expanded from the dock, since minimized windows in the dock don‚t uses collapse boxes to unminimize. The problem is the comment "since minimized windows in the dock don‚t uses collapse boxes to unminimize". Does anyone know of the event that occurs before the window is shown when its minimized version is clicked on the Dock? Thank you. ------------------------------ _______________________________________________ Do not post admin requests to the list. They will be ignored. Carbon-dev mailing list (Carbon-dev@xxxxxxxxxxxxxxx) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/carbon-dev/sarashinai%40gmail.com This email sent to sarashinai@xxxxxxxxx _______________________________________________ Do not post admin requests to the list. They will be ignored. Carbon-dev mailing list (Carbon-dev@xxxxxxxxxxxxxxx) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/carbon-dev/maillists%40codeha.us This email sent to maillists@xxxxxxxxx

Next Message by Thread: click to view message preview

How to explicitly have a socket such that no one else can use that when we use?

Hi All,   I have a socket value with me which I use for various purposes. However other resources trying to access the same socket puts delay on my request. How can prevent this behavior?   Any pointers will be a great help.   Thanks Rahul DISCLAIMER ========== This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails. _______________________________________________ Do not post admin requests to the list. They will be ignored. Carbon-dev mailing list (Carbon-dev@xxxxxxxxxxxxxxx) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/carbon-dev/maillists%40codeha.us This email sent to maillists@xxxxxxxxx