Skip to content
#

communication

Here are 975 public repositories matching this topic...

Kap
eppsilon
eppsilon commented Sep 27, 2019

macOS version:
10.14.6 (18G95)

Kap version:
3.0.0-beta.6

Other possibly relevant info:
Monitor setup: single rMBP 15" screen, no external monitors
macOS scrollbar appearance setting: "Show Always" (in System Preferences > General)

Steps to reproduce

  1. Click the Kap menu bar icon.
  2. Click the button in the Kap bar to record an area of the screen.
  3. Select a regio
cketti
cketti commented Dec 1, 2019

Right now we just launch the MessageList Activity after an account has been successfully set up. This will display the default account. But we should display the Inbox of the newly added account instead.

The relevant code can be found in AccountSetupNames.onNext().

Launching the message list with the default folder of a specific account is a common action and should have a static helper

fulldecent
fulldecent commented Oct 4, 2016

We should have a common format for describing tunes (series of beeps) across the different implementations in this repository. Extensive searching was done, a simple widespread standard was not found.

Following is proposed:

  1. Simple text file
  2. Each line represents a beep or a pause
    1. Column one is a positive integer number of milliseconds
    2. Column two is a positive integer freque
annakirkpatrick
annakirkpatrick commented Aug 15, 2019

This is a really minor issue, but hopefully will also be an easy fix.

Because of recent physical workspace set up changes, I've been experimenting with docking Optikey to the bottom of my screen (rather than the top, as has been my preference in the past).

With Optikey set up this way (docked to the bottom), the expand dock and collapse dock icons on the mouse keyboard appear to be drawn for

wexman
wexman commented Feb 12, 2020

I noticed that the "certificate weakening" TlsOptions like IgnoreCertificateChainErrors, IgnoreCertificateRevocationErrors, AllowUntrustedCertificates and CertificateValidationCallback have no effect when using web socket connections.

I understand this is because the underlying api (System.Net.WebSockets) does not support this (at least not in all target frameworks), but I think it should be no

za3ter2p
za3ter2p commented Feb 1, 2020

Im scrolling and read i2pd.console and read stuff like:

[trust]
## Enable explicit trust options. false by default
# enabled = true
## Make direct I2P connections only to routers in specified Family.
# family = MyFamily
## Make direct I2P connections only to routers specified here. Comma separated list of base64 identities.
# routers = 
## Should we hide our router from other route
pattacini
pattacini commented Dec 24, 2019

Describe the bug
The device controlboard has been deprecated in favor of controlboardwrapper2. Therefore, the documentation available at http://www.yarp.it/yarp_without_yarp.html that relies on controlboard for the test scenario needs to be updated accordingly.

To Reproduce
Launch:

$ yarpdev --device controlboard --subdevice test_motor --name /motor --axes 5

**Sc

Improve this page

Add a description, image, and links to the communication topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the communication topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.