Date   

Outlook.com keyboard shortcuts

 

Hi all,

After some Googling around, I came across this. http://windows.microsoft.com/en-us/windows/outlook/keyboard-shortcuts

This Microsoft support page lists the available keyboard shortcuts in Outlook.com, so this should help any of you who are concerned about the inability to use WLM2012 after June.

I know change like this is a pain, but...let's face it we all have been through such change. Remember the time when Microsoft announced that it will discontinue Windows Live Messenger? I'm sure many of you have the same feeling of not wanting to change to Skype, but...what can we do when we don't much of a voice...


Re: Fw: Action required for users of Windows Live Mail 2012

Brian's Mail list account BY <bglists@...>
 

So what about other email clients in use, what about older accounts like hotmail.
Luckily I only have one hotmail account.
To me this smacks of centre of the universe syndrome. Best advice seems to be to use another email provider of free emails with eirher a better online interface or still uses pop3 and any old email client.
I use Outlook express and I suspect a lot still do from looking at headers of emails I see here.
If they are going to make a bespoke system they cshould publish how it works so third parties can emulate the protocol on their clients in my view, or expect to be left behind by the m leaving of people who do not want things t change for changes sake.
brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Supanut Leepaisomboon" <supanut2000@outlook.com>
To: <nvda@nvda.groups.io>
Sent: Friday, May 06, 2016 12:23 AM
Subject: [nvda] Fw: Action required for users of Windows Live Mail 2012


Action required for users of Windows Live Mail 2012



From: Outlook
Sent: Friday, May 06, 2016 02:26
To: supanut2000@outlook.com
Subject: Action required for users of Windows Live Mail 2012

Action required for users of Windows Live Mail 2012. Dear User, Earlier this year we announced updates to Outlook.com that will help you collaborate with others, focus on what matters, and get more done.

Action required for users of Windows Live Mail 2012


Dear User,

Earlier this year we introduced a new Outl‍ook‍.‍com that will help you collaborate with others, focus on what matters, and get more done. The new Outlo‍ok‍.‍com delivers an exciting set of new experiences across web, phone, and desktop, and we’re eager for you to start using it.

It appears that you are currently using Windows Live Mail 2012 to connect to your Out‍look‍.‍com account. Windows Live Mail 2012 does not support the synchronization technologies used by the new Outl‍ook‍.‍com. When account upgrades begin at the end of June, you will no longer be able to receive email sent to your Out‍look‍.‍com account in Windows Live Mail 2012. Rest assured, you can always access your email by logging into Out‍look‍.‍com from any web browser, and you will continue to have access to all your data that is currently in Windows Live Mail 2012.

If you currently use Windows Live Mail 2012, we recommend that you switch to the Mail app in Windows to‍day. The Mail app is built in to Windows 8/8.1 and Windows 10, and has a more modern design. To begin using it, simply launch the app and add your Out‍look‍.‍com account.

If you are using Windows 7, you can upgrade to a newer version of Windows to enjoy the Mail app and the other benefits. If you do not wish to upgrade, you can access your account via a web browser, or, you can take advantage of a free one-year subscription of Office 365 Personal, and use Outl‍ook 2016 to connect to your account.* This Off‍ice 365 subscription also includes other productivity applications such as Word, PowerPoint and Excel. It works on Windows 7, Windows 8/8.1, and Windows 10.

Please take action before Ju‍ne 30th, 2016, which is when we’ll begin upgrading accounts that currently use Windows Live Mail 2012. If you have more questions, please find answers to common FAQs in this help article, or you can contact Microsoft support.

We recognize that changes like this can be difficult, and apologize for any inconvenience this causes you. We hope that you’ll enjoy the benefits of moving to the new Outl‍ook‍.‍com.

Sincerely,
Outl‍ook‍.‍com team



*Must redeem by October 15, 2016. Valid for first time Office 365 subscriber. Credit card required; cancel anytime at www.office.com/myaccount. See full terms here.

Microsoft respects your privacy. To learn more, please read our Privacy Statement.
Microsoft Corporation
One Microsoft Way
Redmond, WA 98052


Action required for users of Windows Live Mail 2012. Dear User, Earlier this year we announced updates to Outlook.com that will help you collaborate with others, focus on what matters, and get more done.


Re: NVDA still freezing, don't know what the deal is

Brian's Mail list account BY <bglists@...>
 

