[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Strange Bug in GtkText ... I think.



Kevin Atkinson wrote:

I just released I forget the URL for gaspell.  It is
http://metalab.unc.edu/kevina/aspell/.

> 
> I have been having trouble with my gaspell applit for quite some time
> now but it got a lot worse when I updated to the October gnome release
> which has gtk 1.2.6 in it.
> 
> I think it is a bug in the GtkText widget, but I am not sure.
> 
> What happens is that either, the wrong text is highlighted in red when
> gaspell highlights the misspelled word, OR gaspell just crashes.
> 
> Here is how to reproduce the problem with the October gnome release.
> 
> 1) Download and compile gaspell.
> 2) *Paste* the text at the end of the message in gaspell. (If you save
> the text in a file and then open the problem disappears)
> 3) Click at the very beginning of the text
> 4) Click on start.
> 5) Ignore Hauppague
> 6) correct manuual
> 7) notice how "then W" is highlighted instead of "WinTV's"
> 8) If you keep on correcting gaspell may crash
> 
> Also
> 
> to make gaspell crash for sure just paste the first 2 or three
> paragraphs in and start at step 3.
> 
> I have carefully debugged my code and can not seam to find anything that
> I am doing wrong which leads me to believe that is is a Gtk+ bug.
> However, I am not a Gtk+ expect as this is my only Gtk+ programs I have
> written.
> 
> So, I would *really* appreciate it if someone who knows Gtk+ well and a
> little C++ could look at my gaspell program and tell me what the heck is
> going on.  Ie.  is it me or Gtk+.  And, if it is Gtk+, how can I can
> around the bug until it is fixed for good.
> 
> Thanks in advance.
> 
> Begin test text:
> 
> According to the Hauppague manuual:
> 
> Live TV can be displayed on your VGA screen by using either _Video
> Overlay_ or the _Primary Surface_ mode.
> 
> ... then WinTV's Video Digitizer "pushes" YUV 4:2:2 video pixels for
> temporary storage into an off-screen part of the VGA meory called a
> Secondary Surface.  This method is called Video Overlay.  The VGA
> display adapter will then convert the video image from YUV 4:2:2 inbto
> RGB video and continuosly overlay the VGA screen with the video image.
> Using Video Overlay, the VGA controller treats the live TV image just
> like any other window, which results in a 24-bit video image on your
> VGA screen.  You will be able to display full screen TV at all VGA
> resolutions.
> 
> ... but does not have either a Video Port or enough memory to hold the
> video image off-screen, then the WinTV board converts the YUV 4:2:2
> video pixels into an RGB format which is compatible with you VGA
> adaptor's operating mode (8 biuts per pixel, 16 bits per pixel, or
> 24-bits per pixel) and then moves the pixels direcly into the display
> memory Primary Surface of your VGA.
> 
> This results in a high quality video image whose color depth is
> dependent upon youe VGA display adapror'soperating mode.
> 
> Also becuase the video is moved direcyly onto the Primary Surface,
> featurs such as close captiojning and full-screeen TV in resolutions
> greather than 640x480 will be disabled.
> 
> Now by question is: Which mode does the Linux drivers use?  I suspect
> it is Primarty Surface becuase I can not get video at resolutions
> greather than 640x480.
> 
> Also, is the linux driver capable of cpaturing video at resolutions
> greather than 640x480?  I release that the actual singal is no more
> than roughly 640x480 but I would be really nice if I could capture
> higer resolution images.  The reselting images are sligtly better than
> capturing an image at 640x480 and then resizeing it using gimp or some
> related tool.
> 
> --
> Kevin Atkinson
> kevinatk@home.com
> http://metalab.unc.edu/kevina/

-- 
Kevin Atkinson
kevinatk@home.com
http://metalab.unc.edu/kevina/



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]