Re: A Parable of Two Carpenters

From: The Half A Wannabee (ShakainZulu_AT_Ozzy_DMX_ODB_&_C_NowWhereToRun_at_hotmail.com)
Date: 11/26/03

  • Next message: The Half A Wannabee: "Re: Whiny CS Majors" 
    Date: Wed, 26 Nov 2003 08:22:17 +0100

    "quality computer systems" <qual1@nwidt.com> wrote in message
    news:bq0n64$73m$1@news.netins.net...
    > Sage,
    >
    > Excelllent.
    > Good to have a purpose in life. Hope Linux isn't quite so bad.

    Hehe. I would rather claim : Its good NOT to have a purpose in life.

    > Good Luck.
    >
    > John
    >
    > The Half A Wannabee wrote:
    > > "John lauman" <qual1@midlands.net> wrote in message
    > > news:bpvlpg$pph$1@news.netins.net...
    > >
    > >>After further thought. I will do some investigation.
    > >>
    > >>John
    > >
    > >
    > > Oki. Please do. Because after all (disclaimer follows), I may have been
    too
    > > angry back than, that I just didnt see a solution. And I see no reason
    to
    > > unzip my old VCL library code at *this* point to test it any further. By
    the
    > > way, this was on a Win98 system, maybe two years ago.
    > >
    > > But everywhere when I see a scrollbar (MS) in a document or a list or
    > > something, I try to see if someone has used it in a manner like that. I
    have
    > > yet to see it. They always seem to just MAP the resolution into
    something
    > > less than smooth. Of course I havent seen everything so....
    > >
    > > The new skin library from MS. The manifest? (Dont know it) may have
    solved
    > > this problem of course, once and for all. I would expect it, since it
    seems
    > > very capable. At least it looks capable.
    > >
    > > Java ? Dont know much of Java. I have trouble enough learning one
    language,
    > > perhaps two. Ask the dearest PDF Jedi, he seem to know all of them :-)
    > >
    > > Linux is interessting. I will shortly port most of my code there,
    hopefully
    > > by end of february. I have ordered another cheap machine for that
    purpose,
    > > which I should bring back home with me tomorrow. As you can tell I am a
    > > litle excited about it, cause judging from what I heard Linux is also
    far
    > > from perfect....so trouble here we come. The coolest thing about
    creating
    > > your own graphical objects is that porting becomes so much easier. You
    just
    > > have to port the API calls for the drawing code. And I will be dreaming
    like
    > > that until I know better.
    > >
    > > Enough.
    > >
    > >
    > >
    > >>The Half A Wannabee wrote:
    > >>
    > >>>"John lauman" <qual1@midlands.net> wrote in message
    > >>>news:bpv5ol$4pe$1@news.netins.net...
    > >>>
    > >>>
    > >>>>Sage,
    > >>>>Just a thought?
    > >>>>
    > >>>>
    > >>>>>Example. The win32 scrollbar object is (still????) 16 bit. Making it
    16
    > >>>
    > >>>bit
    > >>>
    > >>>
    > >>>>>causes problems when
    > >>>>>e.g you want to softscroll a large document. You run out of
    resoultion.
    > >>>>
    > >>>>The GetScrollInfo function enables applications to use 32-bit scroll
    > >>>>positions. Although the messages that indicate scroll-bar position,
    > >>>>WM_HSCROLL and WM_VSCROLL, provide only 16 bits of position data, the
    > >>>>functions SetScrollInfo and GetScrollInfo provide 32 bits of
    scroll-bar
    > >>>>position data. Thus, an application can call GetScrollInfo while
    > >>>>processing either the WM_HSCROLL or WM_VSCROLL messages to obtain
    32-bit
    > >>>>scroll-bar position data.
    > >>>>
    > >>>>To get the 32-bit position of the scroll box (thumb) during a
    > >>>>SB_THUMBTRACK request code in a WM_HSCROLL or WM_VSCROLL message, call
    > >>>>GetScrollInfo with the SIF_TRACKPOS value in the fMask member of the
    > >>>>SCROLLINFO structure. The function returns the tracking position of
    the
    > >>>>scroll box in the nTrackPos member of the SCROLLINFO structure. This
    > >>>>allows you to get the position of the scroll box as the user moves it.
    > >>>>The following sample code illustrates the technique.
    > >>>>
    > >>>
    > >>>
    > >>>LOL. :-) I have tried it. MS doesnt even use that "functionality"
    > >>>themselfes....its a patch..
    > >>>not even a patch ...its MS saying "oh *** we blew it...heres a patch
    > >
    > > for
    > >
    > >>>you".
    > >>>But the patch does not work. It causes a naughty bug at each 16 bit
    > >
    > > barrier.
    > >
    > >>>In anycase, it cause you to write much extra code to cope with it, in a
    > >
    > > very
    > >
    > >>>nasty manner.
    > >>>I wrote a scrollbar from scratch and it took me 2 hours.
    > >>>But it took me allmost a day (maybe even more, cant remember) to patch
    > >>>something
    > >>>that worked halfways with the MS object. After spending hours decoding
    > >
    > > the
    > >
    > >>>documentation....
    > >>>
    > >>>
    > >>>
    > >>>>>If you make it 64bit from the start you will never ever have to
    > >>>>
    > >>>>bother with
    > >>>>
    > >>>>>that logic
    > >>>>>again. Ever. Since having a resolution like that, you could
    > >
    > > real-scroll
    > >
    > >>>a
    > >>>
    > >>>
    > >>>>>Movie, frame
    > >>>>>by frame (100 nanoseconds), and still have plenty of resolution left.
    > >>>>
    > >>>>
    > >>>>Eventually even 64 bit will not be big enough.
    > >>>>Again this is based on the Least Common Denominator of the processor
    and
    > >>>>the context of when it was created.
    > >>>>
    > >>>>IMHO,
    > >>>>
    > >>>>John
    > >>>>
    > >>>
    > >>>
    > >>>With a fine resolution scrollbar :
    > >>>
    > >>>On a 1024*768 resolution screen, 65536 pixels gets you 85 pages into
    the
    > >>>document perhaps.
    > >>>a 64 bit scrollbar will not stop until 24019198012642645 pages.
    > >>>Thats maybe the PDF from Randall in 2020 ?
    > >>>
    > >>>
    > >>
    > >
    > >
    >

  • Next message: The Half A Wannabee: "Re: Whiny CS Majors"
    • Quantcast