Skip to main content

Timeline for pset4 resize: how to copy a row

Current License: CC BY-SA 3.0

13 events
when toggle format what by license comment
Aug 14, 2016 at 12:30 vote accept Semyon Pilyukov
Aug 12, 2016 at 20:49 comment added covrebo Trying to address a similar issue with my code. I see where you create the temporary line storage in 'outrow' and where you try to use it for the vertical enlargement, but where are you putting the pixel data into the elements of 'outrow' so that it can be used to write n-1 additional lines?
Aug 12, 2016 at 14:29 history edited Semyon Pilyukov CC BY-SA 3.0
edited body
Aug 12, 2016 at 13:59 history edited Semyon Pilyukov CC BY-SA 3.0
added 4752 characters in body
Aug 12, 2016 at 13:38 comment added Semyon Pilyukov oki doki, I'll give all code and additional info, thanks!
Aug 12, 2016 at 6:26 history edited ChrisG CC BY-SA 3.0
added 181 characters in body
Aug 12, 2016 at 6:25 comment added ChrisG From what I can see, the first time your loop runs, you have not written any pixel lines to your output file, but you fseek() backwards to it. Post the full code so we can debug your program. We can't guess all the missing lines. Please read How to create a Minimal, Complete, and Verifiable example
Aug 11, 2016 at 20:31 answer added Cliff B timeline score: 1
Aug 11, 2016 at 15:03 comment added Semyon Pilyukov Good idea, that is nice design improvement. I'll try after program will work correctly. Afraid that reading whole row including padding may be a problem: pixels are RGBTRIPLE type, then padding is raw bites. But will see.
Aug 11, 2016 at 14:54 comment added Blauelf Shouldn't you use the input row size when reading? You then have to repeat individual pixels.
Aug 11, 2016 at 14:00 history edited Semyon Pilyukov
edited tags
Aug 11, 2016 at 13:50 review First posts
Aug 12, 2016 at 6:26
Aug 11, 2016 at 13:45 history asked Semyon Pilyukov CC BY-SA 3.0