image issues

Only because I don't know what they are. I've got a spare half hour later tonight, tell me what they are. If the techniques fit with what I already have I'll put them in.

I didn't realize it was changing the aspect ratio that you were interested in. It would be easy to do option 2, but why? Is there any demand? The neat thing about specifying only width is that it maintains aspect ratio.A question. If the image is 500x300 but you specify 100x100, when you click on the magnifying glass cursor does the image go to it's normal 500x300, or does it maintain aspect ratio and go to 500x500, or maybe 300x300?--Percy

I implemented this a couple days ago and was waiting to see if CS would chime in. I decided that maintaining aspect ratio was the correct action when changing image size. It'll become available the next time I post an update.

You can do that now, just leave out the space after the comma: Sorry it's so picky about punctuation, I'll take a look at making it more flexible.

I've just released a couple minor improvements to the [img] and [thumb] dBCodes. You can now specify a height along with a width. For example, this would specify that the image be displayed at 100 pixels wide by 200 pixels high: If the actual image width is larger than the displayed image width then when you click on the image it will grow to it's actual width, but the aspect ratio of 100x200 will be maintained. In other words, the image will still be twice as high as wide, as seen here. The first image specifies only a width of 100, while the second specifies a width/height of 100x200, click on the images to see how aspect ratio is maintained: The other minor improvement is that extraneous white space around the arguments is ignored. For example, this now works: It would display like this: Edited by Admin, : Grammar.Edited by Admin, : Grammar again.Edited by Admin, : Rerender now that newly introduced image display bug is fixed.