How could I modify the default notifications for my google calendar? - notifications

Google by default fires up a notification only 10 mins before. But I want to add more notifications. Like on 30 mins before. One at the time of the event too. Is this possible?
If you refer to the image below, all we see are the notification method. Not even the default value or place to add more reminders? Or is that something available at the event level and not the calendar level?

Yes, it is possible to add more than one notification in one specific event on Google Calendar. To do this, follow these steps below:
Go to your Google Calendar.
Select the event you wanted to have more than one notifications.
Click on Edit event(the pencil icon that you can see on the
upper right of the event selected).
Under Event Details tab, you can see the Add Notification
button.
Click the Add Notification button. On the first drop-down menu,
select the type of notification you want to receive(email or a
pop-up notification message).
To schedule when you want the notification be received/appear,
indicate the specific number of time in the box(or
you can click the up and down arrow as an option), and then
select the unit of time(minutes, hours, days or weeks) you
prefer.
If you want to have another notification/s for one specific event, you
can click the Add Notification button again and do
the same steps from 4-6.
Then click Save.

Related

Vuetify v-select how to call change only when user select an option?

Currently the v-select change event will fires multiple times during user typing keywords.
Is there any event will be only fired if user has select an option or press Enter to select an option.
I don't want the change event be fired during user typing keywords.
V-Select#Events
Unfortunately, it looks like the change event only has a parameter that is the value of selected option. There is not event passed through for you to check what actually raised the change event. However, looking at the link above, there are other events you can use.
There is a keydown event listed here that you might be able to leverage. It takes in a keyboard event, you should be able to check what keyboard event was raise i.e. 'Enter'. There are also other events such as mousedown or mouseup.

Telegram Bot: Add action to keyboard button to add text in the chat inputbox

I have added a Inlinekeyboard button as reply_markup to a chat message, and now as an on click action, i want to add a text in the input box, to make it easy for the user ( the text is part of the input to be given in the conversation).
All I could find is 'switch_inline_query_current_chat', which only supports inline queries
Unfortunately, you can't do it directly at this time. :(
You need to send/edit a message which contains a switch_to_inline_current_chat button, and ask user to click it.
I hope you can make this suggestions to #BotSupport, this would be useful for further developers!

YUI3: Re-fire an event that I stopped from propagating?

I've got a form within a tabview with input fields. If the user changes the input fields, doesn't save, and then tries to change the tab I want to ask them if they want to save changes before the tab is changed. I'm preventing the tab-change from occurring using e.stopPropagation(). I then prompt the user to ask if they want to save their changes, discard them, or cancel. If the user chooses save or cancel I'd like to perform the operation and then change them over to the tab they requested.
Is there a way for me to re-fire the event? Or will I have to extract what tab they were requesting from the event and then manually change the active tab?
I would think that the best way to tackle this issue would be to select the tab programmatically instead of trying to "re-fire" the event somehow.
To select a tab programmatically with tabView, you need to use the selectChild(index) method.

How can I make a button not fire its action on click-through?

The Apple Human Interface Guidelines state that:
An item that provides click-through is one that a user can activate on an inactive window with one click, instead of clicking first to make the window active and then clicking the item. Click-through provides greater efficiency in performing such tasks as closing or resizing inactive windows, and copying or moving files. In many cases, however, click-through could confuse a user who clicks an item unintentionally.
and
Don’t provide click-through for an item or action that:
Is potentially harmful and does not allow the user to cancel it (for example, the Delete button in Mail)
Is difficult or impossible to cancel (such as the Send button in Mail)
Dismisses a dialog without telling the user what action was taken (for example, the Save button in a Save dialog that overwrites an existing file and automatically dismisses the dialog)
Removes the user from the current context (for example, selecting a new item in a Finder column can change the target of the Finder window)
What I want to do is that if the user clicks a specific button it will not send its message unless the window is active (for example, the delete message button in Mail). How can I achieve this? If I need to subclass NSButton that's fine.
Look at the NSView Documentation:
http://developer.apple.com/library/mac/#documentation/Cocoa/Reference/ApplicationKit/Classes/NSView_Class/Reference/NSView.html#//apple_ref/occ/instm/NSView/acceptsFirstMouse:
You need to override acceptsFirstMouse to return TRUE to enable click through.
The default behaviour is not click-through:
The default implementation ignores theEvent and returns NO.
It's possible you have already overridden this method in your code, or in code you have based your code on. Try removing the implementation of acceptsFirstMouse in your code.

How can I tell if a Balloon tip in the system tray has closed?

I have an application that uses a NotifyIcon in the tray to hide/restore the application, as well as pop up notices to the user of application events. My application has a notification queue, and I use the NotificationIcon.BalloonTipClosed event to determine when to reset the balloon and show the next notification (if there's one in the queue).
This method seems to work great in both usual causes (user lets the balloon close itself when it times out, and user clicks "X" in balloon to force it to close), but there's a third case where BalloonTipClosed doesn't get called:
Notification balloon pops up
While it's visible, user right-clicks on notification icon to bring up context menu, causing the balloon to disappear
The BalloonTipClosed event doesn't get triggered in this instance - I figure it's a bug in the framework (I'm using 2.0), but does anybody have an idea around this? If I don't get this event, my application always thinks there's a balloon visible (I have a boolean that prevents it from displaying multiple balloons at once), and it will never show another icon again, as long as it's running.
This belongs as a comment to Aarons answer, but I am not allowed to comment yet.
If you handle the BalloonTipClicked and MouseClick events on the NotifyIcon (as well as the BalloonTipClosed) then you can capture all the ways the balloon can close. The only thing you have to be aware of is that several scenerios will trigger multiple events, so be sure to code around that (something like isClosed = true, and then reset that when a new balloon is displayed).
In the event handler for the BalloonTipClicked Event, I would check to see if the right mouse button was clicked, and if it was set the boolean to false.
Here's what I ended up doing, though I don't particularly like this solution. I added a second timer to the form and set it for 10 seconds. When a notification pops up (when I pop one), I start the timer, and then in BalloonTipClosed, I stop it. If the timer ticks (meaning that BalloonTipClosed hasn't run yet), I display the next tip manually.
The result is that if it hasn't fired yet, I take care of it. However, I'm open to better solutions if anybody has one.
I think this post from Raymond Chen about balloon notifications may help you:
http://blogs.msdn.com/oldnewthing/archive/2009/05/04/9585032.aspx