Just checked it out, looks VERY nice. Makes me want to buy a programmer to work with it.
Just checked it out, looks VERY nice. Makes me want to buy a programmer to work with it.
-Bert
The glass is not half full or half empty, Its twice as big as needed for the job!
http://foamcasualty.com/ - Warbird R/C scratch building with foam!
Norm , I just downloaded your latest version and I think it needs a bit more work. I use TAB's for my indenting and when edited with MCSP it looks as it should. When the same program is loaded into your latest version, it seems to get confused about the tab spacing and also seems to get confused about where to put the connecting lines to the left side of the screen. There are places where multiple connections are all covered up by the same line... If you can give me your email address I will send you the some screen shots...
dave Purola,
N8NTA
Last edited by Normnet; - 24th December 2010 at 01:00.
Hi,
I've just downloaded and "installed" the IDE - went through the config process of pointing the IDE at the installation folders for MPSAM, PBP etc and then loaded up one of my old programs. The IDE responded with a pop up about converting tabs or something and then displayed the code.
A lot of the coloured brackets shown in your example were bunched up against the far left of the code window, so the "importation" didn't work for me. I tried compiling and each time I got an error about an invalid path statement, for either PBP or MPSAM. It seemed as if the IDE had lost it's settings, even though the INI files show the path statements to where the EXE's are
I think I've set all the parameters up, to use my easypic5 board, MPSAM and PBP which is my current set up with MCS, but could be wrong. I did try the automatic scan as well for each option and if didn't find the exe's on some occasions and I used the manual browse optionCode:[PicBasicPro] Use MPASM=1 Use PBPL=0 Compiler Path=C:\PBP2.60\PBP.EXE Assembly Path=*:\ IDE Path=C:\Program Files\Mecanique\MCS\CodeStudio.exe [Proton] Compiler Path=*:\ IDE Path=*:\ [Programmer] Name0= Name1=PICkit2 3.3 volt Name2=PICkit3 Name3=EasyPic5 Name4=melabs U2 Programmer Location0= Location1=Browse to *\pk2cmd.exe Location2=Browse to *\pk3cmd.exe Location3=C:\Program Files\Mikroelektronika\PICFLASH-mikroICD\PICFLASH.exe Location4=Browse to *\meProg.exe Parameter0=
EDIT:
Ignore that..... have found out where I was going wrong - can now compile OK !!! - USER ERROR ON THIS OCCASION !!!
Last edited by malc-c; - 28th December 2010 at 11:15.
In the left column it's possible to select things like labels, variables, includes etc, and an option for none. Would it be possible to have an option for all, in the same way MCS does.
Ive also noticed that when a file is opened in FL it changes the text of the commands. For example
Note the lower case "if" in the last two lines. I then use the option to open in MCS and looked at the same set of linesIF Temperatures(pid_Channel) > alarmhigh(pid_Channel) and Alarm = 1 then AlarmPin = 1
IF Temperatures(pid_Channel) > alarmhigh(pid_Channel) and Alarm = 0 then AlarmPin = 0
IF Temperatures(pid_Channel) <= alarmhigh(pid_Channel) then AlarmPin = 0
IF Temperatures(pid_Channel) <= alarmlow(pid_Channel) then AlarmPin = 0
if Temperatures(pid_Channel) < alarmlow(pid_Channel) and Alarm = 1 then AlarmPin = 1
if Temperatures(pid_Channel) < alarmlow(pid_Channel) and Alarm = 0 then AlarmPin = 0
Formatting was correct....IF Temperatures(pid_Channel) > alarmhigh(pid_Channel) and Alarm = 1 then AlarmPin = 1
IF Temperatures(pid_Channel) > alarmhigh(pid_Channel) and Alarm = 0 then AlarmPin = 0
IF Temperatures(pid_Channel) <= alarmhigh(pid_Channel) then AlarmPin = 0
IF Temperatures(pid_Channel) <= alarmlow(pid_Channel) then AlarmPin = 0
IF Temperatures(pid_Channel) < alarmlow(pid_Channel) and Alarm = 1 then AlarmPin = 1
IF Temperatures(pid_Channel) < alarmlow(pid_Channel) and Alarm = 0 then AlarmPin = 0
Are you relying on the program to do the capitalization? Or are you typing IF.
Dave
Always wear safety glasses while programming.
NEW v1.0.0.4
Added a format all button for keywords (case).
User discretion required a button as both Proton and PicBasic files could be open with FL not certain of which style to use.
Formatting would be recommended when opening a file edited in MicroCode Studio as it saves "as typed" but appears formatted.
Proton IDE has a recommended option to "Commit formatting changes to source code" which would then require no FL format button press.
Formatting does all compiler keywords as well as variables, constants, aliases, labels, macros, and data labels.
Norm
-Bert
The glass is not half full or half empty, Its twice as big as needed for the job!
http://foamcasualty.com/ - Warbird R/C scratch building with foam!
Bookmarks