FYI, I’m using the latest v 1.0.0.20.
I’m a bit confused about the text color. A defined constant or variable appears in blue text color and I find that very convenient. But very often the blue color disappear and goes back to black, and suddenly when I start writting more code the text color changes back to blue again.
Has anyone noticed this? And is there a way to fix it?
Yes, I have seen some of that as well, not sure what to do about it, other than make Nathan aware of it. 20 is a lot better than 18 or 19, so hopefully in the next few builds with this new editor class things will continue to improve.
I am glad to have New Window support again (2 views on the same file) Works for Basic/Asm files, does not currently work for C/C++ files.
I think the fix for the color issue that Zenta mentioned was also fixed.
Sounds great, I’ve just a short question I got this error after compilling and linking ok:
C:\Programfiler\BasicMicro\Basic Micro Studio\bin\ld.exe : region text is full (c:\programfiler\basicmicro\basicatom-pro ide\myprogs\kurt\binary mode\robots\apod_binaryssc_xbee.bin section .text)
I can’t get any release beyond 1.0.0.16 to run on my Windows XP systems.
Here’s the message I get from version 1.0.0.17 through 1.0.0.23:
Starting Compiler…
This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.
I’ve created new basic and c projects but still get the same error. I’ve tried 3 different Windows XP systems with the same result.
I did follow the message and tried reinstalling with the same result.
From the BasicMicro post I think he fixed some typos in the TimerW Interrupt handler.
Also from a previous post. Some people running XP have had problems installing builds since maybe 1.0.0.10. It has something to do with VC2008 library not being installed… If you are one of them you should look at the post: forums.basicmicro.net/viewtopic. … 09bf828aaa
It has a software work around for an issue on the Arc32 with Hitec Digital servos. You can read more about this issue up on the thread: forums.basicmicro.net/viewtopic. … 6034c00bff
Just for those who want to know this will be the perminent fix. The production ARC32s will ship with 4.7k pulldowns on pins 8 to 15 and 24 to 27 which will allow all the digital servos to work on them. The other pins don’t have a problem with the digital servos as of .28 and those pins(0 to 7, 16 to 23 and 28 to 31) will have no pulldowns on the production ARC32s.
Thanks Nathan,
I was not sure if this was a permanent fix or only until the production ones were done as you mentioned that there was a performance hit for you having to set the 3697 IO pin to low…
I felt the extra processing time was worth it for the extra fexibility. Being able to use the internal pullups on the 3687 I/Os is a big plus in my book. The HSERVO2 system processor usage is from 0.4%(enabled but no servos active at all) to 1.7%(actively moving all 32 servos) with the .28 update. Since the ARC32 is already 25% faster than the AtomPro24 or 28 I don’t think it’s too big a hit.