int QisLib_GetOASIS(const char* OutFileName);

	OutFileName: Name and path of the OASIS file to be created.

	success: 0
	failure: one of the following values :

Error Codes:
	-1: QisLib has not been initialized.
	-2: The specified path is invalid (null).
	-3: No OASIS file opened.
	-4: Cannot save OASIS output file with the same name and path as input file.
	-5: File I/O error occurred while creating OASIS output.
	-6: File open in progress, operation not permitted.

	- This function can be used to extract OASIS data in the current window to a flat
	OASIS file with no hierarchy.
	- The extracted OASIS file does not contain any cell hierarchy even if the input file
	is hierarchical. The top cell is called 'TOP'. The data is clipped at the window
	- All display filters are disregarded while creating the OASIS file.
	- Output entities are boundaries. Any paths are converted into boundaries unless they
	have zero width in which case they are ignored.
	- Data is output on the same layer as the input. However QisLib_SetOutputLayerMap can
	be used to control the mapping of the input layers to different output layers.
	- If the user's program needs to set a particular window for extraction, it should use
	QisLib_SetExactWindow since QisLib_SetExactWindow makes no adjustments to the window
	extents based on the image size aspect ratio. However, the user's program must also
	make sure to restore the original window extents once the extraction is done.
	- This function cannot be used to write to an OASIS file currently opened. OutFileName
	must be different from the name or path of the currently opened OASIS file.
	- By default, the grid of the extracted OASIS file are same as the input OASIS file.
	However, different output grid can be controlled using the QisLib_SetDBU and
	QisLib_SetResolution functions.
	- QisLib_GetOASIS output is affected by current settings such as layer on/off, nesting
	level, array mode etc.
	- It is not necessary to open the OASIS input file in edit mode to use this function.
	- If QisLib_SetOASISCompression is on, the output file will have CBLOCKs in the cells.
	- QisLib does not emit any progress message even if a progress message callback
	function has been set using QisLib_SetProgressMessageCallback.
	- If this operation needs to be cancelled, use QisLib_Stop. This can only be done if
	QisLib_SetProcessEvents is turned on. Also, for Unix/Linux, the program's
	application context must be passed to QisLib_InitLib.