brcaswell

I received the following exception opening a target file I created... I created it with my program, and I'm attempting to determine why the out tga file isn't loading properly in Paint.Net. My program uses the TargaImage class from the following codeproject article: http://www.codeproject.com/Articles/31702/NET-Targa-Image-Reader It supposedly follows adhers to Truevision TGA Specification 2.0 After reviewing my own code that generates the targa file... I looked up '\src\pdn\paintdotnet\src\PaintDotNet\Data\TgaFileType.cs' and found this reference source file: https://code.google.com/p/openpdn/source/browse/src/Data/TgaFileType.cs but there is a discrepancy in the line number. I'm attaching a sample tga file. The issue seems to be with the imageType, but my code specifies it to be '2' in value. What does it look like under debug? Note that my code is uses TargaImage1.0 class (surprised that he updated his class recently, actually), and ultimately I wonder if bitmap image.... hmm Opps.. nevermind, just realized the issue is indeed with my code.. TargaImage.Image is a bitmap image, and thus.. that's what I'm saving with a tga extension.. ....... Thanks Windows Fax viewer for the false positive

hmm... yall are making me out to seem arguementative.. lol 'I suggest' as a title isn't a generic, unspecific title...though it maybe frequently used, it is certainly comprehensible to readers that the content of the post is going to BE suggestions by the author of the post (is deriving the author as 'I' the issue?). Would 'brcaswell suggests...' suffice? I guess I could specify the title more by labeling my suggestions in the topic head, but then what would the body of my post contain, 'refer to title'? haha my post was about my suggestions, and I was to list them in a single topic/post. I don't suppose you are suggesting that I seperate out each of my suggestions, by posting seperate topics with each topic containing my suggestion in title. That could be quite the spam fest. Again, although it may mean tedious changes, it really shouldn't be difficult to alter the saveas method to not change the values of the object, or structured object, that it will eventually write to file. Fair enough, if the developer doesn't want to pursue personalization of the application, or feature personalization in the app, that's understandable. However, irrelavent of the existing code or even language of Paint.Net (which i presume is a .net language anyway) , it is fundamentally simple to program and indeed implement my suggestion. It's beginner windows programming 101 stuff. Also, when I suggested the user mode login should be simple, and not actually referring to how complex it is to program it, I was actually refering to design. However, again, it's not complex to program it, unless the developer is writing his own language and compiler. In which case, It's still easy to implement, as one could 'simply' write the program in a common language and reference to the compiled app. As far as tech support, I couldn't see a user needing tech support to address issues with seeing a data view control that displays statisics. What would his question be? "How do I make the 'new projects started:' number increase?". I realize users can ask some pretty bonehead questions sometimes, but I would hardly anticipate a nightmare scenerio. I'm talking about a start page here, not a randomized dynamic property altering code segment, or some insane equivalent. The objective is to have, or at least attempt to have, both. Though, I fail to see where implementing a user mode complicates matters for the user, nor does the feature reflect, or affect, the power of the app. So, what do you mean by that? the 'overview' at http://www.getpaint.net/doc/latest/en/index.html suggested differently. By simplicity, you mean it's simplier for the user to download and run the Latest version of Paint.Net then go to your website's forum, read/search through each plugin published topic and (freely) download each plugin individually (or by collection, if the author puts them in a pack), and then extract them to Paint.Net's effects folder? As opposed to, distributing the plugins with the latest Paint.Net versions, after gaining distribution rights from the same plugin authors that are freely distributing them on your forums? Look, I can see a reason for not distributing the plugins with the program, as it creates traffic to the site, as well as protects the authors intellectual property to a degree, but simplicity? Furthmore, I weighed these reasons before making my suggestion. Anyhow, lets call this a hypothetical then, IF Paint.Net was going to actively gain distribution rights from plug authors, I would suggest the method I stated. A wishlist page, with a status report. You quoted me out of context a bit. What I said was in reference to zero plugins in the effects folder after downloading the latest Paint.Net. Still, I may be incorrect about 'attempts' to gain distribution rights, but it's still a little difficult to believe of the 100 or so plugins distributed freely on Paint.Net's forums, that these same authors would refuse all attempts by those associated with Paint.Net to gain a right to distribute the authors plugin. My conclusion was to consider the possibility that the decision maker(s) of paint.net did not want to gain the rights, or didn't consider it. So to correct myself, what I really meant was, 'They (which apparently is 1 man, the paint.net developer) isn't pursueing distribution rights of plug authors, because (aforementioned) there are no plugins being distributed in the 3rd version of the program.' FINALLY!.. haha (now I could be accused of pulling your comment of context) Again, I don't judge these things by trends. I know if I was the developer of the program, I would have a thread devoted to feedback of my program to me (or to those that have experience in developing application) that's seperate from troubleshooting. Infact, this is the first forum that didn't actively embrace, or prompt, feedback. On that note, how does the developer know whether their application is user friendly, if not from user feedback? You have a plugin feedback thread, though its intended purpose is to publish the plugins. As far as I've read, a lot of plugin authors enjoy and rely on that feedback to improve on their plugin. It's really quite essential to revisional programming, I'm suprised in the lack of promotion actually. I see, well, that serves to purpose. You wouldn't wager on such a guess would you? I'm betting it is actually because the developer is using byreference calls to his object (ie your image project) instead of byvalue calls, and has nothing to do with considering newbie mistakes. Though, If you're correct, then I suggest... -creating an options/preference submenuitem under the file menuitem and.. -creating a checkbox control to change a boolean value that will disable automatic flattening of your current active project when performing a saveas method. Other suggestions... -include a combobox that contain presets in the new document dialog for common sceeen resolution sizes, and other standards. ...btw, Rick.. what was your degree(s) in? And, are there any other projects you're working on right now? Also, for the forum, it keeps logging me out when I type out these thought provoking, and subsequently slow going posts.. what is the session cookie value set to, an hour?

