akg4y Posted February 4, 2010 Share Posted February 4, 2010 One thing I feel would be helpful would be the ability to comment my code in ComposerHE so that when I pull up something if I dont remember why I did something (ie put in a delay somewhere, or cant remember exactly which variables/contacts/buttons are tied together) if I commented it then I can figure it out easily.As my project gets more complex with more programming in it I find it takes me more and more time to figure out what I did a few weeks ago... especially since some of the things I did back then werent necessarily the best way to do things so then it takes me a while just to find the programming before even trying to understand it (for example if I programmed a multitap using programming under press & release rather than under release then variable). Link to comment Share on other sites More sharing options...
dinosaur Posted February 4, 2010 Share Posted February 4, 2010 It's been on my wish list also. What I ended up doing is to keep separate doc file that has documentation. It's not perfect but it works well in lieu of actual comment lines in the code. Link to comment Share on other sites More sharing options...
neil12011 Posted February 6, 2010 Share Posted February 6, 2010 I comment my code, I just make a string variable called "comment". Link to comment Share on other sites More sharing options...
dgbrown Posted February 6, 2010 Share Posted February 6, 2010 ^ Same here. It's weak though. Almost an after thought. Comments are the first thing that should have been put in the programming interface. Link to comment Share on other sites More sharing options...
neil12011 Posted February 8, 2010 Share Posted February 8, 2010 agreed, hardly a robust solution, but it is what it is, we've voiced our opinions to C4 on the matter, I'm pretty sure it's somewhere between font size and intercom functionality on the priority list. Link to comment Share on other sites More sharing options...
shaneoneill Posted February 8, 2010 Share Posted February 8, 2010 excellent idea. also would like some sort of visible programming tree per variable or however c4 wants to structure.in other words, because im learning as i go myself, sometimes i cause the action to occur when the button is pressed (variable tested), sometimes i cause the action to occur when the variable is toggled and sometimes i cause the action to occur in programming once the variable is retested. i have become more consistent, but it would be helpful if c4 could show me all the places a variable occurs in my programming.basically its the trail of breadcrumbs for programmers. i'd like to be able to see all the occurrences of a variable or really other things too. shane Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.