Might also be a good idea to create a ticket with it as well, as it could be that they can duplicate the effect.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Pete" <emac00@cogeco.ca>
To: <nvda@nvda.groups.io>
Sent: Thursday, May 05, 2016 10:14 PM
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is



The error that sticks out for me is:
WindowsError: [Error 1775] A null context handle was passed from the
client to the host during a remote procedure call

before you tare up your computer looking for hardware reasons check the visual c++ / number instalations
I don't know how to repair them, since removeing and reinstalling doesn't seem to fix it.


On 5/2/2016 5:30 PM, Kenny Peyattt jr. wrote:
Hi if you want i can forward the log you sent over to the nvda developers li9st.
Kenny Peyatt jr.

On 5/2/2016 3:15 PM, Sharni-Lee Ward wrote:
I forgot to mention that last log was made in the old snapshot I have,
not the official installation. But I would still like a translation of
those errors from someone who understands them better than I do.


On 3/05/2016 2:17 AM, Sharni-Lee Ward wrote:
It just happened AGAIN. This time, with no Braille Display plugged in,
but still in Word. My sister described what she saw as "It's circling
and the screen is foggy," so I'm assuming it was hanging. It took longer
than normal to shut down, and longer than normal to start up properly,
and apparently Windows Explorer lagged for a few seconds. I don't know
how to recover my writing (I tried one of the previous times this
happened by restoring the auto recovery file from the Recycle bin but it
didn't work...).


Anyways, here's the log. I hope this time I can get an answer for why
this is happening. I'm getting seriously concerned at this point.


INFO - __main__ (00:26:15):
Starting NVDA
INFO - core.main (00:26:19):
Config dir: C:\Users\pc\AppData\Roaming\nvda
INFO - core.main (00:26:20):
NVDA version brltbl20160315
INFO - core.main (00:26:20):
Using Windows version 6.1.7601 service pack 1 workstation
INFO - core.main (00:26:20):
Using Python version 2.7.11 (v2.7.11:6d1b6a68f775, Dec 5 2015,
20:32:19) [MSC v.1500 32 bit (Intel)]
INFO - core.main (00:26:20):
Using comtypes version 0.6.2
INFO - external:synthDrivers.ptenglish.SynthDriver.__init__ (00:26:24):
Using eSpeak version 1.48.03 04.Mar.14
INFO - synthDriverHandler.setSynth (00:26:24):
Loaded synthDriver ptenglish
INFO - core.main (00:26:24):
Using wx version 3.0.2.0 msw (classic)
INFO - braille.initialize (00:26:24):
Using liblouis version 2.6.5
INFO - braille.BrailleHandler.setDisplayByName (00:26:24):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - brailleInput.initialize (00:26:24):
Braille input initialized
INFO - core.main (00:26:25):
NVDA initialized
INFO - braille.BrailleHandler.setDisplayByName (00:27:25):
Loaded braille display driver freedomScientific, current display has 40
cells.
ERROR - queueHandler.flushQueue (00:33:30):
Error in func _handleUpdate from eventQueue
Traceback (most recent call last):
File "queueHandler.pyc", line 50, in flushQueue
File "virtualBuffers\__init__.pyc", line 674, in _handleUpdate
File "braille.pyc", line 1645, in handleUpdate
File "braille.pyc", line 906, in update
File "textInfos\offsets.pyc", line 346, in expand
File "virtualBuffers\__init__.pyc", line 314, in _getUnitOffsets
File "textInfos\offsets.pyc", line 328, in _getUnitOffsets
File "virtualBuffers\__init__.pyc", line 256, in _getParagraphOffsets
WindowsError: [Error 1775] A null context handle was passed from the
client to the host during a remote procedure call


On 3/05/2016 12:15 AM, Sharni-Lee Ward wrote:
Just tried another thing that consistently got NVDA to hang recently,
namely, opening the sounds manager in Control Panel and then arrowing to
the Sound Scheme tab. I thought it only did this because of the Braille
Display but I wanted to test it to make sure. This time, once the window
was closed, NVDA started responding again. I also tried to activate
Narrator but it didn't work, though as I said, that didn't end up
mattering. Here's the log for that session, though I warn you, the
warning repeats itself several times. In case each warning was subtly
different, I copied the whole thing. Don't worry about the Braille error
that shows up first—that's about me starting up the computer and by
extension NVDA without my display plugged in and then saving the
configuration with default as No Braille.


INFO - __main__ (18:51:56):
Starting NVDA
INFO - core.main (18:51:59):
Config dir: C:\Users\pc\AppData\Roaming\nvda
INFO - core.main (18:52:00):
NVDA version 2016.1
INFO - core.main (18:52:00):
Using Windows version 6.1.7601 service pack 1 workstation
INFO - core.main (18:52:00):
Using Python version 2.7.11 (v2.7.11:6d1b6a68f775, Dec 5 2015,
20:32:19) [MSC v.1500 32 bit (Intel)]
INFO - core.main (18:52:00):
Using comtypes version 0.6.2
INFO - external:synthDrivers.ptenglish.SynthDriver.__init__ (18:52:10):
Using eSpeak version 1.48.03 04.Mar.14
INFO - synthDriverHandler.setSynth (18:52:11):
Loaded synthDriver ptenglish
INFO - core.main (18:52:11):
Using wx version 3.0.2.0 msw (classic)
INFO - braille.initialize (18:52:11):
Using liblouis version 2.6.5
ERROR - braille.BrailleHandler.setDisplayByName (18:52:11):
Error initializing display driver
Traceback (most recent call last):
File "braille.pyo", line 1447, in setDisplayByName
File "brailleDisplayDrivers\freedomScientific.pyo", line 179, in __init__
RuntimeError: No display found
INFO - braille.BrailleHandler.setDisplayByName (18:52:11):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - brailleInput.initialize (18:52:11):
Braille input initialized
INFO - core.main (18:52:12):
NVDA initialized
INFO - braille.BrailleHandler.setDisplayByName (19:30:34):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - config.ConfigManager.save (19:30:39):
Base configuration saved
WARNING - watchdog._watcher (23:47:35):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:47:50):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:48:05):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:48:20):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:48:35):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:48:50):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:49:05):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:49:20):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

INFO - core.onEndSession (23:54:04):
Windows session ending


On 2/05/2016 7:29 PM, Sharni-Lee Ward wrote:
If the master snapshots fixed it, does this mean the next release (which
is hopefully coming sometime this month or next) will have the fix?
Because if so, I can just change the configuration so I have to connect
it manually when I want to use it, which isn't a problem as I usually
have to re-activate the Braille settings if I have to disconnect the
display for one reason or another, or if the computer's put to sleep. If
the fix is implemented next release, I'll adjust the configuration
again. If it does happen again despite this measure, I will try Gene's
method, although I suspect it will be fine. Thank you everyone for all
your help and tips, and at least I know how to retrieve old log messages
now! :D


On 2/05/2016 7:02 PM, Brian's Mail list account wrote:
I don't think its malware, reading the thread it sounds like the
braill table part of nvda and the master snapshots are supposed to
have now fixed it. Its been a while since I had a computer with one of
those displays. fartoo expensive for the low usage I have.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Arlene" <nedster66@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Monday, May 02, 2016 4:15 AM
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is


Hi there: Do you think your computer could have mellwhere to cause this
freezing?

-----Original Message-----
From: Rob [mailto:captinlogic@gmail.com]
Sent: May-01-16 6:31 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is

Gene <gsasner@ripco.com> wrote:
Why wouldn't my workaround accomplish the same end but more easily.
Because most of the keyboard is frozen when this freeze happens. The
only
thing that works is the windows key and some function keys.










Re: Feature request: List of clickable elements in Elements List dialog and single letter navigation for clickable elements

Bhavya shah
 

Hi Victor,
Thanks for the ticket link. I have added my comment on there.
Thanks.

On 5/6/16, 蔡宗豪 Victor Cai <surfer0627@gmail.com> wrote:
Hi,
Please see 124 for quick navigation key request issue:
https://github.com/nvaccess/nvda/issues/124

Thanks.

Regards

Victor


2016-05-06 12:00 GMT+08:00, Bhavya shah <bhavya.shah125@gmail.com>:
Dear all,
As the subject line quite clearly suggests, my request is to add a
feature in the NVDA Elements List dialog which includes the listing of
clickable elements on the page too. Also, a particular key (which may
remain unassigned by default, if needed) should be able to navigate to
the clickable elements.
Before filing a ticket for the same, I was in doubt if this proposal
had already been brought up in the past or if it is worthy of a new
ticket being filed.
Thanks.

--
Warm Regards
Bhavya Shah
Using NVDA (Non Visual Desktop Access) free and open source screen
reader for Microsoft Windows
To download a copy of the free screen reader NVDA, please visit
http://www.nvaccess.org/
Using Google Talkback on Motorolla G second generation Lollipop 5.0.2
Reach me through the following means:
Mobile: +91 7506221750
E-mail id: bhavya.shah125@gmail.com
Skype id : bhavya.09





