From: mark samir <ai.robotic@googlemail.com>
To: caml-list@yquem.inria.fr
Subject: GPack.paned problem
Date: Wed, 16 Nov 2005 11:41:52 +0100 [thread overview]
Message-ID: <eefc05450511160241v1fc82f76wffdf3b4b304c7465@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 633 bytes --]
Dear All friends,
I use the GPack.paned for separating the two areas of my program'GUI. These
two areas are GPack.vbox. When I resize the two areas, there is a little
noise in the boundary of these two areas. But when I move the mouse in that
areas, the noise are cleared and two areas are presented well. It seems that
if the areas are refreshed, the noise in the boundary will be removed. I
don't know the reason of this problem. I sent email to the ocaml_biginers
and one person reply me I don't have this problem in my program. Maybe I
must do a special setting in my program.
does anybody has any idea?
thanks,
Mark
[-- Attachment #2: Type: text/html, Size: 673 bytes --]
next reply other threads:[~2005-11-16 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 10:41 mark samir [this message]
2005-11-16 11:58 ` [Caml-list] " Richard Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=eefc05450511160241v1fc82f76wffdf3b4b304c7465@mail.gmail.com \
--to=ai.robotic@googlemail.com \
--cc=caml-list@yquem.inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).