![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On 19/01/2011 4:12 PM, andrel wrote:
> You don't honestly expect anyone to answer that, do you?
I will.
No! he's winding you up. :-P
--
Regards
Stephen
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Invisible wrote:
> arguably clearer than the actual paper book I'm currently reading,
Yep. It's like high-gloss paper without the gloss. Very high resolution and
very smooth. Much easier to read than a standard paperback book.
--
Darren New, San Diego CA, USA (PST)
Serving Suggestion:
"Don't serve this any more. It's awful."
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Invisible wrote:
> why is the iPhone the only device on the market to
> do this?
Why would you say it is?
--
Darren New, San Diego CA, USA (PST)
Serving Suggestion:
"Don't serve this any more. It's awful."
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On 19/01/2011 4:08 PM, andrel wrote:
>>> Reading and listening a lot until you get a feeling for the language.
>>
>> Oh! Just like native speakers :-)
>
> yes, it does probably explain the FTFY from Andy yesterday.
To deep for me ;-)
--
Regards
Stephen
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On 19/01/2011 04:23 PM, Darren New wrote:
> Invisible wrote:
>> why is the iPhone the only device on the market to do this?
>
> Why would you say it is?
He didn't say "lots of devices do this", he said "the iPhone does this".
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Stephen wrote:
> On 19/01/2011 1:35 AM, Jim Henderson wrote:
>>> "It will be John and I coming tomorrow" sounds fine to me in answer to
>>> > "Who will be coming tomorrow?"
>> It's a bit formal, and still doesn't sound right to me. In answer to
>> that question, most people would say "John and I" or some variation
>> thereof - "Me and John" would be grammatically incorrect, but what a lot
>> of Americans would actually say, or "John and me" for that matter.)
>>
>
> Try "John and I are coming tomorrow" or "will be"
I'm not saying it's the only or best way of phrasing it. But it's perfectly
good english to say "It will be John and I attending." You might reply that
on a wedding invitation or something, because it sounds a bit formal, but
it's nowhere near wrong.
--
Darren New, San Diego CA, USA (PST)
Serving Suggestion:
"Don't serve this any more. It's awful."
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On 19/01/2011 04:23 PM, Stephen wrote:
> On 19/01/2011 4:08 PM, andrel wrote:
>>>> Reading and listening a lot until you get a feeling for the language.
>>>
>>> Oh! Just like native speakers :-)
>>
>> yes, it does probably explain the FTFY from Andy yesterday.
>
> To deep for me ;-)
Shouldn't that be "too deep"?
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On 19/01/2011 4:28 PM, Invisible wrote:
> Shouldn't that be "too deep"?
Oh! Bugger off, ya big toerag :-P
--
Regards
Stephen
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On 19/01/2011 4:28 PM, Darren New wrote:
>>> , or "John and me" for that matter.)
>>>
>>
>> Try "John and I are coming tomorrow" or "will be"
>
> I'm not saying it's the only or best way of phrasing it. But it's
> perfectly good english to say "It will be John and I attending." You
> might reply that on a wedding invitation or something, because it sounds
> a bit formal, but it's nowhere near wrong.
No arguments. It was “I coming tomorrow" I meant.
--
Regards
Stephen
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
>> When I got 3Dfx card ages ago I remember setting my CRT to 640x480x120Hz
>> and playing Forsaken (one of the bundled games). As long as there wasn't
>> much on-screen action it would run at 120 fps and that was sweeeeet.
>
> Um... can you actually do that? I mean, do there actually exist any
> display devices that operate at some frequency other than 50Hz or 60Hz?
IIRC most CRTs could be set to run at almost any frequency up to some
maximum. 75 and 85 Hz was very common as 60 Hz gave quite bad
flickering. LCDs can easily manage 120 Hz now, even 480 Hz:
http://www.extremetech.com/article2/0,2845,2337668,00.asp
The problem is the TVs are designed to only accept 60 Hz signals and
create the inbetween frames themselves. If only they could allow higher
frame rate data to be supplied from outside we'd be sorted (also I have
no idea what limitations are in current graphics cards regarding high
framerates). It surely can't be far off, I expect 3D to drive the
change, as consoles/PCs will soon be required to send data at 120 Hz to
give 60 Hz to each eye.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |