syncsign 0.4.1 → 0.4.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: ecfc03f1b6335088ff04e9bbe56a78fd1942569b30ffb07e6a5a0094d8451a3e
-  data.tar.gz: cdd719e880cc9117d0dde045956c4e299a8de5c3fb4952a9aff5305c6d1ff1ea
+  metadata.gz: 4574f4a41e361efb3c930e259b9bd99ffba55989fb6d0a314fed51d8d93c5a56
+  data.tar.gz: 890c60254cd507474fc13de8a163c131385b9f38c5408b16e37f92e680668fd7
 SHA512:
-  metadata.gz: 6e1e58973658b2fcc66b8cf538b123d9554f32966022689bf316f23592acf17241762034fc7c7082063e9099663dd75f55a1beec14e808dbff340e0508840dfc
-  data.tar.gz: 6f5ec20b8eda95908fd34a2012f108b16f623b97dec137a31eff4fca41d87387279ca4196b9f83608e59812ce29ab61d045f363962aec2e76d0f547a3c4c3544
+  metadata.gz: 033cfd91cc3e501b61e8ef2e27028728b174c614b19a8ad2f2d60cc98489e261942773a2fba702a18a3725e6ac3caeb441c94da5eaa400d3a5a2f4ac745df5d1
+  data.tar.gz: 5daf0bead45f71423ca9d7b8b58549a26b2fb02ea6f1373ea235f5e83eb00cb53b1509b457553f64595a7855be25f19baec825ebc75d2a44cef0914d88a3424a

data/README.md

@@ -5,7 +5,7 @@
 Ruby class/gem to access the [SyncSign](http://sync-sign.com) cloud service to display information on e-paper displays.
 
 ## Features
- * Display circles, lines, rectangles, QR codes, and text on the displays.
+ * Display circles, lines, rectangles, QR codes, symbols, text, and more on the displays.
  * Obtain information about associated hubs and displays.
 
 ## TODO
@@ -29,7 +29,7 @@ Create a SyncSign Service instance using your API key (found in the SyncSign por
     node.render(template: template)
 
 ## Direct Rendering
-The SyncSign hubs have a simplified API that can be used, bypassing the cloud service. This can result in significant time savings (15s vs 25s) as well as less time between sending the request and the first visible change on the display. This is especially useful for the 4.2" model with buttons, as the time a user spends waiting after pressing a button can be significantly reduced.
+The SyncSign hubs have a simplified API that can be used, bypassing the cloud service. This can result in significant time savings (15s vs 25s in one example) as well as less time between sending the request and the first visible change on the display. This is especially useful for the 4.2" model with buttons, as the time a user spends waiting after pressing a button can be significantly reduced.
 
 To enable direct rendering, create a file named signhubs.cfg in either the same directory as your app, the current directory, or /etc/signhubs.cfg. This file should have the following format:
 hub-serial-nbr  hub-ip  hub-apikey

data/lib/syncsign/version.rb

@@ -1,4 +1,4 @@
 module SyncSign
   # The version number of the SyncSign module.
-  VERSION = '0.4.1'
+  VERSION = '0.4.2'
 end

data/lib/syncsign/widgets/circle.rb

@@ -36,6 +36,7 @@ module SyncSign
           'type': 'CIRCLE',
           'data': {
             'center': {x: @x, y: @y},
+            'radius': @radius,
             'fillColor': @bgcolour.to_s.upcase,
             'fillPattern': @fillpattern.to_s.upcase,
             'strokeColor': @colour.to_s.upcase,

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: syncsign
 version: !ruby/object:Gem::Version
-  version: 0.4.1
+  version: 0.4.2
 platform: ruby
 authors:
 - sarahemm
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2020-08-30 00:00:00.000000000 Z
+date: 2021-11-06 00:00:00.000000000 Z
 dependencies: []
 description: Interface library for SyncSign e-paper displays
 email: github@sen.cx