Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by odalet

  1. I noticed that too. See topic #12 (http://forums.getpaint.net/index.php?/topic/27227-paintnet-40-alpha-build-5034/#entry398549).
  2. You're right: Google confirms, but hey, what I said was not wrong strictly speaking
  3. I've found another weird behavior: the new "help" menu does not react like a regular menu. Steps to reproduce: - click the "?" menu - move your mouse to the left - the dropdown menu disappears (which it should not) - then, without clicking anywhere, move the mouse back to the right so that it hovers the "?" - the dropdown menu appears again... To summarize, it appears one has to be very careful not exiting the "?" area once he has clicked and go right to the dropdown otherwise it disappears. By comparison, the Effects menu - which is a regular menu - behaves normally: when going too far to the right after the click, the dropdown remains opened and you can go back to it and click a menu entry. Hope this helps.
  4. Just a last note to say thanks: I've just witnessed that my WSQ filter plugin worked seamlessly with Pdn4
  5. Here is another tiny bug related to translations: - Just installed PDN4 on a French Windows7 box (btw, the installer was set by default in English) - First run: the UI is in French, but if I go to Settings > Language, English appears selected in the combo. - I change to french. Pdn restarts, the UI is in french and french appears as the selected language. - Then I can change back to English (because I always prefered using Pdn in English) in the Language combo, restart and this time, the UI appears in English. There must be some initialization check failing right after installation, Pdn thinks it is running in English, but instead it uses CurrentCulture/CurrentUICulture... I don't know where you store the user's settings (seems you don't use app.config user settings), but I suspect the rules you use to determine the current language are not consistent throughout the application when no culture is specified in the config. And another little disprecancy: during the setup phase, I checked "also check for pre-release", but when in Settings > Updates, the equivalent check box was not checked.
  6. Yep, something like that
  7. Hi, @null54, I was wondering, could this plugin support resolution information in the JP2 headers? I know this is optional, and libs such as openjpeg (or FreeImage which embeds it) do not support this yet.Though, you seem to use the jasper implementation; I've downloaded v1.900.1 source code, and it seems to support resolution information (through the JP2_BOX_RESC and JP2_BOX_RESD boxes defined in jp2_cod.h). Or, is there a possibility you publish your plugin's source code? Regards, Olivier
  8. Thanks, and yes you're right, there are 4 DLLs, and indeed, the simplest way to install it is to copy all the 4 DLLs to the FileTypes directory (regardless of the machine bitness, for Delta.Wsq.dll selects at runtime what native implementation to use based on the machine's bitness). By the way, the image is also free of rights as it was captured from my own left index (ain't it handsome!) PS: it's Olivier, not Oliver, but you're forgiven (I know how hard it is for English speakers to say it...)
  9. Hi all, For anyone interested in editing fingerprint images, I've crafted a WSQ File Format (http://en.wikipedia.org/wiki/Wavelet_Scalar_Quantization) plugin for Paint.NET; This plugin is based on original code provided by the NIST (http://www.nist.gov/itl/iad/ig/nbis.cfm). It should work on x86 and x64 machines, given you install the Visual C++ 2010 SP1 runtime: x86 runtime: http://www.microsoft.com/en-gb/download/details.aspx?id=8328 x64 runtime: http://www.microsoft.com/en-us/download/details.aspx?id=14632 You'll also need at least .NET 3.5 Client profile as well (which by the way should already be installed if you use Paint.NET). The plugin is attached to this post (as well as a sample fingerprint image). As usual, to install the plugin, simply copy the three DLL in the attached zip to your C:\Program Files\Paint.NET\FileTypes\ directory. Source code is available at github: https://github.com/odalet/Delta/tree/master/Delta.Wsq There is room for improvements (support for embedded comments, specification of bitrate alongside of "quality"...) but though it's usable (I do). Regards, Olivier -- Works on my machine... wsq.zip
  10. Thanks, and sorry for duplicating questions, and not searching first. I just wanted to say that I used to download source code because I like literature, good books, fascinating novels... And PDN source code can be read exactly as a good book: suspense (how did he manage to do this...? goto definition...), style, hidden gems in some paragraphs, overall construction... If anybody knows Scott Hanselman's computer zen blog, then she knows this man writes regularly a series of posts named "The weekly source code" under labeled an "ongoing quest to read source code to be a better developer". This is exactly what I have in mind when I grab PDN source code. About people stealing code, unless Rick obfuscates PDN, there will be nothing preventing people from reflectoring his code (at least the managed parts)... This will certainly be less readable, but I don't think such people care about style and beauty... So, I'll end with a great thanks to Rick for having provided us during such a long time with such material to read (and I'll go right now backuping my latest source download). PS: by the way, Scott has had a discussion with Rick available here: Hanselminutes Podcast 138 - Paint.NET with Rick Brewster.
  11. And in longer? Why is it so? PS: don't see any form of attack behind this question, I was really happy to be able to have some insight about how PDN was made. If you decided not to release the source code anymore, ... well it's a shame to me, but it's definitely strictly your right, and I thank you to have done this before.
  12. Hi, I was quite surprised not to find the link to this new version's source code. Was it intentional?
  13. I've just downloaded your plugins: in fact I was more interested in your source code than in the effects themselves. And woh! I particularly appreciate the clever (or smart as you tend to prefer this word) use you make of delegates and lambda expressions, especially the definition of a Layer which is just beautiful!
  • Create New...