Recent content by Niek

Ok - any idea when this might be fixed?

Using conditional compilation is corrupting the contents list? After using $IF $THEN $END it is no longer generating the content list correctly. Is this a known issue? And if so, when will it be fixed?

Thanks Marco! I did try this out and this is working great - it seems there are more changes within this pre-release. Some things are working differently now. It seems that line prefixes are not working - even '--' is not ignored anymore. For example try generating doc for the following...

plsqldoc cannot handle EZconnect names for database correctly: \\localhost\orcl it is complaining that it cannot find the directory \localhost\orcl. Creating that directory manually will not solve the problem when using multiple databases.

Is it possible to add an option to look for comments below program unit definitions? We do have all our program unit comments below the definitions itself. When you click on the contents you will jump the the top of the program unit itself and you will see the comments directly below it. With...

Generating documentation for this package specification is not correct - it will ignore all contents after a second line comment is found in combination with the tags and custom plsqldoc tags... Try it to see what I mean. This section is wrong: %History <code> #! 01/01/01 XX NNNNNN...

Generating documentation for this package is corrupting the synopsis and the actual format. Also spacing is not correct for tables made up with +-| (which looks pretty when using a non proportional font). CREATE OR REPLACE PACKAGE test /** Package spec text */ IS /** This is test...

All information that is meta data should not get cross-referenced. For example if you define an ID field as a view column it should not get cross-referenced at all in the 'Name' column (it will right now if you have a column id defined somewhere). Also having a column 'Y' defined all Optional...

Is it possible to enhance the cross-reference options - since when turned on it will for example reference all 'id' text to the first occurrence in the documentation that can be referenced. Global cross reference is very handy when generating documentation for views and have links for table...

Using the following options: Format: One parameter per line 'Align datatypes' enabled 'Comma after datatype' disabled 'List at left margin' enabled Will result in: PROCEDURE insertdept ( p_deptno IN OUT dept.deptno%TYPE ,p_dname IN dept.dname%TYPE ,p_loc IN dept.loc%TYPE ) IS I was...

I have a procedure defined in a package structured like this: PROCEDURE set_test ( p_test_string VARCHAR2 , o_keep PLS_INTEGER := 1 ); Disabling the Format program unit declarations will result in Procedure set_test(p_test_string VARCHAR2 , o_keep PLS_INTEGER := 1 ) It...

Using --! or --anything as a line prefix, it will not suppress the prefix It will ignore the --, but not !. So all lines are starting with !. Is this an internal parser problem - hence can it be fix? ini file: LinePrefixes=--!,--$,--^

I am getting an error after entering a valid license number (the status bar of AA Installer is changed to our Serial Number etc.): Error while unpacking files! I tried this on different boxes, but got the same problem. Any ideas?

Would like to line out the INs and OUTs too. Output of beautified version: PROCEDURE test ( ,p_price NUMBER ,p_id IN NUMBER ,p_flag OUT BOOLEAN ,p_last_name IN OUT VARCHAR2 ) IS BEGIN NULL; END test; But I prefer the code fragment below: PROCEDURE test ( p_price...

Would like to have an option to add the package / procedure / function / ... name after the END of such object: PROCEDURE test(p_id NUMBER) IS BEGIN NULL; END test;