--
Warm Regards
Bhavya Shah
Using NVDA (Non Visual Desktop Access) free and open source screen
reader for Microsoft Windows
To download a copy of the free screen reader NVDA, please visit
http://www.nvaccess.org/
Using Google Talkback on Motorolla G second generation Lollipop 5.0.2
Reach me through the following means:
Mobile: +91 7506221750
E-mail id: bhavya.shah125@gmail.com
Skype id : bhavya.09


Re: Fw: Action required for users of Windows Live Mail 2012

 

Well its clear ms are starting to have everything use its apps or not at all.
When I finally do upgrade, I will simply not be using apps because I am not sure which ones will hijack my account to be a ms one.
I don't use outlook.com anyway so thats all fine.
Cortana uses edge which is not fully up there and groove which isn't up there either.
Bing is basically all over ms pages, I use google on everything.

On 6/05/2016 4:05 p.m., Brian Vogel wrote:
Rosemarie Chavarria wrote: "Like the old saying goes, if it ain't broke, don't fix it."

Microsoft and Google both seem to fail to appreciate the timeless nature of this adage. They also tend to break the KISS principle of design on a very frequent basis, too.
Brian
--
Never underestimate the difficulty of changing false beliefs by facts.
~ Henry Rosovsky


Re: Fw: Action required for users of Windows Live Mail 2012

 

Well its no secret that windows live mail is being phased out to be replaced with the mail app, its been no secret for months now.

On 6/05/2016 1:07 p.m., Brian Vogel wrote:
Even I'll say that this is Microsoft trying to force people into a very narrow set of mail access options for e-mail services they own. I wonder what's going to happen to those with any of the Microsoft e-mail accounts (outlook.com, live.com, msn.com, hotmail.com) that are using other e-mail clients. WLM 2012 supports POP and IMAP and those two access methods are what every other e-mail client I know of, including the Win8 and Win10 mail apps, use.

This is a peculiar and stupid move on Microsoft's part.
Brian
--
Never underestimate the difficulty of changing false beliefs by facts.
~ Henry Rosovsky


Re: Fw: Action required for users of Windows Live Mail 2012

Helga Schreiber
 

Hi, this is helga! What od you mean? I use Gmail so you mean it will not work man! Are you serious! NO way! And i use windows live mail 2012. Now what? What email client will i use guys? I will really appreciate any suggestions! Thansk and God bless!

Helga Schreiber 

Member of National Federation of the Blind and Florida Association of Blind Students.
Member of the International Networkers Team (INT).
Independent Entrepreneur of the Company 4Life Research.
Phone:  (561) 706-5950 
Skype: helga.schreiber26 
INT Website: http://int4life.com/ 

"For God so loved the world that he gave his one and only Son, that whoever believes in him shall not perish but have eternal life." John 3:16 
Sent from my iPhone 6S running IOS 9.3.1    

On May 5, 2016, at 11:16 PM, Supanut Leepaisomboon <supanut2000@...> wrote:

[Edited Message Follows]

And, for those who are still believing that the email I received is a phishing email, take a look at this, https://blogs.office.com/2016/05/05/using-windows-live-mail-2012-with-outlook-com-time-to-update-your-email-application/

This is from official Microsoft Office blog, so it's obvious that this is a serious manor and that it is going to happen for real.

Edit: Even Google's Gmail no longer work with WLM2012 unless if you turn off a security setting, which is not a wise thing to do.


Re: Feature request: List of clickable elements in Elements List dialog and single letter navigation for clickable elements

蔡宗豪 Victor Cai
 

Hi,
Please see 124 for quick navigation key request issue:
https://github.com/nvaccess/nvda/issues/124

Thanks.

Regards

Victor


2016-05-06 12:00 GMT+08:00, Bhavya shah <bhavya.shah125@gmail.com>:

Dear all,
As the subject line quite clearly suggests, my request is to add a
feature in the NVDA Elements List dialog which includes the listing of
clickable elements on the page too. Also, a particular key (which may
remain unassigned by default, if needed) should be able to navigate to
the clickable elements.
Before filing a ticket for the same, I was in doubt if this proposal
had already been brought up in the past or if it is worthy of a new
ticket being filed.
Thanks.

--
Warm Regards
Bhavya Shah
Using NVDA (Non Visual Desktop Access) free and open source screen
reader for Microsoft Windows
To download a copy of the free screen reader NVDA, please visit
http://www.nvaccess.org/
Using Google Talkback on Motorolla G second generation Lollipop 5.0.2
Reach me through the following means:
Mobile: +91 7506221750
E-mail id: bhavya.shah125@gmail.com
Skype id : bhavya.09




Re: [TechTalk] Alert Windows Live Mail users, scam email warning

David Moore
 

Hi Helga
Could you change your hotmail account to another gmail or yahoo account? Emails from Yahoo.com could be imported into Windows Live Mail.
 
 

Sent: Friday, May 6, 2016 12:24 AM
Subject: Re: [nvda] [TechTalk] Alert Windows Live Mail users, scam email warning
 
Hi all! This is Helga! How are you all? I use Windows live mail 2012 as my eamil client, so Ishould I change my client? I'm just owndering! On my windows live mail I have my gmail account and hotmail account! So that means I should change to outlook 2016 or what other client is available? I will update my windows 8.1 to windows 10 soon! I look forward for any suggestions! Thanks and God bless!

Helga Schreiber 
 
Member of National Federation of the Blind and Florida Association of Blind Students.
Member of the International Networkers Team (INT).
Independent Entrepreneur of the Company 4Life Research.
Phone:  (561) 706-5950
Skype: helga.schreiber26
INT Website: http://int4life.com/ 
 
"For God so loved the world that he gave his one and only Son, that whoever believes in him shall not perish but have eternal life." John 3:16
Sent from my iPhone 6S running IOS 9.3.1   

On May 6, 2016, at 12:15 AM, Ron Canazzi <aa2vm@...> wrote:

Hi Brian,

 

There are changes, but this address:

Outlo‍ok‍.‍com 

 

is bogus.

 


On 5/5/2016 11:23 PM, Supanut Leepaisomboon wrote:
It's not a spam/phishing email, take a look at this https://blogs.office.com/2016/05/05/using-windows-live-mail-2012-with-outlook-com-time-to-update-your-email-application/

This is real, and...the change will happen, no matter what. To be honest I felt kind of surprised by this, having used WLM for so long.


--
They Ask Me If I'm Happy; I say Yes.
They ask: "How Happy are You?"
I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"


Re: [TechTalk] Alert Windows Live Mail users, scam email warning

 

Helga,

          That second sentence should have read, "keep your hotmail account and your gmail account and have them in a client . . ."  It's getting late.

Brian
-- 

Never underestimate the difficulty of changing false beliefs by facts. 
   ~ Henry Rosovsky

    



Re: [TechTalk] Alert Windows Live Mail users, scam email warning

 

Helga,

          This little caper involves access via WLM 2012 only to those e-mail accounts ending in @outlook.com, @live.com, @msn.com, and @hotmail.com.

          If you wish to keep your hotmail account and have it in a client that can also access e-mail from any of the above noted e-mail addresses then you will have to transition to one of the e-mail clients noted on this support.microsoft.com webpage.


Brian
-- 

Never underestimate the difficulty of changing false beliefs by facts. 
   ~ Henry Rosovsky

    



Re: [TechTalk] Alert Windows Live Mail users, scam email warning

 

The only alternative email client I can think of that will be able to support the new Outlook.com is...Thunderbird. Even though if it suddenly won't work after June, I have confidence that Mozilla will fix it in a new version pretty quickly.


Re: [TechTalk] Alert Windows Live Mail users, scam email warning

Helga Schreiber
 

Hi all! This is Helga! How are you all? I use Windows live mail 2012 as my eamil client, so Ishould I change my client? I'm just owndering! On my windows live mail I have my gmail account and hotmail account! So that means I should change to outlook 2016 or what other client is available? I will update my windows 8.1 to windows 10 soon! I look forward for any suggestions! Thanks and God bless!

Helga Schreiber 

Member of National Federation of the Blind and Florida Association of Blind Students.
Member of the International Networkers Team (INT).
Independent Entrepreneur of the Company 4Life Research.
Phone:  (561) 706-5950 
Skype: helga.schreiber26 
INT Website: http://int4life.com/ 

"For God so loved the world that he gave his one and only Son, that whoever believes in him shall not perish but have eternal life." John 3:16 
Sent from my iPhone 6S running IOS 9.3.1    

On May 6, 2016, at 12:15 AM, Ron Canazzi <aa2vm@...> wrote:

Hi Brian,


There are changes, but this address:

Outlo‍ok‍.‍com 


is bogus.



On 5/5/2016 11:23 PM, Supanut Leepaisomboon wrote:
It's not a spam/phishing email, take a look at this https://blogs.office.com/2016/05/05/using-windows-live-mail-2012-with-outlook-com-time-to-update-your-email-application/

This is real, and...the change will happen, no matter what. To be honest I felt kind of surprised by this, having used WLM for so long.


--
They Ask Me If I'm Happy; I say Yes.
They ask: "How Happy are You?"
I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"


Re: [TechTalk] Alert Windows Live Mail users, scam email warning

 

Ron,

          "Outlook.com" and "outlook.com" both get used, regularly, in Microsoft materials.  That includes on the very official Microsoft support page announcing the change to which I supplied the link (and just did again).

Brian
-- 

Never underestimate the difficulty of changing false beliefs by facts. 
   ~ Henry Rosovsky

    



Re: [TechTalk] Alert Windows Live Mail users, scam email warning

Ron Canazzi
 

Hi Brian,


There are changes, but this address:

Outlo‍ok‍.‍com 


is bogus.



On 5/5/2016 11:23 PM, Supanut Leepaisomboon wrote:
It's not a spam/phishing email, take a look at this https://blogs.office.com/2016/05/05/using-windows-live-mail-2012-with-outlook-com-time-to-update-your-email-application/

This is real, and...the change will happen, no matter what. To be honest I felt kind of surprised by this, having used WLM for so long.


--
They Ask Me If I'm Happy; I say Yes.
They ask: "How Happy are You?"
I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"


Re: [TechTalk] Alert Windows Live Mail users, scam email warning

 

Ron Canazzi wrote:  "Well, then Microsoft phone support is stupid."

This is not news, nor is that observation in any way limited to Microsoft.

Brian
-- 

Never underestimate the difficulty of changing false beliefs by facts. 
   ~ Henry Rosovsky

    



Re: Fw: Action required for users of Windows Live Mail 2012

 

Rosemarie Chavarria wrote: "Like the old saying goes, if it ain't broke, don't fix it."

Microsoft and Google both seem to fail to appreciate the timeless nature of this adage.  They also tend to break the KISS principle of design on a very frequent basis, too.

Brian
-- 

Never underestimate the difficulty of changing false beliefs by facts. 
   ~ Henry Rosovsky

    



Re: Fw: Action required for users of Windows Live Mail 2012

 

Supanut,

         Well, I've never found two-step verification all that necessary for my e-mail.  A strong password is more than enough.  I have had the "allow less secure clients" (or whatever the phrasing is on Gmail) setting selected for years now without ill effect.  It's one of the few e-mail server setups that defaults two-step verification on.

Brian
-- 

Never underestimate the difficulty of changing false beliefs by facts. 
   ~ Henry Rosovsky

    



Re: [TechTalk] Alert Windows Live Mail users, scam email warning

Ron Canazzi
 

Well, then Microsoft phone support is stupid.



On 5/5/2016 11:57 PM, Brian Vogel wrote:
Ron,

          It is not false.  It is posted on Microsoft's own website and is being heavily discussed in the tech press.

          It doesn't get more official than an announcement on support.office.com.

          I also think this is going to backfire on Microsoft and they'll lose a lot of e-mail users.
Brian
-- 
Never underestimate the difficulty of changing false beliefs by facts. 
   ~ Henry Rosovsky


--
They Ask Me If I'm Happy; I say Yes.
They ask: "How Happy are You?"
I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"


Feature request: List of clickable elements in Elements List dialog and single letter navigation for clickable elements

Bhavya shah
 

Dear all,
As the subject line quite clearly suggests, my request is to add a
feature in the NVDA Elements List dialog which includes the listing of
clickable elements on the page too. Also, a particular key (which may
remain unassigned by default, if needed) should be able to navigate to
the clickable elements.
Before filing a ticket for the same, I was in doubt if this proposal
had already been brought up in the past or if it is worthy of a new
ticket being filed.
Thanks.

--
Warm Regards
Bhavya Shah
Using NVDA (Non Visual Desktop Access) free and open source screen
reader for Microsoft Windows
To download a copy of the free screen reader NVDA, please visit
http://www.nvaccess.org/
Using Google Talkback on Motorolla G second generation Lollipop 5.0.2
Reach me through the following means:
Mobile: +91 7506221750
E-mail id: bhavya.shah125@gmail.com
Skype id : bhavya.09