Sign in
Search basicx
Subscribe to basicx
basicx by Keywords
Accelerometer | ADC | ADXL | Adxl20 | AVR | BasicStamp | BX-35 | BX28 | BX35 | COM3 | Compiler | Downloader | EEPROM | Electromagnet | GetADC | GP2D1 | GPS | I2C | IDE | Keypad | LCD | LCD+ | MIDI | Motors | Multitasking | Netmedia | Networking | PCB | PID | PlaySound | PWM | Relays | RTC | Servo | ShiftOut | SitePlayer | SPI | Stack | Timer | USB
Ads
Discussion Groups
Discussion Groups | BasicX | Re: Saving programs
Discussion forum for the BasicX family of microcontroller chips.
Saving programs - mechatronicsccc - Sep 14 2:33:26 2006
Up to know I only worked with one basicX chip.
I just got 6 new Basicx24p and working on more then one project.
I have 2 questions.
Could someone help explane the difference between Module and project?
How to save different verations of the same program without
overwriting the first?
Ex. I wrote the first program and saved it. Then I wont to try
something new but would like to go back to the unchanged program.
Outside of changing the Dir of where the program is saved I am lost.
Thanks
(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )
I just got 6 new Basicx24p and working on more then one project.
I have 2 questions.
Could someone help explane the difference between Module and project?
How to save different verations of the same program without
overwriting the first?
Ex. I wrote the first program and saved it. Then I wont to try
something new but would like to go back to the unchanged program.
Outside of changing the Dir of where the program is saved I am lost.
Thanks
(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )
Re: Saving programs - mr_tentacle_too - Sep 15 9:36:45 2006
The project represents all the code that will be compiled and downloaded
into your BasicX. A project can have one or more modules. This is a
little confusing if you usually just write a single program, all in one
file, and download that. This is a really useful facility if you have
chunks of code that you often re-use, for exaample code to interface
specific devices, I2C, etc. You can put it on a separate module and
include it in many projects.
To save a prior module version, so you can go back to it, this is what I
do:
When you open the project, the modules that are in that project also
opened. So, lets say project My_Bx_00 includes module My_Module.bas.
To make changes to a NEW COPY, in the editor, click on "File" then
"Save Module As". Save the current module as My_Module_01.Bas. This
will autonatically update the project to reference the new version, and
your old file will still be there.
To get the old version back, use the "Project-->Files" dialog.
Hope this helps!
--- In b...@yahoogroups.com, "mechatronicsccc"
wrote:
>
> Up to know I only worked with one basicX chip.
> I just got 6 new Basicx24p and working on more then one project.
> I have 2 questions.
> Could someone help explane the difference between Module and project?
>
> How to save different verations of the same program without
> overwriting the first?
> Ex. I wrote the first program and saved it. Then I wont to try
> something new but would like to go back to the unchanged program.
>
> Outside of changing the Dir of where the program is saved I am lost.
>
> Thanks
>
[Non-text portions of this message have been removed]
(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )
Re: Re: Saving programs - Mechatronics At Camden CC - Sep 19 0:43:34 2006
I think I got it. I dont need the modules unless i like to reuse code EX I2c, or
code for LCD display.
Now if I like to reuse say code for a LCD display for debuging purposes how would I
create the module to be able to recall it to add in a new program??
Thanks
mr_tentacle_too wrote:
The project represents all the code that will be compiled and downloaded
into your BasicX. A project can have one or more modules. This is a
little confusing if you usually just write a single program, all in one
file, and download that. This is a really useful facility if you have
chunks of code that you often re-use, for exaample code to interface
specific devices, I2C, etc. You can put it on a separate module and
include it in many projects.
To save a prior module version, so you can go back to it, this is what I
do:
When you open the project, the modules that are in that project also
opened. So, lets say project My_Bx_00 includes module My_Module.bas.
To make changes to a NEW COPY, in the editor, click on "File" then
"Save Module As". Save the current module as My_Module_01.Bas. This
will autonatically update the project to reference the new version, and
your old file will still be there.
To get the old version back, use the "Project-->Files" dialog.
Hope this helps!
--- In b...@yahoogroups.com, "mechatronicsccc"
wrote:
>
> Up to know I only worked with one basicX chip.
> I just got 6 new Basicx24p and working on more then one project.
> I have 2 questions.
> Could someone help explane the difference between Module and project?
>
> How to save different verations of the same program without
> overwriting the first?
> Ex. I wrote the first program and saved it. Then I wont to try
> something new but would like to go back to the unchanged program.
>
> Outside of changing the Dir of where the program is saved I am lost.
>
> Thanks
>
[Non-text portions of this message have been removed]
---------------------------------
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail.
[Non-text portions of this message have been removed]
(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )
code for LCD display.
Now if I like to reuse say code for a LCD display for debuging purposes how would I
create the module to be able to recall it to add in a new program??
Thanks
mr_tentacle_too
The project represents all the code that will be compiled and downloaded
into your BasicX. A project can have one or more modules. This is a
little confusing if you usually just write a single program, all in one
file, and download that. This is a really useful facility if you have
chunks of code that you often re-use, for exaample code to interface
specific devices, I2C, etc. You can put it on a separate module and
include it in many projects.
To save a prior module version, so you can go back to it, this is what I
do:
When you open the project, the modules that are in that project also
opened. So, lets say project My_Bx_00 includes module My_Module.bas.
To make changes to a NEW COPY, in the editor, click on "File" then
"Save Module As". Save the current module as My_Module_01.Bas. This
will autonatically update the project to reference the new version, and
your old file will still be there.
To get the old version back, use the "Project-->Files" dialog.
Hope this helps!
--- In b...@yahoogroups.com, "mechatronicsccc"
wrote:
>
> Up to know I only worked with one basicX chip.
> I just got 6 new Basicx24p and working on more then one project.
> I have 2 questions.
> Could someone help explane the difference between Module and project?
>
> How to save different verations of the same program without
> overwriting the first?
> Ex. I wrote the first program and saved it. Then I wont to try
> something new but would like to go back to the unchanged program.
>
> Outside of changing the Dir of where the program is saved I am lost.
>
> Thanks
>
[Non-text portions of this message have been removed]
---------------------------------
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail.
[Non-text portions of this message have been removed]
(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )
Re: Re: Saving programs - "nje...@ihug.co.nz" - Sep 19 1:34:36 2006
Don't forget, you can go to an peice of code that works finer, copy (
hi-light then CTRL-C) the subroutine or code you want to use, then
open your new program and paste the bit in ( CTRL-V). Sometimes that's
easier than using modules.
neil
Mechatronics At Camden CC wrote:
> I think I got it. I dont need the modules unless i like to reuse code
> EX I2c, or
> code for LCD display.
>
> Now if I like to reuse say code for a LCD display for debuging
> purposes how would I
> create the module to be able to recall it to add in a new program??
>
> Thanks
> mr_tentacle_too> wrote:
>
> The project represents all the code that will be compiled and downloaded
> into your BasicX. A project can have one or more modules. This is a
> little confusing if you usually just write a single program, all in one
> file, and download that. This is a really useful facility if you have
> chunks of code that you often re-use, for exaample code to interface
> specific devices, I2C, etc. You can put it on a separate module and
> include it in many projects.
>
> To save a prior module version, so you can go back to it, this is what I
> do:
>
> When you open the project, the modules that are in that project also
> opened. So, lets say project My_Bx_00 includes module My_Module.bas.
> To make changes to a NEW COPY, in the editor, click on "File" then
> "Save Module As". Save the current module as My_Module_01.Bas. This
> will autonatically update the project to reference the new version, and
> your old file will still be there.
>
> To get the old version back, use the "Project-->Files" dialog.
>
> Hope this helps!
>
> --- In b...@yahoogroups.com,
> "mechatronicsccc"
> wrote:
> >
> > Up to know I only worked with one basicX chip.
> > I just got 6 new Basicx24p and working on more then one project.
> > I have 2 questions.
> > Could someone help explane the difference between Module and project?
> >
> > How to save different verations of the same program without
> > overwriting the first?
> > Ex. I wrote the first program and saved it. Then I wont to try
> > something new but would like to go back to the unchanged program.
> >
> > Outside of changing the Dir of where the program is saved I am lost.
> >
> > Thanks
> > [Non-text portions of this message have been removed]
> ---------------------------------
> Do you Yahoo!?
> Everyone is raving about the all-new Yahoo! Mail.
>
> [Non-text portions of this message have been removed]
>
>------------------------------------------------------------------------
>
>No virus found in this incoming message.
>Checked by AVG Free Edition.
>Version: 7.1.405 / Virus Database: 268.12.5/450 - Release Date: 18/09/2006
>
>
(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )
hi-light then CTRL-C) the subroutine or code you want to use, then
open your new program and paste the bit in ( CTRL-V). Sometimes that's
easier than using modules.
neil
Mechatronics At Camden CC wrote:
> I think I got it. I dont need the modules unless i like to reuse code
> EX I2c, or
> code for LCD display.
>
> Now if I like to reuse say code for a LCD display for debuging
> purposes how would I
> create the module to be able to recall it to add in a new program??
>
> Thanks
> mr_tentacle_too
>
> The project represents all the code that will be compiled and downloaded
> into your BasicX. A project can have one or more modules. This is a
> little confusing if you usually just write a single program, all in one
> file, and download that. This is a really useful facility if you have
> chunks of code that you often re-use, for exaample code to interface
> specific devices, I2C, etc. You can put it on a separate module and
> include it in many projects.
>
> To save a prior module version, so you can go back to it, this is what I
> do:
>
> When you open the project, the modules that are in that project also
> opened. So, lets say project My_Bx_00 includes module My_Module.bas.
> To make changes to a NEW COPY, in the editor, click on "File" then
> "Save Module As". Save the current module as My_Module_01.Bas. This
> will autonatically update the project to reference the new version, and
> your old file will still be there.
>
> To get the old version back, use the "Project-->Files" dialog.
>
> Hope this helps!
>
> --- In b...@yahoogroups.com
> "mechatronicsccc"
> wrote:
> >
> > Up to know I only worked with one basicX chip.
> > I just got 6 new Basicx24p and working on more then one project.
> > I have 2 questions.
> > Could someone help explane the difference between Module and project?
> >
> > How to save different verations of the same program without
> > overwriting the first?
> > Ex. I wrote the first program and saved it. Then I wont to try
> > something new but would like to go back to the unchanged program.
> >
> > Outside of changing the Dir of where the program is saved I am lost.
> >
> > Thanks
> > [Non-text portions of this message have been removed]
> ---------------------------------
> Do you Yahoo!?
> Everyone is raving about the all-new Yahoo! Mail.
>
> [Non-text portions of this message have been removed]
>
>------------------------------------------------------------------------
>
>No virus found in this incoming message.
>Checked by AVG Free Edition.
>Version: 7.1.405 / Virus Database: 268.12.5/450 - Release Date: 18/09/2006
>
>
(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )
Re: Saving programs - Tom Becker - Sep 19 15:49:19 2006
> ... I dont need the modules unless i like to reuse code...
One module (usually a .bas file) is required which must, I believe,
contain procedure Main().
An important concept to remember is this: when you make a change to a
shared module (in a common folder), that change will affect _every_
project that uses that module from that folder. Module management
might be necessary.
If, for example, you decide to remove some unneeded code from your
current project, if that module and code is used in another project,
you just broke the other project. [BTW, you needen't remove unused
procedures or functions since they will not be included in the current
project if they are not called anywhere in the project.]
Tom
(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )
One module (usually a .bas file) is required which must, I believe,
contain procedure Main().
An important concept to remember is this: when you make a change to a
shared module (in a common folder), that change will affect _every_
project that uses that module from that folder. Module management
might be necessary.
If, for example, you decide to remove some unneeded code from your
current project, if that module and code is used in another project,
you just broke the other project. [BTW, you needen't remove unused
procedures or functions since they will not be included in the current
project if they are not called anywhere in the project.]
Tom
(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )
Re: Saving programs - mr_tentacle_too - Sep 20 8:21:37 2006
To add a new module:
In the editor, click "Project" then "Files", then "Add File". The add
file dialog will display the current project directory. If this is
not where you want to create the module, navigate to the desired
directory.
When the desired directory is displayed, type the name of the new file
(for the module) in the file name field and hit "enter". You will be
prompted that the file does not exist, and asked if you want to create
it. Click "Yes".
The new module will open in a new window. Put the code you want to
share into the new module, and save it.
--- In b...@yahoogroups.com, Mechatronics At Camden CC
wrote:
>
> I think I got it. I dont need the modules unless i like to reuse
code EX I2c, or
> code for LCD display.
>
> Now if I like to reuse say code for a LCD display for debuging
purposes how would I
> create the module to be able to recall it to add in a new program??
>
> Thanks
>
(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )
In the editor, click "Project" then "Files", then "Add File". The add
file dialog will display the current project directory. If this is
not where you want to create the module, navigate to the desired
directory.
When the desired directory is displayed, type the name of the new file
(for the module) in the file name field and hit "enter". You will be
prompted that the file does not exist, and asked if you want to create
it. Click "Yes".
The new module will open in a new window. Put the code you want to
share into the new module, and save it.
--- In b...@yahoogroups.com, Mechatronics At Camden CC
>
> I think I got it. I dont need the modules unless i like to reuse
code EX I2c, or
> code for LCD display.
>
> Now if I like to reuse say code for a LCD display for debuging
purposes how would I
> create the module to be able to recall it to add in a new program??
>
> Thanks
>
(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )