Forum Discussion
Updates and change logs
Hello, Ben:
I appreciate your response. Some decisions have been very difficult, and we don't make them lightly. The tradeoff is often multiple man-months of effort to implement a feature versus ongoing bug fixes and other features.
With respect to take-control of screen sharing (meaning sending mouse and keyboard events across the wire to a remote computer), we have never supported this in any Lync or Skype for Business product on Mac. Lync 2011 and our web apps on Mac have screen sharing, but do not allow taking control of remote sharing.
For tabbed chat windows, I don't know the history of the momentary feature you describe. Perhaps there was some investigation into supporting it that got rolled back, or perhaps it was a bug. To support tabbed windows correctly requires a significant rearchitecting of the product in order to be able to retrieve past messages to create the history.
I would like to understand your failures with peer-to-peer file sharing. This sounds like we have a bug that needs to be fixed. Are you using the insider build? If so, please submit a bug so we can investigate the logs around the failure. To do that, recreate the problem and then click Help\Report an Issue and fill out the ticket. It may be helpful if whoever you tried to send to/from could do the same, so we can see the logs on both sides of the transfer.
Thanks,
Phil.
Hey Phil,
I hope you do not mind me chiming in here as well. First of all, thank you for taking the time with a more detailed response.
1. Tabbed window - as you mention SfB for Mac was a complete rewrite. Then how come this particular item just was not thought off? Why would anyone think that this is something Mac users would not want, when at the same time Apple has been implementing more features in the OS for tabs. It is available when there is a setting on the server to allow for archiving enabled. Now I can understand that with this disabled, any IM not received in SfB can thus not be shown. But really, why can you not just show the different windows into 1 window with tabs instead? What does that then even have to do with history? This is pure UI right now. And UI which you have already implemented. Right now I IM with multiple people, each IM is in it’s own window. Put it as tabs instead and we would be a lot happier!
2- Glad to hear you’re implementing something to reduce the issue to have multiple conversations with the same person, across multiple chats? Personally. Conversation is coming from person X; I already have a window (preferably tab though) open with person X. Put the IM in there. So many other IM programs seem to be able to do this, weird that MS is having so many issues on this one. And again, with implementing this it would thus end up making it easier for point 1 as well right?
3- Control. Understand what you mean here with limitation. Yet, as the world keeps on moving more to smartphones, tablets, and what else. At some point not having it Windows centric will I think become more critical. Now I am not sure if you mean it means changes to everything SfB (Windows, servers, Mac) or just Mac. If it is Mac, then I would say here as well that this should have been taking into account when rewriting the app for the Mac in the 1st place. If everything else, I can understand this would be quite the undertaking. But maybe one best to be taken sooner rather then later? For the overall SfB platform itself then?
Thank you.
- Ben MorelliNov 06, 2017Brass Contributor
Well... I suppose with this information all of this feature fighting is moot.
https://techcrunch.com/2017/09/25/microsoft-is-going-all-in-on-teams-and-plans-to-phase-out-skype-for-business/
Let's hope Teams will have the tabbed chats and remote control features we need.