Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In tgt.c we used fprintf not the openjpeg message reporter #184

Closed
gcode-importer opened this issue Oct 25, 2012 · 3 comments
Closed

In tgt.c we used fprintf not the openjpeg message reporter #184

gcode-importer opened this issue Oct 25, 2012 · 3 comments

Comments

@gcode-importer
Copy link

Originally reported on Google Code with ID 184

In tgt functions the message manager is not available so some messages are not correctly
return to the user. 
It is very complicated to pass this manager to these functions, so for the moment we
use fprintf.
Moreover we need some documentations about the case where we used fprintf to return
warnings. 

Reported by savmickael on 2012-10-25 09:13:07

@gcode-importer
Copy link
Author

Hi, 

With SVN revision 2343, the trunk still use fprintf messages (e.g. inside image.c,
openjpeg.c, tgt.c). 
This is very problematic (better print nothing and return an error). 
There are also many fprintf calls that are commented => should be deleted. 

Please add this correction on top of the priority list. 

Hervé Drolon

Reported by FreeImage on 2013-05-08 18:31:15

@gcode-importer
Copy link
Author

Closing current issue 184, please follow issue 246 instead

Reported by malaterre on 2014-02-25 15:46:42

  • Status changed: WontFix
  • Labels added: Milestone-Release2.1

@gcode-importer
Copy link
Author

Reported by malaterre on 2014-03-07 15:14:22

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants