Jump to content

EricRS

Newbies
  • Posts

    6
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Netherlands

Recent Profile Visitors

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

EricRS's Achievements

Rookie

Rookie (2/14)

  • First Post
  • Week One Done
  • One Month Later
  • Conversation Starter

Recent Badges

0

Reputation

  1. Thanks! Changing to fixed helped. When calling Resize, the pop-up window states: 96 DPI vs 300 DPI for the two images in question. Is there a way to view the DPI value of an image, e.g. at the bottum of the screen where other properties are being displayed?
  2. I have two .pdn files (multi-layered) approximately the same size (240 * 400 vs. 240 * 376). When trying to insert in either file characters of the same size, I get a notable difference in size as the characters appear on screen in one file compared to the other one. In both images characters are 8 pt in size, same font (both bold), while the difference in appearance is about a factor 2. How do I get the same selected size characters to appear the same size in my images in those two separate files? (I need to add those two to a master image, each in a separate layer; that's is the reason I want those characters to have the same size.)
  3. Thanks for these tips Rick; and thanks for developing paint.net. I was already aware of the windows quick access option. My right-click explorations had not reached the Copy Path and other options, so that is new and very welcome. Purely for the awareness of the path for the file under edit, I think I prefer the Ctrl + Shift + S shortcut and then subsequently abandoning it.
  4. Thanks for the quick response; and the amended one! Let me try to compare; as suggested we have: Ctrl + Shift + C (copy Merged) Ctrl + Shift + V (Paste into new image) Ctrl + S (Save = Save As... because this new file will have no existant source file). Close new file or return to your original PDN file to continue editing. My sequence (file under edit already saved as t1.pdn-and thereby t1.pdn file name added to the recently used list): Ctrl + Shift + S (Save As...) (e.g. as t1.png) Ctrl + W (Close) [Note: no confirmation needed because "just saved") Alt + F (open file menu) 3 * arrow down (higlighting Open Recent) arrow right (highlighting top entry in recently used list; i.e. t1.png) arrow down (higlighting the desired entry; i.e. t1.pdn) ENTER/RETURN ( again opening t1.pdn) 4 thru 7 can of course also be established by mouse actions; as can all the mentioned actions. My request: [selected schort cut key sequence] (Save Copy As...)* So, in conclusion: your suggestions are (definitely) an improvement! These observations also lead me to amend my request with specifics about when file names are added to the recently used list. I stil like my (amended) request to be considered. This is also related to my newly entered topic about the implementation behaviour of the recently used list; see my inquiry here. ___ * probably preferably not entered in the recently used list
  5. I recently added a feature request here, which is somewhat related. This is fairly long, sorry for that. I noticed that saving a file under edit for the first time will add that file name to the recently used list immediately (the file still being open). I'm undetermined yet as to that this addition is the "best" or "most desired" behaviour. Another implementation behaviour would be to only add the file name to the recently used list when that file is no longer in the list of open files (being in the list of open files to be considered distinct from the file under edit; I'll elaborate on that). I noticed that after saving the current file under edit (i.e. has focus) and then opening that same file by selecting it from the recently used list it _will_ be opened as a new instance. That means that there are two instances in the list of open files with the exact same file name. Not only that but these two instance with the same file name in the list of open files, one of which has focus (i.e. is under edit) and the other one does not refer to the same OS file on disk. Making edits in one instance will be effectuated only in that instance; not in the other one. The Save command saves the instance under edit with those (before unsaved) edits and will update the OS file instance in the file system on disk. The most obvious problem here is the undesired "competition" between the two files (withe the same name) in the open files list. "open" in the sense that they are open in the list displayed by paint.net as seen by the user. Both instances open in paint.net refer to the exact same (OS) file instance on disk. I think this is undesirable behaviour. In addition you have, after the described save action (of edits) to disk: The instance that was just saved to disk, accurately displays its status by not displaying the * (i.e. not displaying the: edits-not-saved-to-disk; hereafter labelled as *-display). The other instance also displays its status by not displaying the *-display. It can be argued that both are correct with respect to the (at one time) saved edits as seen from Paint.NET. They are, however, _not both_ correct with respect to their *-display as an accurately representation of the saved edits of the OS file instance on disk. Q: Can you confirm this behaviour and is it intended as such? I've noticed that it doesn't seem possible to open a separate running instance of paint.net. (i.e. having a another separate instance of paint.net in memory). My idea/suggestion would be something along these lines: Only add a filename to the recently used list when it is no longer in the list of open files in paint.net. When opening a file from outside paint.net from the OS explorer, check if this file is already open in paint.net. If so, only direct focus to that open file instance. If not, open the file from disk (and let it acquire focus). When opening a file from within paint.net (with the open command), check if this file is already open in paint.net. If so direct focus to that open file instance. If not, open the file from disk (and let it acquire focus). My observation is that currently all actions mentioned under 1 thru 3 will result in a two instances situation in the open file list in paint.net _both_ referring to the same (OS) file in the file system and thus both affecting that disk file. This can occur in practice when having open a lot of files in paint.net. Having forgotten that a particular file X is already open and then opening it from the recently used list will create this situation. The implementation of my suggestion of ad point 1 will require some additional manipulation of the recently used list. For instance: closing file X results in addition of its name to the list. After that, opening file X results in (a temporary) deletion from the list or (temporary) obscuring from being visible by the user (numbering has to be adjusted accordingly). This will also bring about nifty details about the exact meaning of "recently used": When "recently used" is interpreted as just having the Save command executed upon, the (saved) file name is added to the recently used list. When "recently used" is interpreted as just having the Save As... command executed upon, the (saved) file name is added to the recently used list. When "recently used" is interpreted as opened in paint.net (but _not_ having acquired any edits), the file name is added to the recently used list. In situation 1 thru 3 the file name is currently added to the recently used list immediately at position # 1 when opened. If my suggestions are being considered then that behaviour at the opening of a file will probably change. No 3 might be eligible to change if my suggestions are being considered. My feature request, mentioned at the opening of this post, regarding the addition of a "Save a Copy As..." command might result in no (updated or new) addition to the recently used list. Eric
  6. I'd like to make two feature requests that are slightly related. Strictly speaking, they are probably a nice to have but these would be useful to my workflow. Working on a .pdn file as an original I use various derivatives in creating intermediary files and final output files. Such intermediaries/derivatives are for example a smaller resolution of the original file and a final output file in .png or .jpg format used for “release”. Saving a file in a different file format changes the current file name being edited; unsurprisingly of course, but discarding the changed file under edit and returning to the original .pdn file takes a little extra work (as a side effect the changed filename is added to the recently used list). I usually use separate directories for this. I also use separate directories as a differentiator for files with the same file name and as a result I cannot see from the name displayed after the paint.net icon which file I am editing. Therefore I’d like to request: (possibly optional setting) which displays the filename prepended by its complete pathname. It would then be appropriate that full names be displayed in the recently used list as well. Add “Save a copy As” as a command option to the File menu to save under a different name or format; after execution returning to the original (.pdn) file. Eric Update 27/12: Based on the first two responses below and my rethinking, I'd like to amend my requests and extend No. 2 with 2.b. My two requests are now as follows: (possibly optional setting) which displays the filename prepended by its complete pathname*. It would then be appropriate that full names be displayed in the recently used list as well. a. Add “Save a copy As” as a command option to the File menu to save under a different name or format; after execution returning to the original (.pdn) file. b. Do not add the file name used in the "Save a copy As" command to the recently used list. ___ * I didn't see this at first but I've come to the realisation that this will probably require some "real estate restructuring" at the top with respect to the area for the filename.
×
×
  • Create New...