OpenLLM-France/wikimedia huggingface dataset:
# History of wireless telegraphy and broadcasting in Australia/Topical/Publications/Australasian Radio World/Issues/1945 04
## P.03 - Contents Banner

THE AUSTRALASIAN RADIO WORLD
Devoted entirely to Technical Radio
and incorporating
ALL-WAVE ALL-WORLD DX NEWS
VOL. 9. - APRIL, 1945 - No. 11

## P.03 - Publication Notes

PROPRIETOR — A. G. HULL
Manager - DUDLEY L. WALTER
Secretary - Miss E. M. VINCENT
Short-wave Editor — L. J. KEAST
For all Correspondence: City Office — 243 Elizabeth St., Sydney, Phone: MA2325
Office Hours — Weekdays: 10 a.m.-5 p.m. Saturdays: 10 a.m.-12 noon
Editorial Office — 117 Reservoir Street, Sydney
Victorian Advertising Representative — W. J. LEWIS, 379 Collins St., Melbourne, 'Phone MU4725
Subscription Rates: 6 issues - 5/3; 12 issues - 10/6; 24 issues - £1; Post free to any address.
Service Departments — Back Numbers, 1 /- ea. post free; Reply-by-mail Queries, 1/- each
Printed by Bridge Printery Pty. Ltd., 117 Reservoir Street, Sydney, N.S.W., for the proprietor of the "Australasian Radio World," Elizabeth St., Sydney (Footnote P.36)

## P.03 - Contents

CONTENTS
CONSTRUCTIONAL —
Balanced Linear V.T.V.M. . . . . 5
TECHNICAL —
Continental Design . . . . 11
Contrast Without Distortion . . . . 15
Aegis Components Do War Job . . . . 17
A Short Course In Radio Fundamentals - Part 3 . . . . 18
Technical Review from U.S.A. . . . . 25
Production of Audio Frequencies . .. . . . . .. .. . 27
SHORTWAVE REVIEW —
Notes From My Diary . . . . 30
New Stations . . . . 31
Loggings . . . . 32
The Service Pages —
The Service Pages . . . . 34

## P.03 - Editorial

EDITORIAL.
Several readers have written to let me know how much they appreciate the varied style of the articles now being presented in Australasian Radio World. From near and far come contributions, some of them possibly lacking in the niceties of journalism, but all from the hearts of enthusiastic radio men just like you and me. It takes an exception to prove the rule, and so I also find that some people are not in agreement with views expressed by contributors, and so they abuse me for not exercising greater editorial supervision. I can imagine that I am going to get into really hot water for publishing Mr. Stevens' article in this issue. Paul Stevens claims that Australian radio engineers have slavishly followed American design, thereby doing the wrong thing. Personally I do not think that Mr. Stevens has presented both sides of the case, nor do I think that his arguments are all entirely sound, yet I feel that the article is well worth publishing exactly as submitted. Some of my thin-skinned friends are going to be hurt by the inferences; others may be shocked by the audacity of anyone daring to suggest that our set designers are not infallible. My courage comes from the thought that in these days of so much talk about freedoms, that my readers should have the right to freely criticise, so long as their criticism is within the bounds of reason. Those who do not agree with views expressed will be gladly afforded space to state their claims and present their cases.
# FINDERINFO function
## FINDERINFO
### Function

✔ Appearance ✔ Standard ✔ Console

### Syntax

Move all waiting items to arrays or simple variables
countVar = maxAcceptableentries action = ¬  FINDERINFO(countVar%, nameVar$, typeVar&, dirRefNumVar%)
Find out how many items are waiting to be picked up
countVar = 0 action = ¬  FINDERINFO(countVar%, nameVar$, typeVar&, dirRefNumVar%)
Pick up an indexed item from the list
countVar = negativeIndex action = ¬  FINDERINFO(countVar%, nameVar$, typeVar&, dirRefNumVar%)
Gather a list of file spec records
countVar = maxAcceptableentries action = ¬  FINDERINFO(countVar%, @FSSpec[(array)],@OSType&[(array)], dirRefNumVar%)
Clear the list
FN CLEARFINDERINFO

