Search found 16 matches

by Paul
Wed Jul 10, 2019 10:03 am
Forum: MegunoLink
Topic: AddCommand: full
Replies: 2
Views: 80

Re: AddCommand: full

Hi Eusaki, It probably means you are using our command handler library and have tried to register too many commands. By default you can only add 10 commands before the internal array that stores them is full. Check out the examples here for increasing the number of commands you can add: https://www....
by Paul
Wed Aug 22, 2018 8:55 am
Forum: MegunoLink
Topic: Trouble with Installer built with Builder
Replies: 5
Views: 863

Re: Trouble with Installer built with Builder

We'd like it to be simple for all. Still a little ways to go, but feedback really helps us understand where we need to improve. So thanks for getting in touch!

Please don't hesitate to reach out if you have any more problems.
Have a great day,
Paul.
by Paul
Tue Aug 21, 2018 11:29 pm
Forum: MegunoLink
Topic: Trouble with Installer built with Builder
Replies: 5
Views: 863

Re: Trouble with Installer built with Builder

Hi Griiker, I'm wondering if you put a path in the "Destination Folder" field in the "Edit Project Item" dialog? Normally this isn't needed. When it is blank, the project item will get installed in the main install folder. You can put a folder name here to have it installed in a sub folder. A full p...
by Paul
Sun Apr 22, 2018 9:46 am
Forum: MegunoLink
Topic: TrackBar Command Editor
Replies: 4
Views: 943

Re: TrackBar Command Editor

Hi Tim, The latest version (1.20.18108.0418) released today will let you get the actual bytes. In your case, you'll want something like: \xFF\x00[Tools.AsByte((byte)TrackBar.Value)] The \xXX are literal byte values; Tools.AsByte(...) converts a number to a sequence of bytes. Expressions (surrounded ...
by Paul
Wed Apr 11, 2018 1:49 am
Forum: MegunoLink
Topic: TrackBar Command Editor
Replies: 4
Views: 943

Re: TrackBar Command Editor

Hi, You can use: [((int)num.Value).ToString("X4")] to create a message with hex values in a string. But I think you want actual bytes. Unfortunately that doesn't seem to be working at the moment. MegunoLink is converting numbers to strings. I will try to figure out what's gone wrong and fix it. Kind...
by Paul
Mon Oct 02, 2017 5:01 am
Forum: MegunoLink
Topic: Unable to set data to send back to the UI
Replies: 8
Views: 2906

Re: Unable to set data to send back to the UI

Hi RoboBill, Great idea to start breaking your program up into smaller chunks. 1,000 lines is quite a bit for a single file. And breaking your problem down to the simplest example is a good idea too. Without the actual source it is a little hard to be sure what the problem is but my best guess is yo...
by Paul
Sun Jul 09, 2017 10:24 am
Forum: Projects
Topic: UDP from ESP8266 to MegunoLink Pro
Replies: 5
Views: 22276

Re: UDP from ESP8266 to MegunoLink Pro

Hi all,

We've had quite a bit of interest in sending data from the ESP8266. We added a little example in the UDP docs that does just that. Check it out here: http://www.megunolink.com/documentation ... nnections/

Have fun
Paul.
by Paul
Tue Feb 21, 2017 9:39 pm
Forum: MegunoLink
Topic: ToString function bug?
Replies: 1
Views: 1142

Re: ToString function bug?

Howdy, MegunoLink is built on C# and we are using that for formatting. In C# the width specifier sets the minimum width of the output. The output will expand to whatever is necessary to correctly represent the value. And an int is a 32 bit number so negative values will take 8 characters. To solve t...
by Paul
Sat Jan 21, 2017 9:37 am
Forum: MegunoLink
Topic: Can I export the table content?
Replies: 5
Views: 1955

Re: Can I export the table content?

There's also a shortcut to copy table values to the clipboard.

Just select the rows/ cells you want to copy, then type Ctrl + C (the windows shortcut for copying a selection to the clipboard).
by Paul
Sun Jan 15, 2017 7:48 am
Forum: MegunoLink
Topic: Sending Float number to arduino with SerialCommandHandler.AddVariable
Replies: 1
Views: 1199

Re: Sending Float number to arduino with SerialCommandHandler.AddVariable

Hi, Thanks for reporting that; I've added it to our list of bugs. This happens if your windows localization settings are set to a region that uses a comma as a decimal separator. Until I get it fixed, you can use this as a workaround in the interface panel: !SetPoint [num.Value.ToString().Replace(",...