Once you’ve added a webhook, both Moqups comments and thread-status updates (resolved, reopened, deleted) will appear in the designated channel. If you are on our Unlimited Plan, you can connect #channels to your individual Moqups teams by adding multiple webhooks. When you connect your Moqups account to a Slack team, you can add a webhook that pushes Moqups notifications directly to your Slack channels. If you're seeing this problem, and it's not the text-to-speech bug, and it's not Timing, please open a trouble ticket and we'll figure out what's going on.In this article Slack Integration Features However, there is a solution: In Timing's preferences, uncheck the box next to "Advanced Accessibility Tracking." This setting only affects Firefox and Slack, and once it's disabled, Moom will work as expected in those apps. But those features seems to cause inteference with Moom, and it's not something we can do anything about in our code. In Firefox and Slack, Timing uses some features of those APIs to make those apps work well with Timing. Timing uses the Accessibility APIs, as does Moom. However, if you're only seeing the problem in Firefox or Slack, then the likely candidate is the time tracking app Timing.
This FAQ article explains that bug, as well as how to work around it. If this is happening in all your apps, the problem is most likely a long-standing text-to-speech bug.
Or it may resize and move, but not to the chosen size or location. If you're a Firefox or Slack user, you may find Moom behaving oddly in these applications: When you invoke Moom, it may not perform the action you specify.įor example, if you choose a "half left" window from Moom's pop-up palette, the window may move to the left but not resize.
0 kommentar(er)
