Jump to content
Changes to the Jaspersoft community edition download ×

morlandin

Members
  • Posts

    666
  • Joined

  • Last visited

  • Days Won

    1

morlandin last won the day on November 15 2023

morlandin had the most liked content!

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

morlandin's Achievements

Proficient

Proficient (10/14)

  • Week One Done
  • One Month Later
  • One Year In
  • First Post Rare
  • Collaborator Rare

Recent Badges

2

Reputation

1

Community Answers

  1. Overview In this tutorial we will learn about Jaspersoft® Studio Layouts, how they work and how to configure them. For every layout, there will be an overview of its functionality and configuration options. About the Layouts Jaspersoft Studio Layouts are an automatic way to arrange elements inside a container, like frames, bands, cells and pretty much any element that can contain other elements. When a layout is set on a container, it takes care of arranging the child of the container in a way depending on the layout itself and how it is configured. Not all layouts require a configuration and a layout can also interact with elements of other containers in some complex cases. A Layout can forbid a common operation, like resizing and/or moving the elements inside the container, because the layout is handling this operation. To set a layout, simply select a container and select the layout from the appearance tab inside the properties view: Consider that a layout is used only at design time to help the user, and it is a Jaspersoft Studio feature. This means that it will never be used when a report is executed and if, for example, a container grows during an execution, then the layout is not used to re-arrange the content. Free Layout This is the layout used by default by every container and doesn’t arrange or put constraints on the elements inside the container. Horizontal/Vertical Layout The horizontal layout simply disposes the element into a row where every element has the same width and height. It takes all the elements inside the container and resizes them to fit the height of the container and arranges them to take the width of the container divided by the number of elements. The vertical layout works in a similar way, but it disposes the elements as columns. Neither layout allows resizing or moving of elements. Grid Layout The grid layout is a well known layout to UI designers. Its logic and most of its configuration options are the same. It disposes the elements like a grid where each element is a virtual cell, a specific column or row that can span and have a weight. When using this layout on a container all its child elements will show additional configuration properties in the appearance tab of the property view, which allows configuring how the element will be placed inside the layout. There properties are: Row Number, Column Number, Row Span, Column Span, Fixed Size, Row Weight and Column Weight. This layout doesn’t allow moving elements freely, but allows resizing them in some cases. Look at the property, Fixed Size, for more information. Row Number: this property defines the row taken by the element and can be a number or the special value, 'relative'. When set to 'relative', it uses the same row of the previous element. If it is set on the first element, then it counts as 0. When selecting a number, it will try to place the element in that specific row. If the row number is bigger than the actual number of row, the element will be placed on a new row after the last one, ignoring how big it is. This mean that no space is left between elements. For example: if I have 4 rows, and I set as row number of an element 10, then the element will be placed under the fourth row, creating a fifth. But, if after that, another element is created with row number 7, then it will take the fifth, and the previous one will take the sixth. Column Number: this property defines the column taken by the element and can be a number or the special value, 'relative'. It works exactly like the Row Number but on columns. Row Span: this is an integer value greater or equal to 1 and defines how many rows the element takes. Column Span: this is an integer value greater or equal to 1 and defines how many columns the element takes. Row Weight: defines the height of the current row. Every element has a weight greater or equal to 0, and defines how much space in the container it will proportionally take. For example: if, in a column, there are three elements with weight 1 3 and 5, it is calculated the total weight by summing them, that’s 9. This means that the first element take 1/9 of the available height, the second 3/9 and the last one 5/9. So bigger is the weight and bigger is the element. If on the same row there are more elements with different row weight the one with the bigger value take the precedence. Column Weight: defines the width of the current column. It works exactly like Row Weight. Fixed Size: defines if an element should have a fixed size defined by the user instead to be resized by the layout. If set to true, a layout resize will avoid the element and move the other elements accordingly. Also, the Weight for the elements are disabled, since width and height of this element became fixed. When elements use a fixed size, it is no longer assured that they will completely fit in the container. Spreadsheet Layout The spreadsheet layout creates a tabular structure using elements of different bands. Essentially it creates something that looks like a table but without actually being one. This avoids using subdatasets. The spreadsheet layout is unique because it can resize elements across all the containers and it can be set only on bands, other elements don’t support it. In this layout the elements cannot be moved and the height cannot be changed, but the width can be changed. Also it needs some configuration to work correctly and it has some constraints like: To create a column, it is necessary to exactly place an element in the first detail band. This element will act as pivot for the width of the column. The layout cannot be used on containers different from bands. Every column can have only an element for each band. Something similar to a span can be achieved by using a frame as an element of the column and place inside something else. Every band which contains an element of the column must use a spreadsheet layout, otherwise the element will be ignored. The advantages using this layout are: Changing a width of an element of the column will change the width of every other element in that column. It will be very easy to move and swap columns. It allow to have the convenient layout of a table without having its complexity. All the configuration is done through contextual actions on the elements. To use this layout, it first needs to be set on the detail band. Then, all the elements in the detail will fill the height of the band and will be placed one after another, keeping their original width. These elements must be connected to one or more elements of other bands to form columns. Select all the elements and, from the contextual menu, select the option “Add to Column”. This option is visible if every selected element is inside a container with a spreadsheet layout and if only elements for every band are selected. When an element is placed inside a column, it cannot be moved or resized except for the width, if the width is changed then the width of every element of the column is changed as well, like in a table. Instead, an element inside a container using the spreadsheet layout, but that is not part of a column, can be moved and resized like if the layout were a Free Layout. The only exception is for the elements inside the first detail band because they are implicitly part of a column. An element in a column can be removed from it simply with the contextual action “Remove from column”. The elements in the detail are always disposed in their creation order, the same visible in the outline, but changing the position of an element in the detail will allow to change the position of all its entire column.
  2. Hi, the customizer are embedded in JasperReports, if on studio they works and on the server not probably the JR version is too old an it doesn't support customizers.
  3. Hi, can you provide a sample project already configured where the error is easily reproducible? Thank you.
  4. Overview The composite elements are a new kind of user created element introduced in Jaspersoft® Studio with version 6.1.1. They allow to create a new element in the palette starting from one or more basic elements, and reuse them whenever you want in any report. For example it is possible to create a composite element using a static text and a text field with some attributes already predefined (like the fonts or the colors). You will have this new element in the palette and when you drag it in the report it will create the same Static Text and Text Field with the same set of properties of the originals. This composite elements are stored inside a special folder of your Workspace, so when you switch your version of Jaspersoft Studio you can always find your previously created elements as soon as you use the same Workspace. Create a Composite Element Creating a Composite Element is really simple. In any report create the elements you want to add to the Composite Element and customize their properties as you want, when you have finished, select these elements, right click on them and from the contextual menu select "Save as Composite Element..". NOTE: A composite element can be created only from a set of Basic Elements, basic means elements that are not depending from a dataset. When you click this option a Dialog will appear, in this dialog you will be able to specify: The name of your Composite Element, this information is mandatory since it will be used inside the palette and must be an unique name An optional description for the element An optional icon used in the palette for the Composite Element, if this field is leave blank then a default image is used. The palette section where this element will be placed After you have set all the information, press Finish. The element will now be created in the selected palette, NOTE: If you create the element inside a palette and in the next run it is missing, then this can happen maybe because you have created it with a Jaspersoft Studio Pro, placing them inside the Pro Components section of the palette, but you are reusing them into a Community version. The Community version does not have the Pro Components section. In this case and in every case where the palette of a Composite Element is missing, it will be displayed in the Composite Elements section of the palette. Use a Composite Element To use your element, you have to simply drag and drop it inside a report, it and all its contents will be created in the same way it was defined originally. Modify a Composite Element When you right click on a Composite Element you have 3 options: Edit: This option reopens the dialog used to Create the element and all information (name, description, icon and palette location) can be changed. Open in Designer: This option can be used to modify the content of the composite element, in other words you can modify the single elements inside it. When this option is selected a special editor will be opened where you can see all the contents of the element and you can modify it as you wish. This editor will look really similar to the report editor but with some simplifications: there will be only a band where the content is placed, there will be no dataset and no possibility to create one and the palette will allow to use only a set of basic elements. In this editor you can add new elements, remove the existing ones or change their properties. When you have finished simply save your work and the associated Composite Element will be reloaded automatically Delete: After confirming request this action will simply delete the Composite Element and all its resources Import/Export of the Composite Elements The composite elements can be exported and imported in any instance of Jaspersoft Studio. To Export a Composite Element: In the Palette, Right-Click on the the element you want to export and select "Export Composite Elements" A dialog will popup and here you can select any number of composite elements to export. The element that was selected in the palette will be already marked for the export. Every element selected in this page will be exported. Press "Finish" and select the destination, every element selected and their resources, like images, will be exported into a single Zip container. This container can then be used in the import procedure to get this elements back. To Import a Composite Element: Right-Click on any position in the Palette and select "Import Composite Elements". Select a Zip container obtained during the Export procedure. A wizard will popup where you can review every element that will be imported, you can define the name, the icon, the description and the palette position of every imported element. However all this fields will be precompiled with the information of the original exported elements, but you can re-define them during the import procedure. If one of the imported elements has the same name as one of the Composite Elements in your workspace, you will need to provide a new name for it, since the name must be unique. When you have reviewed all the elements, press Finish to complete the import procedure.
  5. OverviewWhen the elements in the report designer are dragged, the behavior of Jaspersoft Studio is similar to most graphical designers. When you drag an element inside a band, or a frame, you expect that the element will change its parent. This happens in most of the cases. But there are some special cases where this doesn't happen. In this tutorial we will examine some of these cases and also some keys that can change the default behavior. Elements from different containerWhen you select one or more elements from a container, you can move them with the default behavior. So, if the drop is done in the same container, then only the position changes, otherwise it will be changed also for the container. But if the selection contains elements from different containers, you can only change the position. So even if you drop the selection on a container, all the elements will keep their original parent and will only change their position relative to it. Elements contained inside frameThe behavior of the frame elements is similar to Subreports and, because of this, the size of a frame will not matter anymore on how its content is painted. For this reason the elements inside a frame can be placed outside it without causing errors. To support this, a modifier was added inside Jaspersoft Studio that acts when the dragged elements are contained in a frame. In this case, the dragged elements will never change parent, even if the selection contains elements that are all contained inside the frame. Since an element of the frame can be placed outside of its boundary, there is no way to know if the user wanted to drag an element outside of the frame and change containers or only move an element that is placed outside the boundary. We choose as default behavior that in this case the element doesn't change parent anymore. Override this behaviourThere are two way to override this behaviour and have the dragged elements moved inside the container where they are dropped. Keep pressed the A key while dragging: Keeping the A key pressed during the drag operation will always change the container of the selected elements to the container where they are dropped.Drag & Drop in the outline: these drag and drop modifiers are applied only on the visual editor, so every drag and drop operation done in the outline will always move the elements to the container where they are dropped. This is because, in the outline, it is easier to distinguish clearly what the user wants to do, since it doesn't allow editing the positions of the elements, we can determinate that each drag over a container wants to change the parent of the selection to that container.Other keyboard modifiersAnother useful keyboard modifier is the SHIFT key. When this button is kept pressed during the drag operation, it allows only straight vertical or horizontal movements of the selected elements. Also it allows only one of these directions, so you will be able to move your selection only straight horizontally if after you pressed the SHIFT key the first movement is on the horizontal axis, otherwise if is on the vertical axis only straight vertical movement of the selection are allowed. You can return to the default behavior simply by releasing the SHIFT key, also during the same drag operation. In the Outline, another useful key combination is ALT+SHIT. In a container, for instance Detail, selecting the first element and the last element while pressing this combination will select all the elements that are in the middle of the first and the last one.
  6. You must set the password property at report level and the locked property at element level. I've tested something like this and it works: <jasperReport xmlns="http://jasperreports.sourceforge.net/jasperreports" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jasperreports.sourceforge.net/jasperreports http://jasperreports.sourceforge.net/xsd/jasperreport.xsd" name="Blank_A4" pageWidth="595" pageHeight="842" columnWidth="555" leftMargin="20" rightMargin="20" topMargin="20" bottomMargin="20" uuid="3bff4add-3bc7-49b8-acd4-0ec822191576"><property name="com.jaspersoft.studio.data.defaultdataadapter" value="One Empty Record"/><property name="net.sf.jasperreports.export.xls.password" value="test_password"/><queryString><![CDATA[]]></queryString><background><band splitType="Stretch"/></background><title><band height="79" splitType="Stretch"><staticText><reportElement x="123" y="2" width="100" height="30" uuid="c9f7abf8-2ed4-44c3-abf5-84fda5d190f4"><property name="net.sf.jasperreports.export.xls.cell.locked" value="true"/></reportElement><text><![CDATA[static Text]]></text></staticText></band></title></jasperReport>
  7. OverviewSince April 2015, TIBCO Jaspersoft® Studio has provided a "Usage Manager" utility which, when installed and enabled, will help us gather anonymous statistics about how the application is being used. All the data is gathered anonymously and can, at any time, be disabled, if you wish. This data doesn't contains any sensitive information like passwords, usernames or URLs What will we use the data forWith this utility enabled, we can start seeing better how and where TIBCO Jaspersoft Studio is being used. We are especially interested in: which type of templates are the most usedhow many users integrate with TIBCO JasperReports® Serverwhich exporters are frequently usedThis will help guide decisions in the future, such as what resources to put towards which improvements. How to enable/disable the usage trackingOver time, we hope to learn more - to help continuously improve Jaspersoft® Studio. If you have done a new installation of Jaspersoft Studio, then on first start, a dialog will pop up asking you for permission to send anonymous usage statistics. If you do not want to send anonymous usage statistics, press No. If you press Yes, then usage statistics for Jaspersoft Studio is enabled. If you later decide to not send statistics, or want to enable it, simply goto the Preferences -> Jaspersoft Studio. How it worksWhen the user has enabled reporting anonymous statistics the number of time some functions are used is stored. The tracked functions are: Which types of data adapters are usedWhich types of reports are used (Normal, Interactive, Book, KPI)Which exporters are usedHow many connections to JasperReports Server were createdThis data contains information about the use of specific objects, but not their configuration information. For example, a statistic might record that a JDBC data adapter was created 5 times, but it will not contain any information about the data adaper itself. Users will not experience any significant impact on performance. The upload of the statistics is done through a dedicated eclipse job. We also generate a random id for the installation so multiple startups from the same eclipse only count as one usage. If you want to inspect the source code for all of the above it can be found here. If you have any problems to access to SVN server or checkout the code please check also this tutorial.
  8. The problem is that JasperReports can't the xml file since you are not providing the absolute path, you have two choices -The first one is to provide the context of the current report, in this way it will look inside the project folder of the report to search the resource when the path is relative, like this: new net.sf.jasperreports.engine.data.JRXmlDataSource((JasperReportsContext)$P{JASPER_REPORTS_CONTEXT}, "rmc.xml", "/mytexts/text") -Provide the absolute path for your jrxml, like this: new net.sf.jasperreports.engine.data.JRXmlDataSource( "C:/Users/Marco/workspace/MyReports/rmc.xml", "/mytexts/text")
  9. Can you provide the xml, the main report and the subreport so we can debug to find why beofre it worked and now not?
  10. OverviewWhen using a textual element inside Jaspersoft Studio, users can select the font used for it. Although this seems simple, there are a lot of problems when using the fonts. The main problem is that the available fonts are provided by the operating system and for this reason you can have: A font that it is available in one operating system isn't available in another. In this case, as fallback solution, the default font is used for the element. A font can be available in different operatiing systems but it could be slightly different from one to another. In many cases this is simply unacceptable. having a different font from the planned one probably will require more or less space for the text and this could have an impact, not only on the graphical appearance, but also on the layout of the report itself. To overcome this problem, the user can use external font files instead of the system provided fonts. In this way, the report will be independent of the operating system fonts and have the same appearance everywhere. This can be done using a Font Extension. The PDF ExporterThe font problem could be even more problematic when using the exporters - in particular, the PDF exporter. The PDF format has its own set of fonts. And, if a document needs to use other fonts, they must be embedded inside the PDF. In the first versions of JasperReports this problem was solved by introducing some properties on the textual elements to allow the specification of the PDF font name and encoding, and, if the font will be embedded or not inside the final PDF. This approach can still be used for backward compatibility, but it is now deprecated and discouraged. In fact, in the latest version of Jaspersoft Studio, a textual element that uses this property shows a warning icon and message. This is because the Font Extension handles the problem better. So, if a user wants to use a custom font in a PDF export, then it should done using a Font Extension. Download the FontFirst, you must have the font you want to use. Jaspersoft Studio allows you to use a wide variety of Font types like TTF, SVG, WOFF and EOT. One of the most used formats is the TTF and there are plenty of websites that collect fonts with various licenses. For this tutorial we will use this one, named Carnivalee Freakshow Font, you can find it also as an attachment to this page. Download it and save the TTF file. If you have downloaded it from the linked website you will need to extract the contents of the zip file. Create the Font ExtensionOpen Jaspersoft Studio, go to Window->Preferences From the new dialog, expand the category Jaspersoft Studio on the left, select Font, and then press Add At this point you must provide a unique name for the Font Extension and the path to its extension. In this tutorial we are using a TTF, so we will provide it using the True Type field. You can also specify a font variant for the Bold, Italic and Bold Italic styled text. If you don't provide this you will still able to use the font with one of those styles. The normal font will be manipulated to obtain the styled variant. But you can also provide a different Font for each of the variants. It is your choice. In this tutorial we will use only one Normal font. You can also specify if this font is replaced when exported in PDF. But we will leave this empty since we want to use this Font also inside the PDF export. For this reason we select "Embed this font in the PDF document" and a compatible encoding, like CP1252, since there are only european chars inside the Font. Note that embedding the Font in the PDF export will make the resulting PDF file bigger. Now click Next. In the following steps you can provide additional information for other exporters and restrict the use of this font only to a subset of Locales. We don't need this so just click "Finish" to close the dialog and "Ok" to close the preferences dialog. You can now open a report and, between the available Fonts you will find one named like your Font Extension, "MyCustomExtension" (If you can't see it try to close and reopen the report). Select it to see it used in the element. You can set the style to Bold, Italic and Bold Italic even if you didn't provide a specific font when you created the Font Extension. You can also preview and export the report as a PDF to see that your font is used correctly. An extension defined in this way will have a global scope and will be visible by every project in your workspace. Export the Font ExtensionOne of the problem that Font Extensions solves is to have the same font on every operative system so the appereance of the text will be the same. But using what is explained in this tutorial we should copy the TTF file on each system, and on each system recreate the Font Extension, with exactly the same name otherwise a report done in one will not find the font in the others. If we were using more TTF files for the text styles we should copy them also and configure more deeply the Extension. It's not hard, but it could take some time and repeating it many times could introduce errors, like a typo on the Extension name. To make this easier there is the possibility we can export our Font Extension as a JAR and use it in any project. First, open the Preferences dialog and go to the Fonts to see all your Font Extensions. Select the previously created extension "MyCustomExtension" and click "Export". At this point a save dialog will popup, define the name of the target file and save it. This JAR has all that is needed to use the extension on another system, you need only to share this single file to port your Font Extension to another machine. You can find the file generated in this way attached to this tutorial. Import the Font ExtensionNow you have your Font Extension. To use it, you must add it to the classpath of the project. For example, to add the Font Extension on the default project, MyReports, right click on it on the Project Explorer and select "Properties". On the dialog that will popup, select "Java Build Path" on the left, then switch on the tab "Libraries" on the right, and click "Add External JARs..." At this point, select your Font Extension JAR and hit Ok. Now, for each report contained in the MyReports project, you will see the font "MyCustomExtension". On some Jaspersoft Studio versions, the new font will not be visible on the reports that are currently opened in the editor. If this is the case, close the report and reopen it. Remember also that a Font Extension defined oin Jaspersoft Studio preferences is global. It can be seen by all the reports in the workspace. One defined using a JAR in the classpath of a project will be visible only by the reports inside the project. Publish the Font to the ServerOnce you have your font.jar file drop this into your application classpath (jasperserver-pro/WEB-INF/lib) and restart jasper reports server.
  11. This functionality is no longer applicable to our latest version. You can now set the compile with older JasperReports version in the properties of Studio or the Project. Please check the link here for documentation in the Jaspersoft Studio User Guide, Chapter: Properties and Configuration, Setting Compatibility with Earlier Versions of JasperReports Library OverviewJaspersoft Studio always uses and embedded version of JasperReports (tipically the one with the same version number of Studio) to build the report. Sometimes the user want to compile with an older version without used an older version of Jaspersoft Studio. This mostly because JasperReports dosen't provide an interface (graphical or from command line) to compile the report, so using it directly need some Java skills. For this reason was introduced inside Jaspersoft Studio a backward compatible compiler that can be used to compile a report with many JasperReports version and everything, from the download of the desired version of JasperReports to the use of it to compile, can be done trough a simple graphical interface. Download the desired version of JasperReportsThe first step to compile with an older version is download the files of that version. Jaspersoft Studio offer a simple interface to do this and to move the downloaded files in the right directory. First of all open the report you want to compile and expand the compile menu from the compile button on the editor. From the menu select "Manage JasperRepoers Version" A wizard will appear, showing all the JasperReports versions you can download and the ones you have already available. The version already on your disk will have a check mark on them, if this is the first time you use this feature then you shouldn't have any mark since there are no older version of JasperReports included in Studio by default. In this step when you check a version you don't have it will be downloaded from internet, so you will need an internet connection. The download can take some time depending on your connection speed, during the download will be shown the amount of data downloaded, cosnider that a JasperReports version has an average size of about 100MB. Always in this step when you uncheck something previously checked then it means you want to remove a JasperReports version from your system, so if you want to be able to use that version to compile you will need to redownload it. You can select or deselect any number of versions and the operation on them will be done sequentially For example select the version 4.7.0 and hit "Next". Now the download will start and you will not able to proceed with the wizard until it is finished. However you can abort the operation anytime, but in this case the files versions that was not completely downloaded will not be usable for the compilation. Once the operations are completed you will see a summary page where you have only to click "Finish". Compile with the downloaded version of JasperReportsAt this point you can compile your file, still expand the compile menu from the compile button and you will see a new option to compile the current file with all the downloaded versions. Select "Compile with JasperReports 4.7.0" The output of the compilation process is shown on a console view, it is also shown the command used to compile the report so the users can review advanced informations like the classpath. At this point you will find in the same location of the source file the jasper file generated with JasperReports 4.7.0. However maybe you don't want that a file generated with this version is placed inside the workspace among other japser files generated with different versions or also because you don't want it replaced by the automatic building. For this reason you can configure the output path. Form the compile menu go in the submenu "Backward Compatible Binary Destination". From here you can add a new absolute path on the filesystyem, select "Add destination path" to open the browse dialog and select the folder you want to use as output. The added folder will be used from now as default location, now every backward compilation will place the resulting file on the selected folder. You can access anytime to this menu and select one of the existing destination or add a new one. The menu will remember the last eight custom location allowing to switch between them easily, without need to select each time the target folder from the browser. Remember that the output folder is used only by the backward compatible JasperReports compiler, if you press directly the compile button will be used always the last version of JasperReports and the result of the compilation will be placed among the source, since it is a standard building. Delete the unnecessary JasperReports versionsYou can delete in any moment the old JasperReports versions you want to use. From the compile menu reopen the wizard trought "Manage JasperReports versions" like show in the first image. Now you will see already marked the version that are currently on your system. Unmark the ones you want to delete and press "Next" and they will be delete. Obviously since they are no more on your system you will not able to compile a report with that versions anymore, if you want to use on of it you must download it like you have done the first time. Advanced informationCompiling the file in this way is something external to the core of Jaspersoft Studio application. Jaspersoft Studio will internally use alway the last version of JasperReports and there is now way to switch it. For this reason the preview dialog will aways shown a report compiled with the last version and also all the other functions like the export and so on. This backward compatible compilation is provided with the purpose to allow to easly compilate the jrxml and use it outside Jaspersoft Studio, because many users want to use the last version of Jaspersoft Studio but still want a jasper file compiled with an older version of JasperReports because it is the one required from some third parties programs. Also for this reason the output of the compilation is shown in a separate console instead of the Report State view as usually. About the classpath used to compile the file, this procedure will try to use in the compilation proccess the same classpath that is defined on the project that contains the source file. The used classpath can be seen by the user when the backward compilation process is satarted. In the console will be paint the command used to compile the source file and in it there is written the used classpat, after the option "-cp".
  12. A good starting point can be create a new JSS plugin data adapter wizard. This was done to allow the users to easly port a JasperReport data adapter on JSS. This wizard will create many of the code that you need to plug your data adapter.
  13. Hi, this depends to which attributes you want to change. You can use an external style reference shared between the reports that you can change and the changes are inherited by the reports who use it. But the styles can not change attributes like size and position. For this ones you can use a Template Set (you can access it from the settings menu on the right-upper corner of the editor), that allow to define some attributes for the new elements and it allows also to provide a default size for each type of element. Also the template set are shared between the reprots but they are used only when an element is created and if you change something in the template set this is not applied also on the report created with it. However, if the attributes you want to change are supported by a style element then create an external style and use it as reference inside your reports.
  14. Hi, i've fixed some NPEs about the crosstab editor, now you can add column or row and undo without problem. If you get the errors during the run of the report it can be also JasperReports, or we allow to delete to much stuff. However if you send us the report that give the exception at runtime we will give a look to the exception. For the next time please use the answer question only for the answer request on how to use the product, for the bugs use the tracker (like you have done the previous times), because for us it easier to read them and keep track of them also. Thanks!
  15. I've just checked and this function was not implemented in JSS 5.5, it is available from JSS 5.6 . Actually JSS 5.6 is still in beta, if you want you can download the last public beta from http://sourceforge.net/projects/jasperstudio/files/beta-release/packages/ , but consider that it may contains many bugs.
×
×
  • Create New...