Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Sun, 05 May 2024 05:45:33 +0000
Google Protocol Buffers
View Count: 2162
| [2016-06-21 07:25:29] |
| User266748 - Posts: 4 |
|
Hi, Was wondering if you've had chance to update the DTC Google Protocol Buffer .proto file to be compatiable with version 3 of the protocol buffer? Get a couple of errors when trying to using at as the input to protoc.exe DTCProtocol.proto: The first enum value must be zero in proto3. DTCProtocol.proto:397:18: Explicit 'optional' labels are disallowed in the Proto3 syntax. To define 'optional' fields in Proto3, simply remove the 'optional' label, as fields are 'optional' by default. Could potentially fix it myself but unsure of any impact on DTC (using Sierra Charts as the server) it would have if changed to order of the numbering in the enums? Thanks |
| [2016-06-21 07:27:48] |
| User266748 - Posts: 4 |
|
REalise I posted this in the wrong forum, can't find a way to delete it though. Have reposted in the DTC forum. Thanks |
| [2016-06-21 17:21:48] |
| |
|
This has been answered on the DTC Protocol forum. We will be updating the protocol file for version 3 of the protocol buffers compiler. Probably we will have a separate protocol file for version 3. Also the way that the enumerations have to be handled is that there needs to be a new enumeration with a value of 0 where one is missing. It will have the name *_UNSET. The existing ones cannot be renumbered. That would cause an obvious compatibility issue. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2016-06-21 17:23:00
|
To post a message in this thread, you need to log in with your Sierra Chart account: