Jump to content

Peter1

Members
  • Posts

    70
  • Joined

  • Last visited

Posts posted by Peter1

  1. It is just a little nuisance. When I toggle the visibilty of a layer, the rotation center gets reset to the center of the selection, instead of remaining at the place where I did put it.

     

    The use case is that I want to match two layers, and image and a base map, zooming and rotating, and to judge the match, I toggle the top layer on and off. To make the post colorful, I show a screen shot of the work in progress (the yellow part is image, the orange part is void and transparent, the brown is map).

    Version is paint.net 5.0.10.8674.32967 ( I do not assume 5.0.11 would have changed exactly this).

    Thanks.

     

    colorfulworkinprogressScreenshot20231021042402.thumb.jpg.b3e230bdf4a1ee880d40a22ba94e3bc4.jpg

  2.  

    On 6/11/2023 at 8:35 AM, Rick Brewster said:

    This has been the behavior since ... version 1.0 probably?

     

    Thank you for explaining the situation and I'm sorry not reading your answer earlier. I didn'nt notice that it concerns the ctrl-B behaviour. My screen is just 15,6 inch and palettes overlap the image on opening, or ctrl-B.

     

    I consider this: Zooming is allowed in the ctrl-B situation.  if panning is inhibited for a reason (which ones?), zooming should be inhibited also, until ctrl-B is released. (Currently panning-after-zoom is allowed, but the inverse, zoom-after-panning is inhibited in the ctrl-B situation. Yet, zoom-after-panning seems more natural to go to the initial, or next, work area on the image.) Is somebody depending on this ctrl-B-panning behaviour? Why not keep panning anyway unlocked after a ctrl-B, or after clicking the icon in the zoom controls at lower right (between % and ruler)?

     

    (version still 5.0.6)

    Thanks

    Peter.

     

     

  3. Hi

     

    When I open a .pdn, and select the Pan tool (hand, or it is preselected from settings), I get the hand with an X and can't move the canvas. Zooming however works. But as soon as I do a zoom and back (=no-op), I can move the canvas. Why would I want to move the canvas first, before doing anything else? For example to center to the part of the canvas where I want to work (and before zooming), or to avoid palettes. That has been in all versions of paint.net >=4.x, since I know paint.net, including the current 5.0.6 (Installer, not Microsoft Store).

     

    Thanks.

    Peter.

     

    (And I'd like to remember the run-away behaviour of the drawing and selection tools when dragging the mouse near the window border, but still inside it, which makes precision work sometimes surprising).

  4. 56 minutes ago, LilChad said:

    I was able to restore the drawing from the screenshot that I sent to discord. Thanks to everyone who tried to help me.

     

    Glad that you found a copy of the drawing (as help was impossible from the zip).

     

    analytical followup steps:

    Nevertheless I suggest that you do a drawing again of the same size and probably two layers (not hours of course, but seconds...) and do the SAME saving again, as you remember you did, to find out what went wrong, or what did interact with the saving process in such a way that paint.NET was not able to write the contents.

    PS both the screenshot you mention, and the contents of the zip do have timestamps, date-created and date-modified (contents of the zip are dated 2022-05-09 10:50h). Which one was earlier?

    PS With Search in Explorer for *.pdn, do you find another place where paint.NET did store something?

    PS how did you create the zip? not with the zip-plugin from paint.NET?

  5. 15 hours ago, LilChad said:

    how can I save it again if I have lost access to it?

     

    Remember what you did before you saved the image.

     

    I suggest you do the drawing again (if it has been your own drawing), as it was not large, or access the source again (if it was not your drawing originally) and do your modifications again, or if it is a plain not-your "image", get it again and compare. 

     

    Perhaps something did not agree with the non-english letters in the file name.

     

    The file you posted here is essentially just empty, instead of image data it contains all binary zeroes and without information about the "image" type.

  6. I' like to ask what interpolation is used, in the Levels adjustment, between the "white" and the "gray" output point, and the "gray" and the "black" output point? Is it linear interpolation or a curvy,  smooth interpolation like in the Curves adjustment? ( the question is also inspired by the Curves+ adjustment, where there is choice?)

    Thanks

     

    the question is related to the recent discussion here:

     

  7. generic troubleshooting would include (and skipping those steps that you do not understand):

    - get the latest official version from getpaint.net

    - try Repair from Control Panels-Programs and Features.

    - try the portable version

    - try the 32bit-version instead of the 64-bit version, and reverse

    (these downloads here: https://github.com/paintdotnet/release/releases)

    - try an older version if you find one or did keep one

    - clean the registry, that is the appropriate keys, with regedit (that  is, rename the appropriate keys named paint.NET to paint.NETx)

    - clean AppData and ProgramData (that is, rename the appropriate folders named paint.NET to paint.NETx)

    - remove plugins

    - disable your antivirus program temporarely.

     

    it is probably faster, than analyzing the specific stack trace. Defragmenting the disk is surely not related.

     

    - The message in Swedish, Filen eller katalogen är skadad och kan inte läsas reads:

    Quote

    The file or directory is corrupt and cannot be read

    Therefore checking the disk from Explorer - click disk - Properties - Tools would be helpful (I don't know how properly in english).

  8. On 5/8/2022 at 6:09 AM, Rick Brewster said:

    Yeah I'm not convinced this is a bug. Could be possible to improve how this is communicated in the UI, but I think it's working as intended.

     

    double-clicking would allow to set the "gray" point in all three color components RGB individually at once, as can be done with the "white" and the "black" points. I agree that it is difficult, because "gray" has to be restricted into a cube between the "white" and the "black" color points, and I have to go to "define colors" to see the current point and change it.

     

    Whether setting gray in all color components is useful, remains a question, but I did have a use case with my blueish take.

     

    supplemental question: what happens between the "white" and the "gray" output point, and the "gray" and the "black" output point? Is it linear interpolation or a curvy interpolation?

  9. The gray point swatch in the Levels UI cannot be double-clicked, but according to the documentation it should be possible.

     

    I don't yet know whether it would be helpful, but it  seemed an easy way to adjust all three color grays individually at the same time. PS: Levels Auto command was very useful to get an initial guess for my de-haze task.

     

    Quoted from the documentation:

    On the right-hand side, three color swatches appear: one each for the output white and black points and another for the output grey point.

    These colors can be adjusted using the numeric inputs, the slider, or by double-clicking on the color swatch itself.

     

  10. On 5/5/2022 at 2:26 AM, Ego Eram Reputo said:

    If you show us the picture (remember: it's a family friendly forum) some clever person might be able to suggest techniques to improve the image.

     

    I believe I found a good solution. The original is the blue image, taken in the year 1982. The second is a intermediary one I don't recall how I did it, but serving as base for seven variants, the third is the mix of these variants and is good enough, providing depth and color. The artifacts in the sky are from the Sharpen operations.

     

    Actually I tried many variants in paint.net using Levels, Auto-Level, Curves+ and Sharpen, and mixed seven promising versions with equal weights 1/7 (opacities 1/7 1/6 1/5 1/4 1/3 1/2 1).

     

    I'm curious what an experienced user will result.

     

    218307204_ausschnittfrForumoriginal.jpg.5b12a2e5cb5eccfcda5a07807101252a.jpg

    1150206773_ausschnittfrForumcolorized.jpg.e96afe977cbc2f64a689f5f75e8ff79e.jpg

    899653977_ausschnittfrForumfinal.jpg.1562cdd2a0a8a93fe1b8400e0d108332.jpg

     

     

  11.  I do have to unfog/unmist a picture C,  somehow, to get more of its content. (1) and (2) which follow are circumscriptions of it, or attempts at it.

     

    (1) Where are the blend modes explained? e.g. as formulas like this one (Ego Eram Reputo, Mai 12, 2021, topic/118210-question-about-blend-modes, comment=583366 )

     

    Quote

     

    Color Burn increases the contrast in proportion to the color of the lower layer.

    image.png

     

     

    I followed the advice in the help documentation to search the forum for "blend modes", but the search returned "126 pages", where I'm lost.

     

    (2) Actually I would need I think, a convex mixing of two layers, to simulate fog/mist,

    which is C = a*A + (1-a)*B, where: a in the range 0..1, A the picture, B a fog simulation, C the "fogged" picture.

     

    and its inverse to unfog/unmist,

    which I would try as A=1/a*C + (1-1/a)*B,  where: 1/a is obviously greater than 1.

     

    Thanks.

     

     

     

  12. On 2/21/2022 at 3:37 AM, Rick Brewster said:

    I already explained that it’s working as intended. I never said anything about changing it for 4.3.8

    Yes agreed, you did explain the intentions. I pointed out that there are TWO mouse positions that could be considered. The one in the zoomed-in view, and the one in the zoomed-to-window view. They have the same mouse coordinates relative to the window, but one of the two is just plain hazard, as long as the mouse is not "intentionally" moved to a new point of interest mostly in the zoomed-to-window view. The hazard half would lead to a lose of the work focus, or point of interest.

  13. On 2/16/2022 at 11:31 PM, Rick Brewster said:

    I agree that Ctrl+, is clumsy when used alongside Alt+PgUp/PgDown, but there aren't really a lot of good choices for keyboard shortcuts since they're pretty fully allocated at this point.

    I vote (as of tonight, very early morning) for ctrl+click to toggle the visibility. This is near to click to change the layer, and does not require a very precise hitting the visibility checkbox.

  14. "autoscrolling out of the window makes huge selections or moves"

    This behaviour is unchanged in Paint.Net version 4.3.8.

     

    On 2/15/2022 at 12:55 PM, Peter1 said:

    Please makes this an issue for an upcoming version. For me as new to Paint.NET, and old to programming, it looks like a sign error on checking the distance from the mouse position to the visible area border, (TRLB or 00WH comparisons with mouse position or (mouse offset from TL)). The absolute value of the distance checked seems right. And please control the scroll speed if it is not already controlled but missed because of the "second phrase" of this post.

     

    In addition I noticed that it is not entirely clear where is the hot spot in the Hand cursor. The run-away occurs always, but depending on whether I grap the nub with the finger tip, the palm, or the lowest part of the hand (dont know how in english, "Handgelenk"), it occurs a few pixel nearer or more distant from the window border, but always inside of the window.

  15. On 2/18/2022 at 4:46 PM, Rick Brewster said:

    simple_line_tool.png.854c5b6112a912841a6e104620820f35.png

     

    This is pretty much what I'd do. I originally planned to have this in the 4.0 release but just ran out of time/energy (it was already a 5 year project). The complexity, iirc, came when you switched between the line vs. curve formats. Where do the nubs go when switching to a curve, modifying the handles, then back to line, modifying it, then back to curve?

     

    The middle nubs go to the straight line and stay there at the thirds, and remain internally moved at the thirds, when switching to the straight line, and go grey, or disappear. When switching from a straight line to a curve, the middle nubs stay, go black, become freely movable, or appear at the thirds. When Undoing in the history, it is Undo. Internal Disappear and Appear is less preferable (not really an option), from a programmers point of view, than internally fixed, versus free move. Visible Disappear and Appear is an option, of course, instead of going grey.

     

    When just one single middle Nub is clicked (perhaps dragged) with some Modifier key (shift), it goes back to the straight line between the two end points (to fix a misplaced middle nub to a well known place). The end points do stay anyway, don't they? When an end point is dragged with a modifier key (shift), the aligment concerns the end points, this endpoint related to the other. It is interface handling (except fixing middle nubs at the thirds, this is new), and not drawing algorithm. Would that sound sane?

     

    When we are in the rotate zone (or right drag to rotate), it is rotate. The rotate anchor is initially in the middle. (the rotate anchor is new, as the rotate zone). There could even be a selection rectangle around the Line/Curve while it is in the drawing layer. (Or a modifier for proportional stretching.) That would be new too, but not completely.

  16. On 6/4/2012 at 6:00 PM, Red ochre said:

    Hi Rick,

    Yes you can - I think it's easier to just click on one icon and have the selection clear rather than expanding the color window, then changing the primary color - then changing it back again - I did say I would probably be the only person using it!

     

    wrong thread

     

  17. 1 hour ago, Rick Brewster said:

    Alt+End should probably be reserved for another keyboard shortcut that needs to move or navigate to the end of something.

    not really, because go to the first or last layer is handled by ctrl+alt+PgUp/PgDn and not  by alt+Home or Alt+End (consistently). Two of the Alt+xxx are already committed to the Layers windows.

     

    how about alt+num keypad -? or what would please you, near ALT+pgup/pgdn

     

    (+)something different yet, something new, I get a lot of Move Pixels in the history; I can't even say when a new line gets added. Could they be numbered? That is the whole history numbered such that it is also possible to reference (taking note for example) a certain state.

    (I do have to align 2 images and judge it, it is not clear what is best, and it is contradictory, it would really be useful to be able to distinguish them)

×
×
  • Create New...