No, it's not appropriate at all in the manner of classification. Topics posted in general discussion that are clearly oriented to the category 'Paint.net Programming / Development' is inappropriate, especially when the only thread visible to the average member is specifically restricted to discussions about plugin development. It sort of makes the whole category pointless, you might as well just create a Plugin category, and move the Development Central and Plublishing Only into it. Also, I'm quite new to this forum, and thus I haven't recorded, or have an estimate of, how many new feature topics that have been assessed by your 'unofficial 20' up till now, but rationally speaking, I'm a new member that has made three seperate suggestions in my first post, and I suspect, everyone in this forum has an opinion on what would improve paint.net, that isn't plugin effect related. no, the term refers to personal identification of the end-user to the application, it has nothing to with paint.net's effects. The implementation of a 'user mode' is the personalization of the application. It gives the user a reason to use Paint.Net over a duplicately 'capable' app, because they, the end-user, have invested themselves to the program, by creating their user name, or creating 'an identity' or 'persona'. I'm not sure why you persume this, I recently downloaded Paint.Net, and it comes quite bare in effects, and contains no 'plugin' effects. I'm quite certain no attempt has been made to gain distribution rights of plugin authors, so that the developers can distribute the authors plugins WITH Paint.Net, not implement the author's code as source into app. I'm not sure what you mean, you don't have the ability to add a new thread to the forum? create a webpage and links on the website? create a new win form for the app, then set it as the startup form and writing a few segments of code that read and write dataobjects between a dataset and xml file, or textfile? If you are infact, incapable of doing any of this, then this post was obviously not meant to be read by you. However, it's understandable that you may of thought it might have been, as I'm posting it in a general discussion thread. If only someone suggested a seperate thread, under an existing category perhaps, that one could post a topic that was understandably meant to be read by developers... More feature suggestions: - implement drag and drop layering - scrolling zoom - Improve the save as feature. Saving a multi-layered, non-PDN image file automatically flattens the project you're working on. theres no logical reason for this.

I suggest... -a non plug oriented developer central under Paint.Net Programming / Development in the forum, that centers around website & Forum, Paint.Net feature suggestions. -a simple login usermode (no password, cleartext storage) that will track intrguing usage statisics in an effort to personalize Paint.Net to the end user. -a 'plugin wishlist' page, on the website, that lists known Plugins that the Paint.Net team wishes to gain distribution rights from the author, to be distributed with latest release of Paint.Net App.