Show Posts
Pages: 1 ... 102 103 [104] 105 106 ... 278
1546  Development / Other Software Development / Re: Cosa: An Object-Oriented Platform for Arduino programming on: July 18, 2013, 12:41:27 pm
I already have a lot of Arduino-like code written for the 122x, pinMode, digitalWrite, Serial etc. It's all C but I plan move it to C++ before too long.

One of my next jobs is to separate the 122x-specific stuff into files to help get it running on the other models.

_____
Rob
Fancy building a core for UECIDE?
1547  Development / Other Software Development / Re: New fork of the IDE on: July 18, 2013, 12:39:51 pm
Great! Now it has got everything we need basically.
The next step is to have multiple serial terminals.. That is easy in java, isn't it ? smiley

PS: select/copy from terminal would be nice to have.. Or is there an another trick?
Selecting an area should auto-copy the contents to the clipboard.

I have been thinking about multiple serial terminals, yes.  With the current serial port setup it's not possible, but it will be when I move the serial port storage from the base to the editor.
1548  Development / Other Software Development / Re: New fork of the IDE on: July 18, 2013, 11:20:28 am
I have added options to the Serial Terminal preferences to make it add CR to LF on incoming and outgoing data automagically.
1549  Development / Other Software Development / Re: New fork of the IDE on: July 18, 2013, 10:19:40 am
Great!
The cr/lf stuff is related to line entry only, or to the serial terminal as well?
Line entry only.  In direct terminal it's the exact keypresses that you send.
Quote
The theme is ok, just the small stuff with status font in theme.txt is in question (replaced by new lib if not saved).
I could always move that from the theme and into preferences smiley-wink
1550  Development / Other Software Development / Re: New fork of the IDE on: July 18, 2013, 10:10:30 am
Quote
I have also added line-based text entry on the serial terminal.
And the trick ?
The trick is to download the new version of the SerialTerminal.jar and copy it in to the plugins directory (or install it from inside the IDE, but as it's a bundled one it won't overwrite it but override it).
Quote
PS: What about to put Theme folder (or theme.txt) off of the lib (otherwise we may overwrite theme.txt  with the upgrade).
The theme is set by the branding.  The branding is set at compile time.  You are using the UECIDE branding, and as a result you have the UECIDE theme.

If you want your own theme you could grab the source code and create your own brand smiley-wink
1551  Development / Other Software Development / Re: New fork of the IDE on: July 18, 2013, 09:49:06 am
You kidding me .. smiley-twist

Code:
# GUI - STATUS
status.notice.fgcolor = #yellow!!
status.notice.bgcolor = #666666
Ok ok ok...  But I'm not using yellow - I'm using #FFFF88 as pure yellow is just too intense.

I have also added line-based text entry on the serial terminal.
1552  Development / Other Software Development / Re: New fork of the IDE on: July 18, 2013, 09:37:58 am
smiley-cry
I cannot see the status info, black on dark gray, what about Yellow bold?   smiley-razz

LOL

You fool smiley-razz
I'll try and remember to do it smiley-wink
1553  Development / Other Software Development / Re: New fork of the IDE on: July 18, 2013, 09:18:08 am
0.5.4a - ok
Yup, that's the one smiley
1554  Development / Other Software Development / Re: New fork of the IDE on: July 18, 2013, 09:16:07 am
I have just added a "Clean build folder" to the Sketch menu.  Also, I have made the "Remove old build folder before each build" option actually do something.
1555  Development / Other Software Development / Re: New fork of the IDE on: July 18, 2013, 09:03:37 am
The setting is applied live.  What it might be is it not recompiling as the file is no newer?
1556  Development / Other Software Development / Re: New fork of the IDE on: July 18, 2013, 08:56:58 am
Now I do understand it better.. I took the multiwii example (posted here), that is 15 files. The "Combine all INO/PDE" flag is set. I created an error somewhere.

