See, as I said, the same install on three different machines and the problem persisted. So it was a problem with the IDE!!
Kurte, do you mind sharing your good version of .8? In the meanwhile I’ll switch to 8.0.1.7
Thanks for all the help guys
I’ll be looking into this this weekend. We give out the beta versions specifically to find issues like this that I missed. I think there has been several .8 releases to fix little bugs that cropped up. I ussually post that it has changed in the forum though. Once I fix this I’ll issue a .9 beta which also fixes the “enable” probalem in the hservo system.
Hi Acidtech,
Is it possible to add something like a build number in the about box. I don’t know what language and environment your using to build the IDE but most of the time this relatively easy and makes it possible to check if people are really working with the same version. Just a idea though 
Xan
I would second that! I also again would love a version that does not give me a compatiblity error every time I run it on vista, but that is a different issue…
One thing you can do is to look at the roperties on the EXE program and find out the modify date, which on the one I downloaded and installed yesterday was built I believe on December 1st.
Another thing that would help is something like a readme.txt file that downloads with each version, that would include what changed in each release. Most of the compiler products that I have include this. They usually also include a list of known problems.
Kurt
-
I’ll not release new betas under the same release anymore. That will solve that problem.
-
Changes.txt would be nice. But I’m afraid it’s old dogs and new tricks all over again. I’ll try to get better at keeping track of changes but don’t expect dramatic changes in that department anytime soon.
-
I don’t release any version(beta or full release) with any known bugs. That doesn’t mean that two seconds after I release it I don’t find a bug(though that is rare).
-
I’ve not had a chance to work on Vista with MBasic so I have not seen this bug. If you could give me something more detailed on the problem I may be able to change something to fix it.
Thanks Nathan,
As for the Vista bug, this is the same one we discussed in a few different threads, including: lynxmotion.net/phpbb/viewtopic.php?t=3109&postdays=0&postorder=asc&highlight=vista+signed&start=15
But basically every time you start the program, you get a message like:
http://i416.photobucket.com/albums/pp245/Kurts_Robots/Atom-Pro-vista-error.jpg
Kurt
I looked up that particular UAC message and it appears it is because we don’t digitally sign our exe files currently.
I fixed the debugger problem. I had added the ability to disable the debugger on the fly so sections of user code could run at full speed(nearly anyway) while still being able to debug other sections. Seems I had the flag backwards so it was disabled by default. Fixed that and I’ve made 8.0.1.9 available for download.
basicmicro.com/downloads/sof … p_8019.exe
Here is an example of the debug disable flag being used:
main
asm
{
bset #7,@SYSF:8 ;disable debuging
}
pause 100
asm
{
bclr #7,@SYSF:8 ;re-enable debuging
}
pause 100
goto main
Hi Nathan,
I downloaded 8019 and tried to compile a program that I believe compiled fine on 8018 and now fails:
Here is a small extract of the code
[code]speed var float
longestmove var float
stepsperdegree fcon 166.6
speed = ((longestmove*stepsperdegree)/(speed/20.0)) [/code]
It gives the error:
Error: FILE C:\USERS\KURT\DESKTOP\LYNXMOTION\FOO.BAS(LINE 3) : [TOKEN 166.6] : Expected a constant
This hits programs like the TV brat.
Kurt, it looks like a typo to me. is fcon part of the language?
I don’t think so, I compiled two different programs with it. For example the program written by Nathan that is in this thread:lynxmotion.net/viewtopic.php?t=1242
I believe it is a floating constant. The IDE editor does not highlight the word like con. If you try con instead of fcon it still errors out.
Kurt
Edit: P.S. - It would also help to know what the difference is between a Atom Pro 28 and an Atom Pro 28 revD
-
Fcon is a floating point constant. Also fcon is not highlighted by the IDE(I’ll fix that while I’m looking into this). FCON was added because the compiler couldn’t always determine if a constant was an int or a float and you don’t want to do a conversion from one to the other if you don’t have too.
-
I’ll check your program out tomorrow and let you know whats wrong. I don’t remember making any changes to the con/fcon handlers though so I’m not sure why it’s complaining.
-
Rev D AtomPros have not been released yet. The difference is they use a 20mhz osc. So they are 25% faster than the current modules.
Hi Nathan,
Since you’re already planning to fix some highlighting stuff. I’ve noticed that variables and constands defined in a separate file using projects aren’t highlighted either. Is it possible to fix that as well?
Thanks! Xan
Yeah, that would be great to get fixed since its very useful to see if you’ve written the variable or constant correctly.
Thanks Nathan,
All you need is the one line:
stepsperdegree fcon 166.6
I added more as with the compiler 8.0.0.0 which I still had on my machine the one line GP faulted out the compiler… Does not do it with your current version.
That capability isn’t going to get added anytime soon. Currently highliting is handled on the fly. Instead of parsing the currently active file I’d have to parse all the files which would greatly slow down the whole process. To do what you wan t I’ll have to rewrite the parser from the ground up to do it in a completely different way. I plan on it but it isn’t a quick fix and it is at the bottom of my todo list.
Fixed the FCON issue. New link is:
basicmicro.com/downloads/sof … _80110.exe
Also PM me with any command color highliting issues. Note that as stated above I can’t do anything about coloring/highliting constants and variables across multiple files at the moment.
Having this fixed would just be a “nice to haveâ€