- Borland Compiler Download
- Turbo Basic Compiler Download
- Borland Turbo Basic Compiler Download Fast Auto Clicker
- Borland C++ Compiler
- Borland C Compiler For Windows
- Borland Turbo Basic Compiler Download Fast Download
DisC was originally written in Borland C 3.0 (running on DOS), but now i dont have the compiler. Also i find that not many people are using it these days, so i have 'ported' DisC to Win32! I have compiled and successfully executed DisC using Microsoft Visual C 6.0, though there shouldnt be any problems with other Win32 compilers. 5.5 (2000-02-16; Windows 95/98/NT/2000): Based on Borland CBuilder 5, it is a freeware compiler without the IDE from the parent product. Includes Borland C Compiler v5.5, Borland Turbo Incremental Linker, Borland Resource Compiler / Binder, C Win32 Preprocessor, ANSI/OEM character set file conversion utility, Import Definitions utility to. Borland Turbo C v3.0 (C Compiler).rar - Google Drive. This project presents clone of the Borland Turbo C/C or Embarcadero C 10.1 ‘Berlin' library 'conio' for the GCC compiler, more precisely for the C language in Windows, Linux and Mac OS operating systems. Because all functions are defined within the header file itself, the installation is simple.
Screenshot of PowerBasic for Windows 9.0 IDE and an example compiled Windows GUI. | |
| Developer | Robert 'Bob' Zale (b. 1945, d. 2012) |
|---|---|
| First appeared | 1989; 32 years ago |
| Stable release | |
| Website | www.powerbasic.com |
| Influenced by | |
| Turbo Basic |
PowerBASIC, formerly Turbo Basic, is the brand of several commercial compilers by PowerBASIC Inc. that compile a dialect of the BASICprogramming language. There are both MS-DOS and Windows versions, and two kinds of the latter: Console and Windows. The MS-DOS version has a syntax similar to that of QBasic and QuickBASIC. The Windows versions use a BASIC syntax expanded to include many Windows functions, and the statements can be combined with calls to the Windows API.
History[edit]
The first version of the DOS compiler was published as BASIC/Z, the very first interactive compiler for CP/M and MDOS. Later it was extended to MS-DOS/PC DOS and in 1987 Borland distributed it as Turbo Basic.
Turbo Basic was originally created by Robert 'Bob' Zale (1945–2012) and bought from him by Borland. Accounting software source code in vb6 free. When Borland decided to stop publishing it (1989), Zale bought it back from them, renamed it PowerBASIC and set up PowerBASIC Inc. to continue support and development of it; it was later called PBDOS.[2][3][4]
PowerBASIC went on to develop BASIC compilers for Windows, first PBWIN — their flagship product — and then PBCC, described below.
On November 6, 2012, Robert Zale, the creator of PowerBASIC, died. For a time, it was assumed that the company might cease operations. His wife, Mrs. Vivian Zale, posted on 8 March 2014 to the PowerBASIC forums a statement that the company would continue in operation.[5] On May 10, 2015, Mrs. Zale announced that work was continuing on new versions of PowerBASIC compilers.[6]
On November 2, 2016, Vivian Zale announced her intention to begin seeking a buyer for the company.
Active development of PowerBASIC products has stopped. They no longer expect to release PBWin11 and PBCC7, which were in beta testing when Bob Zale died, nor the 64-bit compilers or PB/Pro (PBWin and CC in one compiler), which were still in the alpha stages.
On January 31, 2017, Adam Drake announced Drake Software had acquired the PowerBASIC source code from PowerBasic, Inc., with the intention of updating and improving the functionality of the product.[7] This was later confirmed by Vivian Zale with a forum post thanking the members for their support.[8] Sadly, no new version was ever released (the last release v10.03 was 8 years ago as of december 2020), not even small tweaks like adding the correct DPI settings for the IDE were released, and as such makes it quite clear what the future of PowerBASIC is. No development activity has been shown too in the form of progress reports or beta's. Apparently one person is working on something for those 8 years which, even if true, reintroduces the single point of failure. However, one can still buy new licenses.
Compilers[edit]
PowerBASIC programs are self-contained and use no runtime file to execute. In all versions of the compiler the applications compile without external libraries, though you can use such libraries if desired. PBDOS creates 16-bit DOS MZ executable files, while PBWIN and PBCC create 32-bit Portable Executable (PE) files.
Turbo Basic[edit]
Borland's Turbo Basic contains extensions to classical BASIC (while not breaking compatibility). One of those was a drawing API, and mouse access.
Unlike most BASIC implementations of its time, Turbo Basic was a full compiler which generated native code for MS-DOS. Other implementations were either interpreters, or relied heavily on a runtime library. The integrated development environment could run a BASIC program internally for traditional BASIC debugging (see sample below), or generate an MS-DOS stand-alone executable file that could be run on other systems without the Turbo Basic product or runtime libraries.
Code example[edit]
The following program is an example of the ALGOL-like BASIC dialect that Turbo Basic supported. Unlike traditional BASIC[citation needed], which used line numbers and had limited control structures and no support for ALGOL-like subroutines, modern BASIC dialects starting at this period were extended to make the language compatible with modern structured programming theory by discarding the line numbers and adding the control structures and subroutine definitions needed by structured programming.
(s$ is a string and s is a single-precision floating-point (number). They are separate variables.)
Like the other Borland products of this era, the code executes within the integrated development environment.
PowerBASIC for DOS (PBDos)[edit]
PBDOS includes an integrated development environment (IDE) and supports DOS 3.30 and all later versions.[9]
PowerBASIC Console Compiler (PBCC)[edit]
PBCC is a 32-bit compiler for the Windows 9x series and Windows NT series of operating systems, including Windows XP, Windows Server 2008, Windows Vista, and Windows 7. PBCC applications can use dynamic-link libraries (DLLs). The compiler comes with an IDE including an editor and stepping debugger.
No knowledge of Windows programming is required to create character mode or graphical applications with this compiler. Common Gateway Interface executables can also be compiled using PBCC.
PBCC creates only executables, not DLLs. (PBWin — see below — can create both.)
PowerBASIC Compiler for Windows (PBWin)[edit]
PBWin is a 32-bit compiler compatible with the Windows 9x series and the Windows NT series of operating systems, including Windows XP, Windows Server 2008, Windows Vista, Windows 7, Windows 8 (8.1), and Windows 10.[10] PBWin can create dynamic-link libraries. PBWin applications can read dynamic-link libraries].PBWin comes with a compiler, IDE with editor, and stepping debugger.
Dynamic Dialog Tools (DDT)[edit]
You can create an application's graphical user interface using the Windows API, or by using the inbuilt DDT language extensions. The group of BASIC statements which wrap Windows API functions, particularly in the creation and handling of dialog boxes and child controls is collectively known as Dynamic Dialog Tools. Using DDT requires less coding than to create a similar program using the Windows API. Using the DDT and the Windows API (known as SDK style as in Microsoft Windows SDK) are not mutually exclusive.
Trial Versions of Compilers[edit]
25henkathird grade james tes. PowerBASIC renamed PBWin v9.07 and PB/CC v5.07 as 'Classic PBWin' and 'Classic PB/CC', respectively, and on November 1, 2016, released them as free, no-nag, trial versions along with PBForms v1.0 (PowerBASIC Forms).
Tools[edit]
PB Forms[edit]
PowerBASIC Forms, available for purchase separately, is a graphical user interface design tool add-on for PBWin. It automatically produces source code using the DDT language extension that creates forms using the Windows graphical user interface.
COM Browser[edit]
The PowerBASIC COM Browser, which comes with PBWin, is an application that exposes the interfaces, methods, and properties of COM objects, as described by type-library files. The PowerBASIC COM Browser exports an interface structure of a COM object for early-binding purposes in PowerBASIC code, and gives syntax reference and context-help on the interface members exposed by a COM object.[11]
Programming language[edit]
Characteristics[edit]
PowerBASIC is a native-code BASIC compiler whose reported merits are simplicity of use and speed compared to other languages.[12][13]Although the compiled code is fast enough for most purposes, the compilers also support inline assembler for additional code optimizing. The Windows compilers (PBWin & PBCC) support almost all of the x86 instruction set, including FPU, SIMD, and MMX, the main exceptions being a few which are useful mostly to systems programmers. One can still use the unsupported instructions by inserting their opcodes with the 'db', 'dw', and 'dd' statements. Lines of assembler code can be freely interspersed with lines of BASIC code, although one must always consider the potential interactions between the two types of code.
Hello world[edit]
Hello world is used to give a very small example of the syntax used by a programming language and is often the smallest possible program for any given programming language.
Here is an example of a PBCC hello world program. By default PBCC creates a console window at runtime for displaying output. The only purpose of Waitkey$ in this example is to keep the console up so you can read the output.
Here is the PBWin version, which displays a Windows 'dialog' message box.
Object-oriented programming[edit]
PBWin and PBCC support object-oriented programming in the form of COM classes, however the compilers do not force you to use OOP, it is merely an option. In-process and out-of-process COM Servers can also be built using these compilers.
Graphics[edit]
Both the Console Compiler and Windows Compiler can create graphic windows. The GRAPHICs statements are higher-level than Windows' Graphics Device Interface (GDI) library functions.[14][15]
Elements of the GRAPHIC statements[edit]GRAPHIC WINDOWS are dedicated dialogs each containing a single control which fills the dialog's client area. GRAPHIC controls are child windows which support the same GRAPHIC drawing functionality as GRAPHIC windows. GRAPHIC BITMAPS are also defined, again supporting the GRAPHIC drawing functionality, but as purely memory objects, like Windows Bitmaps or DIB Sections. Keyboard and mouse handling statements are included among the GRAPHIC statements. Character output to a GRAPHIC target uses fonts specified via the FONT NEW statement.
Creating a GRAPHIC WINDOW application[edit]A GRAPHIC WINDOW is the equivalent of a Windows dialog box containing a static control on which drawing operations can be done. A single BASIC statement will create a GRAPHIC WINDOW and specify its size, position and title. It is not essential to specify a WNDPROC for the GRAPHIC WINDOW. A short source code example for a complete GRAPHIC WINDOW application follows:
Comparison of PB GRAPHIC statements with the GDI API[edit]Using PB GRAPHIC statements, a GRAPHIC (WINDOW, BITMAP, or control) is first selected as the current GRAPHIC target, then operations are done on it without requiring it to be identified again. Contrast this with the GDI API approach, where the Device Context handle is required for every drawing operation.
It is not necessary when using the PB GRAPHIC statements to define a brush or pen as a separate entity, nor is it necessary to redraw the GRAPHIC target (when in view) in response to Windows messages such as WM_PAINT and WM_ERASEBKGND. GRAPHIC targets are persistent.
When GRAPHIC targets are attached, a REDRAW option can be specified which buffers the results of drawing operations until they are specifically requested. Using this technique reduces flicker in a similar way to the technique of drawing on memory DCs[16] when using the GDI API.
Pixel operations are possible using the GRAPHIC GET|SET PIXEL statements, in a manner similar to GetPixel/SetPixel of the GDI API. GRAPHIC GET BITS allows the entire bitmap to be loaded into a dynamic string. This can be manipulated either as a string or by mapping an array onto it. It can be placed back into the GRAPHIC target by GRAPHIC SET BITS.
Complementarity of GRAPHIC statements and the Windows GDI API[edit]The GRAPHIC statements contain all the commonly used GDI API functions, but if you need one that is not included it is possible to obtain the hDC of any GRAPHIC target and thereby use GDI API functions on it.
User community[edit]
PowerBASIC provides an online forum for users to ask questions and share knowledge.[17] On 8 July 2012 the forum had 5,623 members (only a fraction of them still active) and contained 50,093 threads comprising 408,642 posts since August 26, 1998. The Source Code section alone contained 3,768 threads.[18]
Third-party support[edit]
References[edit]
- ^Release of PowerBASIC 10.0 Compiler for Windows
- ^'PowerBASIC makes smooth move; Tech company finds region's affordability attractive'. Sarasota Herald Tribune (October 2000). 2000-10-10. Retrieved 2008-03-12.
- ^Michael H. Tooley (2005). PC Based Instrumentation and Control. Elsevier. pp. 214. ISBN0-7506-4716-7.
- ^'An Introduction to PowerBASIC'. Archived from the original on 2011-05-27. Retrieved 2010-12-07.
- ^Zale, Vivian. 'PowerBASIC Update'. PowerBASIC Forums. PowerBASIC. Retrieved 5 July 2015.
- ^Eccles, John. 'PowerBASIC Plans'. PowerBASIC Forums. PowerBASIC, Inc. Archived from the original on 24 September 2015. Retrieved 5 July 2015.
- ^Drake, Adam (January 31, 2017). 'PowerBasic Has a New Home'. PowerBasic Support Forums. Archived from the original on 2017-02-19.
- ^Zale, Vivian (February 12, 2017). 'Thank You'. PowerBasic Support Forums. Archived from the original on 2017-02-19.
- ^PowerBASIC 3.5 for DOS
- ^PowerBASIC Compiler for WindowsArchived 2008-03-08 at the Wayback Machine
- ^'Com Browser on PowerBASIC's website'.
- ^New geometries for new materials, Eric A. Lord, AlanLindsay Mackay, Srinivasa Ranganathan, Cambridge University Press, 2006, ISBN0-521-86104-7 ('a very simple user interface .. speed and power of the underlying C++ .. runs extremely fast') Google Books
- ^Chaos and Time-series Analysis, Julien C. Sprott, Oxford University Press, 2003, ISBN0-19-850840-9 ('easy to learn, powerful, and as fast as any C compiler I have encountered') Google Books
- ^https://www.powerbasic.com/support/help/pbwin/index.htm
- ^https://www.powerbasic.com/support/help/pbcc/index.htm
- ^Petzold, Charles (1998). Programming Windows Fifth Edition, Microsoft Press, ISBN978-1-57231-995-0
- ^https://www.powerbasic.com/support/pbforums/faq.php?faq=vb3_board_faq#faq_faq_forum_rules
- ^PowerBASIC's vBulletin forum software statistics
External links[edit]
- Books on Internet Archive:
September 29, 1987
TBWINDO
MULTI-LEVEL WINDOWS
FOR BORLANDS TURBO BASIC
Version 3.2
PURPOSE:
This utility creates incredibly quick multi-level windows
in Turbo Basic programs for IBM PC/XT/AT compatibles.
TEST DRIVE:
Compile and run the tutoring program TBDEMO32.BAS to get a
feel for features and speed.
FILES:
In this version, TBWINDO.ARC contains:
TBWINDO.INC - Turbo Basic window include file
TBMENU.INC - Menu include file
TBINPUT.INC - Structured input include file
QPRINT.BIN - Quick print inline subroutine
QPRINTC.BIN - Quick print between columns
QATTR.BIN - Re-attribute an area of the screen
QFILL.BIN - Fill an area of the screen with a
specified character and attribute
QSAVE.BIN - Save portion of screen
QREST.BIN - Restore portion of screen
RECOLOR.BIN - Screen area recoloring
TBDEMO32.BAS - Demonstration program source code
TBWIND32.DOC - This document file.
README.1ST - Most recent changes and corrections.
Assembly language source code for all BIN files is
included for all those interested. Any Suggestions for
improvements to the code would be appreciated, as I do not
USING TBWINDO
Include the TBWINDO.INC program in your program with the
following statement:
$INCLUDE 'TBWINDO.INC'
Set MW% variable equal to the maximum number of windows
you will have open at any one time.
- 1 -
Set the ScrnArray variable equal to the estimated total
memory required to save your screens. If you expreience a
subscript out of range error in the include file, increase
this variable. As a rough rule of thumb, start out with
the variable equal to 250 times the maximum windows (mw%)
variable.
You invoke the routines by means of a CALL with a list of
parameters, rather than a GOSUB.
Using the MAKEWINDOW procedure:
CALL
MAKEWINDOW(ROW%,COL%,ROWS%,COLS%,ATTR%,BRDRSEL%,SHADOW%,ZO
OM%)
Where: ROW - the screen row of the upper left hand corner
of your desired window. Value should be
between 2 and 23 (for reasons explained
below). WARNING - the subroutine does not
check for proper values. You must check these
yourself or accept the consequences.
COL - the screen column of the upper left hand
corner. Value should be between 2 and 79.
ROWS - the number of rows long the window should be.
COLS - the number of columns wide the window should
be.
ATTR - the attribute of the window colors.
BRDRSEL - the border you desire around the window.
Valid selections in this release are:
0 - No Frame (just a border of BACKground
color.)
1 - Single Line Frame
2 - Double Line Frame
3 - Single Horizontal Line, Double Vertical
Line
4 - Single Vertical Line, Double Horizontal
Line
SHADOW - Another 'switch' to indicate if the window
should have a black 'shadow' under it offset
down. This gives a three-dimensional effect
that seems to 'raise' the window away from the
screen. A value of 1 indicates a shadow is
desired on the left side, a value of 2
indicates the right side, while a value of 0
- 2 -
means no shadow.
ZOOM - A 'switch' used to indicate to the subroutine
if the window should 'grow' from a small box
at the midpoints of the coordinates to full
size. A value of 1 indicates the window should
grow. A value of 0 indicates it should not.
using the TITLEWINDOW procedure:
CALL TITLEWINDOW(LOC%,TITLE$)
Where: LOC - Indicates where the title should be placed.
Valid selections are:
1 - Top left hand corner
2 - Top center
3 - Top right hand corner
4 - Lower left hand corner
5 - Lower center
6 - Lower right hand corner
TITLE - The string data you would like printed.
NOTE: The TITLEWINDOW procedure uses the coordinates from
the most recent use of MAKEWINDOW. Use this
procedure only after a call has been made to
MAKEWINDOW.
Using the RemoveWindow procedure:
CALL REMOVEWINDOW
There are no parameters passed to this procedure. The
window created by the last call to MakeWindow is removed
from the screen.
Using the ClearWindow procedure:
CALL CLEARWINDOW
There are no parameters pass to this procedure. The
window created by the last call to MakeWindow is cleared
inside the frame.
Using the PrtWindow procedure:
CALL PRTWINDOW(ROW%,COL%,STRDAT%)
Where: ROW - Is the row within the window you want to
print on.
- 3 -
COL - Is the column within the window where you
Borland Compiler Download
want printing to start.
NOTE: The ROW and COL coordinates are relative to the
current window. Row 1 Col 1 refers to the first
character position inside the frame in the upper
left corner. No parameter checking is done so if
the string data exceeds the width of the window it
will spill out the right side.
STRDAT - Is the string data you want printed inside
the window.
Using the PrtCWindow procedure:
CALL PRTCWINDOW(ROW%,STRDAT$)
Where: ROW - Is the row within the window you want to
have your string data centered on.
NOTE: This procedure uses the current window and will
attempt to center the string data between the left
border and the right border. No parameter checking
is done so if the string data exceeds the width of
the window, it will spill out the sides.
STRDAT - Is the string data you want printed within
the window.
Using the FNATTR% function:
FNATTR%(FORE%,BACK%)
Turbo Basic Compiler Download
Where: FORE - is the foreground color. Any Turbo Basic
color number is valid.
BACK - is the backgound color. Any Turbo Basic
background color is valid.
FNATTR% returns the attribute of the colors specified.
Using the RECOLOR procedure:
CALL RECOLOR(OLDATTR%,NEWATTR%,SNOCHK%)
Where: OLDATTR - Is the attribute of the areas on the
screen you wish to change.
NEWATTR - Is the attribute of the color you want.
- 4 -
X% = SCREEN(1,1,1) ' RETURNS CURRENT SCREEN
' ATTRIBUTE
CALL RECOLOR(X%,FNATTR%(14,4))
This will recolor everything on the screen that
has the same attribute a the upper left corner of
the screen to a foreground of 14 and a background
of 4.
Using the WINDOWXY procedure:
CALL WINDOWXY(ROW%,COL%)
Where: ROW = The row within the window.
COL = The column within the window.
This procedure is similar to Basic's LOCATE command except
the ROW and COL coordinates are relative to the current
window. Row 1 Col 1 refers to the first character
position inside the frame in the upper left corner. No
parameter checking is done so it is possible to locate
outside the window.
Using the MAKEMENU procedure:
Define and title your menu with calls to MakeWindow and
TitleWindow. Then define the selections available to the
user in a string array named item$(). Assign the total
selections available to itemcount% and the starting
selection number to startpos%. Now CALL MAKEMENU.
When a selection has be made in the MakeMenu procedure the
item number selected will be assigned to the variable
curntpos%. You can now use this number to direct the flow
of you main program. Please see the source code of the
Borland Turbo Basic Compiler Download Fast Auto Clicker
demo program for a better understanding. One point toremember is that a MENU window is no different than any
other window. You can pop one over the other and remove
them as would a normal window.
All of the above variables with the exception of the
string variables must either be declared globally as
integers by means of a DEFINT statement early in the
program; or must have the specific integer identifier
(%) attached wherever they appear in the program. The
BASIC compiler is picky about this; so be sure to
verify that the type assignment is correct.
TBWINDO requires no special handling when it comes to
compiling your program. Just make certain that all of
your variables passing parameters to the TBWINDO
subroutine are identified as integers, and you will be
- 5 -
able to proceed with the compile operation as with any
other program.
Borland C++ Compiler
ACKNOWLEDGEMENTS
I would like to express my thanks to Dave Evers
(BASWIN22), Tom Hanlin (ADVBAS33) and Jim LeMay
(WINDOW33). The routines presented are patterned after
routines that were written by them for MicroSoft Quick
Basic and Borland Turbo Pascal.
These utilities are released into the public domain for
anyone to use as they see fit however, anyone who feels
inspired and would like to contribute to my printer paper
and computer supplies fund may feel free to do so.
Rick Fothergill
141 Oak Hill Road
Pittsfield, MA 01201
(413) 442-2456
GEnie Address: R.FOTHERGILL
Compuserve: 76210,443
BBS: (413) 499-7245 300-1200-2400 Baud N-8-1
8:00am - 4:00pm Monday through Friday
USING TBWINDO
Include the TBWINDO.INC program in your program with the
following statement:
$INCLUDE 'TBWINDO.INC'
Set MW% variable equal to the maximum number of windows
you will have open at any one time.
- 1 -
Set the ScrnArray variable equal to the estimated total
memory required to save your screens. If you expreience a
subscript out of range error in the include file, increase
this variable. As a rough rule of thumb, start out with
the variable equal to 250 times the maximum windows (mw%)
variable.
You invoke the routines by means of a CALL with a list of
parameters, rather than a GOSUB.
Using the MAKEWINDOW procedure:
CALL
MAKEWINDOW(ROW%,COL%,ROWS%,COLS%,ATTR%,BRDRSEL%,SHADOW%,ZO
OM%)
Where: ROW - the screen row of the upper left hand corner
of your desired window. Value should be
between 2 and 23 (for reasons explained
below). WARNING - the subroutine does not
check for proper values. You must check these
yourself or accept the consequences.
COL - the screen column of the upper left hand
corner. Value should be between 2 and 79.
ROWS - the number of rows long the window should be.
COLS - the number of columns wide the window should
be.
ATTR - the attribute of the window colors.
BRDRSEL - the border you desire around the window.
Valid selections in this release are:
0 - No Frame (just a border of BACKground
color.)
1 - Single Line Frame
2 - Double Line Frame
3 - Single Horizontal Line, Double Vertical
Line
4 - Single Vertical Line, Double Horizontal
Line
SHADOW - Another 'switch' to indicate if the window
should have a black 'shadow' under it offset
down. This gives a three-dimensional effect
that seems to 'raise' the window away from the
screen. A value of 1 indicates a shadow is
desired on the left side, a value of 2
indicates the right side, while a value of 0
- 2 -
means no shadow.
ZOOM - A 'switch' used to indicate to the subroutine
if the window should 'grow' from a small box
at the midpoints of the coordinates to full
size. A value of 1 indicates the window should
grow. A value of 0 indicates it should not.
using the TITLEWINDOW procedure:
CALL TITLEWINDOW(LOC%,TITLE$)
Where: LOC - Indicates where the title should be placed.
Valid selections are:
1 - Top left hand corner
2 - Top center
3 - Top right hand corner
4 - Lower left hand corner
5 - Lower center
6 - Lower right hand corner
TITLE - The string data you would like printed.
NOTE: The TITLEWINDOW procedure uses the coordinates from
the most recent use of MAKEWINDOW. Use this
procedure only after a call has been made to
MAKEWINDOW.
Using the RemoveWindow procedure:
CALL REMOVEWINDOW
There are no parameters passed to this procedure. The
window created by the last call to MakeWindow is removed
from the screen.
Using the ClearWindow procedure:
CALL CLEARWINDOW
There are no parameters pass to this procedure. The
window created by the last call to MakeWindow is cleared
inside the frame.
Using the PrtWindow procedure:
CALL PRTWINDOW(ROW%,COL%,STRDAT%)
Where: ROW - Is the row within the window you want to
print on.
- 3 -
COL - Is the column within the window where you
Borland Compiler Download
want printing to start.
NOTE: The ROW and COL coordinates are relative to the
current window. Row 1 Col 1 refers to the first
character position inside the frame in the upper
left corner. No parameter checking is done so if
the string data exceeds the width of the window it
will spill out the right side.
STRDAT - Is the string data you want printed inside
the window.
Using the PrtCWindow procedure:
CALL PRTCWINDOW(ROW%,STRDAT$)
Where: ROW - Is the row within the window you want to
have your string data centered on.
NOTE: This procedure uses the current window and will
attempt to center the string data between the left
border and the right border. No parameter checking
is done so if the string data exceeds the width of
the window, it will spill out the sides.
STRDAT - Is the string data you want printed within
the window.
Using the FNATTR% function:
FNATTR%(FORE%,BACK%)
Turbo Basic Compiler Download
Where: FORE - is the foreground color. Any Turbo Basic
color number is valid.
BACK - is the backgound color. Any Turbo Basic
background color is valid.
FNATTR% returns the attribute of the colors specified.
Using the RECOLOR procedure:
CALL RECOLOR(OLDATTR%,NEWATTR%,SNOCHK%)
Where: OLDATTR - Is the attribute of the areas on the
screen you wish to change.
NEWATTR - Is the attribute of the color you want.
- 4 -
X% = SCREEN(1,1,1) ' RETURNS CURRENT SCREEN
' ATTRIBUTE
CALL RECOLOR(X%,FNATTR%(14,4))
This will recolor everything on the screen that
has the same attribute a the upper left corner of
the screen to a foreground of 14 and a background
of 4.
Using the WINDOWXY procedure:
CALL WINDOWXY(ROW%,COL%)
Where: ROW = The row within the window.
COL = The column within the window.
This procedure is similar to Basic's LOCATE command except
the ROW and COL coordinates are relative to the current
window. Row 1 Col 1 refers to the first character
position inside the frame in the upper left corner. No
parameter checking is done so it is possible to locate
outside the window.
Using the MAKEMENU procedure:
Define and title your menu with calls to MakeWindow and
TitleWindow. Then define the selections available to the
user in a string array named item$(). Assign the total
selections available to itemcount% and the starting
selection number to startpos%. Now CALL MAKEMENU.
When a selection has be made in the MakeMenu procedure the
item number selected will be assigned to the variable
curntpos%. You can now use this number to direct the flow
of you main program. Please see the source code of the
Borland Turbo Basic Compiler Download Fast Auto Clicker
demo program for a better understanding. One point toremember is that a MENU window is no different than any
other window. You can pop one over the other and remove
them as would a normal window.
All of the above variables with the exception of the
string variables must either be declared globally as
integers by means of a DEFINT statement early in the
program; or must have the specific integer identifier
(%) attached wherever they appear in the program. The
BASIC compiler is picky about this; so be sure to
verify that the type assignment is correct.
TBWINDO requires no special handling when it comes to
compiling your program. Just make certain that all of
your variables passing parameters to the TBWINDO
subroutine are identified as integers, and you will be
- 5 -
able to proceed with the compile operation as with any
other program.
Borland C++ Compiler
ACKNOWLEDGEMENTS
I would like to express my thanks to Dave Evers
(BASWIN22), Tom Hanlin (ADVBAS33) and Jim LeMay
(WINDOW33). The routines presented are patterned after
routines that were written by them for MicroSoft Quick
Basic and Borland Turbo Pascal.
These utilities are released into the public domain for
anyone to use as they see fit however, anyone who feels
inspired and would like to contribute to my printer paper
and computer supplies fund may feel free to do so.
Rick Fothergill
141 Oak Hill Road
Pittsfield, MA 01201
(413) 442-2456
GEnie Address: R.FOTHERGILL
Compuserve: 76210,443
BBS: (413) 499-7245 300-1200-2400 Baud N-8-1
8:00am - 4:00pm Monday through Friday
- 6 -
TBWINDO QUICK REFERENCE
MakeWindow(Row%,Col%,Rows%,Cols%,Attr%,BrdrSel%,Shadow%,Zo
om%)
TitleWindow(Loc%,Title$)
RemoveWindow
ClearWindow
Borland C Compiler For Windows
MakeMenuPrtWindow(Row%,Col%,StrDat$)
PrtCWindow(Row%,StrDat$)
FNAttr%(Fore%,Back%)
Borland Turbo Basic Compiler Download Fast Download
WindowXY(Row%,Col%)
Qsave(Row%,Col%,Rows%,Cols%,Scrn%(??))
QRest(Row%,Col%,Rows%,Cols%,Scrn%(??))
ReColor(OldAttr%,NewAttr%,SnoChk%)
Qprint(Row%,Col%,StrDat$,Attr%)
QprintC(Row%,ColLeft%,ColRight%,StrDat$,Attr%)
QFill(Row%,Col%,Rows%,Cols%,Char%,Attr%)
QAttr(Row%,Col%,Rows%,Cols%,Attr%)
QBox(Row%,Col%,Rows%,Cols%,Attr%,BrdrSel%)
- 7 -
001a
