Sea state

IanW

Well-known member
whitleyprom.jpg


Edited so the picture should hopefully show now.

[Edited on 21/2/2004 by IanW]
 
Says user exceeded daily limit Ian, you been uploading biggies?

I was at King Eddies with bairn from about 1.30 till 3.0pm, you should of popped along. Caught a tiny codling there, got a bit cold and the waves were heading up the prom so moved to the marina. Got a whiting there first chuck, then nowt else. The bairn enjoyed himself anyway.
 
try another piccy ~ resized with a different programme so it looks like it will work with Marks nesa.cibs site.

brownsbay.jpg


[Edited on 21/2/2004 by IanW]

[Edited on 21/2/2004 by IanW]
 
Just for good measure....and the fact that I might never get another picture on the site here\'s another from today

promwash.jpg
 
Tat, if you can see all three pictures, the first is Whiltey Bay prom looking back towards Whitley beach.

The second is abit further down towards Cullercoats and is Brown\'s Bay.

The third is the same prom as the first but looking towards Brown\'s Bay. If you were to fish Whitley pipe you would head down the steps which was where the water was spraying up from.
 
\"..... I might never get another picture on the site\"

Nah......I think you\'ve got it sussed now, Ian ;)
 
Cheers Ian,it\'s a bit like that today,from South Gare to the Bandstand.A bit choppy are the words I\'m looking for.
 
Bit of a strange one this Norman.

When using Micosoft Photo Editor I followed your guidelines to the point of having a file size of around 20K. Tried to upload on nesa.cibs and all I ever got was the file was too big.

Used a free softeare package KeithB found, resized picture to 600 pixels wide and alter resiolution to 72dpi, save and it uploads no problem.

As I said earlier........strange.
 
Hmmnnn. Blame it on bill gates. Micro$oft jpegs do not stricltly adhere to the JPEG standard, whilst most things can deal with it, some things can\'t. One of the things that can\'t is PHP (the language wot the board is written in).

As with many things from M$, they work fine in a wholly M$ environment, but elsewhere may struggle.

I come across hundreds of these little annoyances, the M$ response is usually, do it in ASP instead (an M$ product) or use microsoft SQL server (an M$product) instead, use a server has support frontpage extension (ooh let me guess, I bet that would be a microsoft one) etc etc etc

Frightening to think that the vast majority of systems that run your lives are wholly reliant on M$ somewhere along the line
 
Back
Top