When being built I get the error message:
Code:
C:\DOCUME~1\pito\LOCALS~1\Temp\build-acfcc626-fe68-44d5-8868-e77417ded46a\PP_MWII.cpp: In function 'void ACC_getADC()':
C:\DOCUME~1\pito\LOCALS~1\Temp\build-acfcc626-fe68-44d5-8868-e77417ded46a\PP_MWII.cpp:7420: error: 'ACC_Common' was not declared in this scope

I see there line 7420 which is 283 in one of the files. But the file and the line with the actual error has not been shown..
The size of the main is 1275 lines.
That is exactly why I think the Arduino way of doing things is so wrong...
Quote
BTW: a change in the settings in preferences window needs a restart of uecide - is that ok?
Which settings in particular?  Most settings are got direct from the preferences map, but some are only ready on startup.
1557  Using Arduino / Programming Questions / Re: How to do a particular operation for 1 ms using arduino. How to set the timer on: July 18, 2013, 08:38:34 am
Quote
How to do  a particular operation for 1 ms  using arduino.
Code:
unsigned long then = micros();
while(millis() - then > 1000)
{
   // Do the one ms thing
}

Quote
How to set the timer values.
Which timer? What values? What for?
That'd be 1,000ms - 1 second smiley-razz

To do something for 1ms you need to do the same thing but with micros().

You'd think at first you could do:
Code:
unsigned long now = millis();
while (millis() == now) {
  // do something
}
but that would only do the "something" for the remainder of the current millisecond.  If you start it half way through a millisecond you'll only get half a millisecond's worth of something.

So use a loop that executes until the number of microseconds exceeds 1000 more than the start time.
Code:
unsigned long now = micros();
while (micros() - now <= 1000) {
    // do something
}
1558  Development / Other Software Development / Re: New fork of the IDE on: July 18, 2013, 08:23:41 am
As not being an experienced programmer, I can only say that when I have 20 separate files which are compiled separately, all compilers I work with show in case of an error the file_name and the line_number_within_the_file_with_the_error. So I can see where the error is located. Usually I click on the error message and the editor opens the particular file showing the specific line in error..
That would be a really nice feature.

But...  I have no control over what compiler is used by a core, so I have no idea what the output format of the error will be, so I cannot parse it reliably for information.  And with the Arduino converting INOs into CPP and adding cruft at the top of the file (#include <Arduino.h> and all the function prototypes) the output of the compiler is not directly related to the INO file anyway.

If it were just one compiler always in use for it, then I'd be able to parse it and calculate the real line number and display that, make it clickable, etc.  But that would break the extensibility and universality of UECIDE...
1559  Development / Other Software Development / Re: New fork of the IDE on: July 18, 2013, 07:56:59 am
Then try to make two line numbers there
Code:
error_line | editor_line |   //the actual source line 1
error_line | editor_line |   //the actual source line 2
..
The editor_line N. will remain the same as within the file, error_line n. will be the line with "offset" you need to see because of errors.
Interesting approach, though.. smiley

Not something I fancy editing really...  and having 2 numbers there would just be plain confusing.

I'll just keep it as an option you can turn on/off at will.
1560  Development / Other Software Development / Re: New fork of the IDE on: July 18, 2013, 07:24:43 am
I do not want to dispute the features of your product, of course, or make deals smiley
But again:

In a 197 lines long main.ino source an error message cannot point to the line 218 of the file main.ino ..

The build process shall not renumber the lines of main.ino in the editor window you watch.
I think your comments are very valid in a system where all the INO files are merged into one - in that scenario the error line number is completely meaningless, and renumbering the main INO file is stupid.

If the INO files are compiled separately though, and you get an error at say line 218 it can be very useful to know just where that line 218 actually is - it will be in that same INO file somewhere and having the lines and the errors matching up will help you find that error.

There's nothing worse than being given a line number for an error and not having a clue where that line actually is.  Finding the error can be a real chore.  With the line numbers changed to match the errors (I cannot do it the other way around) you can instantly find where that error is.
Pages: 1 ... 102 103 [104] 105 106 ... 278