mvcoile

Changed Assigned User from - to @mrabbi It is more than common when you supply a link (from dropbox, google drive or CloudApp) that these files are redirected to an other storage location, like amazon aws or cloudfront. Or, more specifically, our own redirect to a more secure https when a http is supplied.IMPORTANT: Whether or not you decide to support redirects, it should not cause the report to crash/error!!Kind regards,Maarten @ Yesplan

Changed Severity from Critical to Minor Changed Status from New to Acknowledged Changed Assigned User from - to @narcism I did. It's the first thing I said: A text field with value "&" and markup "styled". That's all you need to create the error. "&"

Hi! Working around it is not an issue. The use case is usually testing or leaving a placeholder (todo) message like /* INVOICE NUMBER HERE */. Or when I have an expression that's quite complicated and is not functioning or causing to much overhead while testing. I may want to quickly turn off an expresion using this method. I don't actually want to throw away the content of the expression. /* ... */ comments are valid Java. But I see what you mean now. You could see it like this: leaving an expression empty is also not valid Java expression! ;-) Would it be possible to treat an expression with only a comment like an empty one? Kind regards, Maarten @ Yesplan

Very nice, thanks!

Changed Priority from High to Normal Changed Status from Closed to Feedback Requested Give me some time and I'll post an example.This is getting really annoying to work with. Might be related to an eclipse bug I've seen earlier that is only in effect on Mac. I'll try and update this next week.

Changed Priority from High to Normal Changed Reproducibility from N/A to Always System Message

Changed Assigned User from - to @User_306070 Proof of concept: I forcibly feed JR a Java.awt.Image with a transparency layer thus forcing your renderer to to PNG. The resulting image shows no sign of jpeg-style compression artefacts.

Massimo, thx for the new build! (I should really start learning how to make my own) Chicuslavic, The parameters seem to load even faster then before 6.x! So that's good. However, Our Custom Provider plugin fetches some information from the "description" field of the parameters. In this new build I notice that when I change the description, JSS only compiles the report and prints the static part of the report. Our Custom Provider does it's own logging into the JSS Console, but that stays empty. Pressing "Preview" a couple of times does, eventually, starts a real preview. Kind regards, Maarten @ Yesplan

2 tests I did not see you perform: Going back to the designer, testing with a custom provider class. If there is a community build soon, I can do a test with my provider plugin and files. (Sorry, if I seem to be acting difficult, this is not my intend)

Changed Resolution from Fixed to Reopened Sorry to reopen, however I noticed there are 3 different bugs going on:- Bug introduced in the 6.x series where the default parameter value is refuses to load when you go to the preview screen.- Bug introduced in the 6.x series where the parameter value is reset to the default parameter value when you press the green "play" button to preview.- Bug that already existed in 5.6.x (and probably earlier) where the preview always stopped on boolean values. Boolean parameter values always have to be reloaded at every preview. Not only on first run. Combined with the 6.x bugs, this causes the preview to not function at all.Did you solve all 3?Kind regards,Maarten @ Yesplan

Thank you! Ps. Since you're from Belgium you can, if you prefer, speak dutch also.

I can't. JSS is unusable until #4106 and #4104 are resolved.

JSS 6.1.0.SNAPSHOT.beta.v201502261347 now always resets parameters when you pres run: http://cl.ly/ZyOh

This can be done in the Preferences, select Jaspersoft Studio. You'll see "Version". There you can set what version your jrxml should be complient to.

Carefull. Although you can set the compatibility of the .jrxml file, the generated .jasper file is not! A jasper file generated on JSS 6.0.3 will/may have serious style issues when used on an older library like 4.5.1. My advice: Don't use JasperStudio 6.0.3. If you must/want, you better use iReport 4.5.1 to build the .jasper files.