G-codes/offsets/tools with .Net

Moderators: TomKerekes, dynomotion

User avatar
TomKerekes
Posts: 2676
Joined: Mon Dec 04, 2017 1:49 am

Re: G-codes/offsets/tools with .Net

Post by TomKerekes » Thu Feb 08, 2024 12:07 am

ok thanks.

Added to comment:

Code: Select all

        /// To set int value in KFLOP in C do:
        /// persist.UserData[index] = i;
Regards,

Tom Kerekes
Dynomotion, Inc.

Moray
Posts: 288
Joined: Thu Apr 26, 2018 10:16 pm

Re: G-codes/offsets/tools with .Net

Post by Moray » Sun Mar 17, 2024 9:02 pm

Latest update on this, is I'm 95% happy with my screen designer (I have added buttons to move controls a chosen distance, however I need to split up another function to implement the code).

However, I have (probably foolishly!) gained another full time job, along with some more part time work, so my time to do any work to this is now non-existent for the foreseeable future :(
So If anybody would like access to the source code, let me know your GitHub user details, and I can add you as a collaborator.

User avatar
TomKerekes
Posts: 2676
Joined: Mon Dec 04, 2017 1:49 am

Re: G-codes/offsets/tools with .Net

Post by TomKerekes » Mon Mar 18, 2024 11:59 pm

Hi Moray,

Sounds like good news for you, bad news for us :)

Is there a reason you don't just make it public?
Regards,

Tom Kerekes
Dynomotion, Inc.

Moray
Posts: 288
Joined: Thu Apr 26, 2018 10:16 pm

Re: G-codes/offsets/tools with .Net

Post by Moray » Thu Mar 21, 2024 9:16 pm

TomKerekes wrote:
Mon Mar 18, 2024 11:59 pm
Hi Moray,

Sounds like good news for you, bad news for us :)

Is there a reason you don't just make it public?
There's some code/functionality that I don't really want to make public yet.
The main bit is I started work on making the main init.c being automatically generated a while ago, and I can't actually remember how far I got with that as it's so long ago, so I'd want to at least strip that code out. However I just don't have the time to do so.
Plus there's a few sections that still need tidied up, with some functions needing split out more to make more sense (the main screen designer function is currently somewhat unwieldy!)

Post Reply