### Description

If the user launched your application by double-clicking a document icon, or by dragging document icon(s) to your application's icon, or by selecting document icon(s) and then selecting "Open" or "Print" from the Finder's "File" menu, then you can use the FINDERINFO function to determine which document file(s) were involved, and whether they should be opened or printed.
You should call FINDERINFO once, soon after your program starts. You should also check during null events to see if additional files have been added to the list. This can take place when an _openDoc event is sent from another application or when the user drags a file onto the icon of your running application.
* action - The result of the FINDERINFO function is one of the following:
Image was here.
* countVar - This variable is used to send a value to and receive a result from FINDERINFO
Image was here.
The parameters for FINDERINFO are used to both send and receive values. In order to send a value of "1" for the count, you must first set the variable, then check it on return.
count% = 0 action = FINDERINFO(count%,fName$,fType&,vRefNum%) PRINT "There are" count%" files in the queue."
Image was here.
Note: Before your application can support Finder-launched documents, you need to set up certain special resources (BNDL and FREF) in your application's resource fork. Also, FINDERINFO will not work unless the "High-level event aware" flag is turned on in your application's SIZE resource #-1. See the "Finder Interface" chapter in Macintosh Toolbox Essentials for more information.
# FIX function

* FIX
* Function
* ✔ Appearance ✔ Standard ✔ Console
* Syntax
* wholeNum# = FIX(expr#)
* Description
* This function returns a whole number representation of expr# (it strips off digits to the right of the decimal point). Although FIX always returns an integer, the number it returns is considered to be a double-precision floating-point value.
* See Also
* FRAC; INT
# FN <toolbox> function

* FN <toolbox>
* Function
* ✔ Appearance ✔ Standard ✔ Console
* Syntax
* result = FN ToolboxFunctionName [modifiers] ¬
* [([{#addrExpr1&|arg1}[,{#addrExpr2&|arg2}...]])]
* Description
* This function executes a Toolbox function as defined in Inside Macintosh. A Toolbox function (as opposed to a Toolbox procedure) returns a value.
* ToolboxFunctionName must be the name of a Macintosh Toolbox function. FB recognizes the names of hundreds of Toolbox functions and procedures; advanced programmers can also use the TOOLBOX statement and the TBALIAS statement to add new Toolbox function/procedure names.
* The use of the modifiers, addrExpr& and arg parameters is identical to their use in the CALL <toolbox> statement. See the description of the CALL statement for more information.
* See Also
* CALL
# FLUSHEVENTS statement

* FLUSHEVENTS
* Statement
* ✔ Appearance ✔ Standard ✔ Console
* Syntax
* FLUSHEVENTS
* Description
* This statement removes all pending events from the system event queue and from FutureBasic's internal event queues. This is useful when you want to prevent your event-handling functions from processing any old events that may currently exist in the queue. FLUSHEVENTS does not inhibit future events from being put into the queue.
* See Also
* EVENT; ON EVENT
# Futurebasic/Language/Reference/filesstr fopen
## FILES$(_fOpen...)
### Function

✔ Appearance ✔ Standard ✔ Console

### Syntax

fileName$ = FILES$(_fOpen,[typeListString$],¬  [promptString$], refNumVar%) fileName$ = FILES$(_fOpenPreview,[typeListString$],¬  [promptString$], refNumVar%) fileName$ = FILES$(_FSSpecOpen,[typeListString$],¬  [promptString$], fileSpecRecord) fileName$ = FILES$(_FSSpecOpenPreview,[typeListString$],¬  [promptString$], fileSpecRecord)
gFBUseNavServices = _zTrue|_false

### Revised

February, 2002 (Release 6)

### Description

This function prompts the user to select an existing file. It does this by displaying the standard "Get File" dialog shown below (its appearance may be different on some systems). If the user selects a file, then the file's name is returned in fileName$, and a reference number for the file's directory is returned in refNumVar% (which must be a short integer variable). If the selected file is in a volume's root directory, the refNumVar% will return a volume reference number; otherwise, it will return a working directory reference number. If the user cancels the dialog, then the function returns an empty (zero-length) string, and it sets refNumVar% to zero.
If the global variable gFBUseNavServices is non-zero, FB switches to the more modern Navigation Services dialog. If the one of the FSSpec version of the call is used, gFBUseNavServices is assumed to be _zTrue.
You can limit the types of files that appear in the dialog by specifying up to four file types in typeListString$. For example, is you pass the string "TEXTPICT" in typeListString$, then only files of type "TEXT" and type "PICT" will be available for selection. If typeListString$ is an empty string, or the parameter is omitted, then all file types will be available for selection.
Image was here
If you use the optional _fOpenPreview (or _FSSpecOpenPreview ) parameter, the standard files dialog may display a preview of the file currently selected.
Image was here.
Note: The FILES$(_fOpen...) function does not actually open the selected file. Use the OPEN statement if you need to open the file.
The reference number returned in refNumVar% is a temporary number, which is only valid until your program quits. You cannot use this same number to refer to this folder at a later date. If you need to keep track of a file's location over time, create and save an alias record for the file.

### See Also

FILES$; FILES$(_fSave...); FOLDER; OPEN; Appendix H: file Spec Records
# Futurebasic/Language/Reference/fill
## FILL
### Statement

✔ Appearance ✔ Standard ✔ Console

### Syntax

FILL h,v

### Description

This statement fills the area around pixel coordinates (h, v) (in the current output window) with the current color and pen pattern. All the contiguous pixels which have a color equal to the original color at (h, v) are included in the fill.
Example: This little program paints a red ring:
COLOR = _zBlack CIRCLE 110,110,100 CIRCLE 110,110,80 COLOR = _zRed FILL 100, 15
FB Lite behavior: When you use the "FB Lite" runtime, FILL switches to the Graphics Window before executing.

### See Also

COLOR; CIRCLE
# Futurebasic/Language/Reference/filesstr fsave
## FILES$(_fSave...)
### Function

✔ Appearance ✔ Standard ✔ Console

### Syntax

fileName$ = FILES$(_fSave,[prompt$],[defaultName$],refNumVar%) fileName$ = FILES$(_FSSpecSave,[prompt$],[defaultName$],fileSpecRecord)
gFBUseNavServices = _zTrue|_false

### Revised

February, 2002 (Release 6)

### Description

This function prompts the user to provide a file name, and to select a folder where the file may be saved. It does this by displaying the standard "Put File" dialog shown below (its appearance may be different on some systems). If the user selects a name, then the name is returned in fileName$, and a reference number for the selected directory is returned in refNumVar% (which must be a short integer variable). If the selected directory is a volume's root directory, then refNumVar% will return a volume reference number; otherwise, it will return a working directory reference number. If the user cancels the dialog, then the function returns an empty (zero-length) string, and it sets refNumVar% to zero.
The string (if any) that you provide in prompt$ will appear as a one-line prompt in the dialog. The string (if any) that you provide in defaultName$ will appear initially in the file name edit field in the dialog.
If the global variable gFBUseNavServices is non-zero, FB switches to the more modern Navigation Services dialog.. If the one of the FSSpec version of the call is used, gFBUseNavServices is assumed to be _zTrue.
Example: The statement:
fileName$ = FILES$(_fSave,"Save game as:", "Game 1",refNum%)
will produce a dialog that looks something like this:
Image was here.
Note: The FILES$(_fSave...) function does not actually open or save a file. Use the OPEN statement if you need to open a file, and use output statements like PRINT# or WRITE# to save information into it.
The reference number returned in refNumVar% is a temporary number, which is only valid until your program quits. You cannot use this same number to refer to this folder at a later date. If you need to keep track of a file's location over time, create and save an alias record for the file.
# Futurebasic/Language/Reference/filesstring function
## FILES$
### Function

✔ Appearance ✔ Standard ✔ Console

### Syntax

fileType$ = FILES$

### Description

Returns the file type of the last file returned by the FILES$(_fOpen...) function, as a 4-character string. If the user clicked "cancel" in response to the last File Open dialog, or if the FILES$(_fOpen...) function has never yet been executed, then the FILES$ function returns an empty (zero-length) string.
Note: In some cases it's useful to express the file type as a 4-byte long integer rather than as a string. Use the MKI$ function and the CVI function to convert between these two forms.
# FLUSHWINDOWBUFFER statement
## FLUSHWINDOWBUFFER
### Statement

✔ Appearance ✔ Standard ✔ Console

### Syntax

FLUSHWINDOWBUFFER [{wRef | {_FBAutoFlushOff |_FBAutoFlushOn}]

### Revised

April 2003 (Release 8)

### Description

Under OS X, all drawing to a window is intercepted and stored ("buffered") by the Window Server. The Window Server normally transfers the drawing to the screen only when your program executes a HANDLEEVENTS statement. You can force an early update with FLUSHWINDOWBUFFER.
If wRef is omitted, or is 0, the current output window is flushed by the OS X Window Server. If wRef is non-zero, window wRef is flushed.
The default behavior of the FutureBASIC runtime is to flush the current output window each time a PRINT statement is performed. You can control that behavior: FLUSHWINDOWBUFFER _FBAutoFlushOff will turn off the automatic flushing. You still can force the flushing for a specific window with FLUSHWINDOWBUFFER wRef. FLUSHWINDOWBUFFER _FBAutoFlushOn will restore the automatic flushing.
The FLUSHWINDOWBUFFER command has no effect unless the program is running under OS X.
Example:
// In this example, there is no HandleEvents, // and so FlushWindowBuffer is needed to // make the drawing visible under OS X.
WINDOW 1 PLOT 0,0 TO 500,500
FLUSHWINDOWBUFFER
DO UNTIL FN BUTTON // wait for mouse-down
# Horticulture/Rorippa sylvestris

Yellow Fieldcress :
| Binomial: | Rorippa sylvestris |
| Vegetative Spread: | Long rhizomes |
Rorippa sylvestris (Creeping Yellowcress, Keek, Yellow Fieldcress; syn. Radicula sylvestris (L.) Druce) is an invasive species) in the United States.

## Description

Rosette-forming perennial with pinnatifid leaves and clusters of yellow flowers. Colonizes rapidly via underground rhizomes.

## Ecology

Considered a noxious weed in parts of the United States.

## Control

* Mowing: Ineffective
* Cultivation: Grows back from small root fragments
* Barriers: Paper/mulch barriers

## References

* ↑ Rorippa sylvestris at USDA PLANTS Database
* ↑ Rorippa sylvestris at The Herbarium of Louisiana State University
* ↑ Rorippa sylvestris at Invasive.org
# Horticulture/Rock Gardens

See:
* Rock gardens
* Japanese rock gardens (枯山水)
For plants, see:
* Mosses and Bryophites
* Lichen
# Horticulture/Resistant Varieties

Resistant varieties are plants within a certain group that are less vulnerable to attack by plant pests or diseases. In seed catalogs, these are often indicated by codes, which may vary from company to company.
The use of resistant varieties is strongly recommended if pest or disease issues have arisen in the past.
This page is a stub entry in Horticulture. Please see the Manual of Style for guidelines on how to expand it.
# Horticulture/Rosaceae

The Rose Family :
| Family: | Rosaceae |
| Pest issues: | Some serious pests are common to the family |
| Disease issues: | Some serious diseases are common to the family |
| Pollination: | Insects |
The Rosaceae or rose family is a large family of plants, with about 3,000-4,000 species in 100-120 genera. Traditionally it has been divided into four subfamilies: Rosoideae, Spiraeoideae, Maloideae, and Amygdaloideae. These subfamilies are primarily diagnosed by the structure of the fruits, although this approach is not followed universally. Recent work has identified that the traditional four subfamilies are not all monophyletic, but the structure of the family is still awaiting complete resolution.
Identified clades include:
Amongst these groups, Neillieae appears to be the sister group to Maloideae, and Dryadeae may be a sibling group to Rosoideae. Other genera, for example Kerria, appear not to belong to any of these groups.

## Genera and species

* Agrimonia
* Alchemilla
   * Alchemilla mollis
* Cotoneaster
* Fragaria
* Malus
* Prunus
* Pyrus
* Rosa
# Horticulture/Rosmarinus

Rosemary :
| Genus: | Rosmarinus |
| Family: | Lamiaceaae |
| Pollination: | Insects |
| Toxicity and edibility: | Edible |
Rosmarinus is a small genus of woody, perennial herbs with fragrant evergreen needle-like leaves in the family Lamiaceae, native to the Mediterranean region.

## Varieties

There are just two species, Rosmarinus officinalis (Rosemary), widespread in the Mediterranean region, and Rosmarinus eriocalyx, native to northwest Africa and southern Spain. The latter differs from the well-known herb rosemary in its smaller leaves, only 5-15 mm long and less than 2 mm broad, and densely hairy flower stems. It also tends to be lower-growing, often under 25 cm tall and prostrate, and never exceeding 1 m tall (R. officinalis can reach 1.5 m, exceptionally 2 m, tall).
# Horticulture/Tarsonemidae

Tarsonemid mites :
| Type: | Mites |
| Family: | Tarsonemidae |
| Order: | Acari |
| Damaging stages: | All |
| Season: | Warm season |
| Vulnerable stages: | All |
Tarsonemidae is a family of mites, also called the thread-footed mites or tarsonemid mites. Only a limited number tarsonemid genera, Steneotarsonemeus, Polyphagotarsonemus, Phytonemus, Floridotarsonemus and Tarsonemus, are known to feed on higher plants while most species in this family feed on the thin-walled mycelia of fungi or possibly algal bodies (Jeppson, 1975). Even among the plant-feeding tarsonemid mites, most are confined to areas of new growth where cell walls are thin and therefore easily pierced. However two species (broad mite and cyclamen mite) are able to feed on older leaves because of their ability to inject toxins during feeding (presumably of salivary gland origin) causing an increase of thin walled cells surrounding feeding sites (Jeppson, 1975). This proliferation of new growth often results in leaves that appear stunted, puckered and twisted (Jeppson, 1975).
While little pest management research has been done on the majority of tarsonemid species, comprehensive studies have been made into the biological and chemical control of the cyclamen mite and the broad mite. Chemical trials demonstrated that Endosulfan and Dicofol consistently reduced densities of P. latus and P. pallidus (Rai, et. al, 2004, Sterk, et. al, 1997), and planting stock can be effectively decontaminated through fumigation with Methyl bromide or Ethylene dibromide (Jeppson, 1975). Three entomogenous fungi, Beauveria bassiana, Metarhizium anisopliae, and Paecilomyces fumosoroseus, can effectively manage broad mite infestations, with B. bassiana providing the greatest reduction (Nugroho, 2004). Predatory phytoseiid mites, in the genus Neoseiulus, can also successfully control P. latus and P. pallidus under greenhouse and field conditions (Croft, et. all, 1998, Weintraub, et. al 2003).

## Control

* Organic pesticides: Horticultural Oil, Neem Oil
# Horticulture/Tetranychus urticae

Twospotted Spider Mite :
| Type: | Mite |
| Binomial: | Tetranychus urticae |
| Family: | Tetranychidae |
| Order: | Acari |
Tetranychus urticae (an animal with over 60 common names, including red spider mite and two-spotted spider mite) is one of many species of plant-feeding mites found in dry environments, and generally considered a pest. It is the most widely known member of the family Tetranychidae or Spider mites.

## Description

During the summer, T. urticae has a greenish brown appearance with two darker spots, but as winter approaches it gains a strong red color. Some populations are pemanently greenish or reddish, and these are considered different species of Tetranychus by some authorities.

## Symptoms and Signs

Tetranychus urticae is extremely small, barely visible with the naked eye as reddish or greenish spots on leaves and stems; the adults measure about 0.5 mm. The red spider mite, which can be seen in greenhouses and tropical and temperate zones spinning a fine web on and under leaves. The red spider mite is extremely polyphagous; it can feed on hundreds of plants, including most vegetables and food crops (peppers, tomatoes, potatoes, beans, corn, strawberries) and ornamentals: roses, etc. It lays its eggs on the leaves, and it poses a threat to host plants by sucking cell contents from the leaves cell by cell, leaving very tiny, pale spots or scars where the green epidermal cells have been destroyed. Although the individual lesions are very small, commensurate with the small size of the mites, the frequently-observed attack of hundreds or thousands of spider mites can cause thousands of lesions and thus can significantly reduce the photosynthetic capability of plants, greatly reducing their production of nutrients, sometimes even killing the plants. Although this way of feeding could spread plant viruses, this is considered of secondary importance.

## Host plants

A wide range of hosts, including the folloring genera:
* Aquilegia (Columbine)
* Aster
* Cucumis (Cucumber, Melon)
* Cornus (Dogwood)
* Dahlia
* Dendranthema (Hardy Mum)
* Dianthus (Carnation)
* Hedera (Ivy)
* Hemerocallis (Daylily)
* Hosta (Plantain Lily)
* Hydrangea
* Impatiens
* Juniperus (Juniper)
* Lycopersicon (Tomato)
* Malus (Apple)
* Morus (Mulberry)
* Ocimum (Basil)
* Pachysandra
* Phlox
* Prunus (Stone Fruits)
* Pseudosasa (Arrow Bamboo)
* Rhododendron (Rhododendron, Azalea)
* Rosa (Rose)
* Rubus (Brambles)
* Salvia (Sage)
* Solanum
* Verbena
* Viburnum
* Viola (Violets)

## Control

* Biocontrols (microscopic): Its natural predator, (Phytoseiulus persimilis), commonly used as a biological control method, is one of many predatory mites which prey exclusively or mainly on spider mites.

## References

* How Red Mites affect the Poultry Industry - Article by the Poultry Youth Association
# Horticulture/Templates
## New page templates

* Fruit template (herbaceous) -- Use for herbaceous fruits often called "vegetables", such as tomato, cucumber, etc.
* Fruit template (woody) -- Use for woody fruit-bearing plants such as blueberry, grape, apple
* Vegetable template (leaf) -- For leafy vegetables such as lettuce
* Vegetable template (flower) -- For flower vegetables such as broccoli
* Vegetable template (root) -- For root vegetables such as garlic
* Template:Plantprof -- A general template for plant genera and species
* Template:Pgenprof -- A specific template for genera (possibly unneeded)
* Template:Weedprof -- For weeds
* Template:Pestprof Designed for arthropod pests such as insects or mites, but can be used for other pests.

## Infobox templates

* Template:Weedbox - for weeds
* Template:Gveggiebox - for leafy vegetables
* Template:Hortibox -
* Template:Treebox - for trees
* Template:Phytopathbox - for plant diseases

## Section templates

* Template:Weedcontrol - template for weed control sections

## Stub templates

Template:Horticulture/Stub - for template-related stubs
# Horticulture/Templates/Fruit template (herbaceous)

This page template is deprecated. Use {{subst:Plantprof}} instead and add the level three headlines as needed.