Opened 16 years ago
Last modified 16 years ago
#1327 closed defect
BaseFileExporter creates two parameter sections if the first plug-in parameter is 'section' — at Version 1
Reported by: | Nicklas Nordborg | Owned by: | Nicklas Nordborg |
---|---|---|---|
Priority: | critical | Milestone: | BASE 2.12.1 |
Component: | core | Version: | |
Keywords: | Cc: |
Description (last modified by )
For example:
If a BASE1 plug-in defines the first parameter as:
1 h section 30 cghBFCParams 0 ... and more parameters
the following is generated in the exported BASEfile:
BASEfile section cghBFCParams % section settings ... and more parameters
If the 'section' parameter is left out from the plug-in definition the file is created as expected:
BASEfile section settings ... and more parameters
This workaround only works if the plug-in in question doesn't care about the name of the section. Plug-ins that require the parameters section to have a specific name will not work.
Change History (1)
comment:1 by , 16 years ago
Description: | modified (diff) |
---|---|
Owner: | changed from | to
Status: | new → assigned |
Summary: | BaseFileExporter creates two parameter sections if the first plug-in parameter is 'section' with a value different from 'settings' → BaseFileExporter creates two parameter sections if the first plug-in parameter is 'section' |
Note:
See TracTickets
for help on using tickets.
Ooops... it turns out that duplicate sections are generated in all cases where the plug-in defines a 'section' parameter. It doesn't matter if the value is 'settings' or some other value. I'll change the description of the ticket.