_id865&opÌk
___
Perl-Win32-GUI-Users mailing list
Perl-Win32-GUI-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users
http://perl-win32-gui.sourceforge.net/
OK. So it is SetCheck and not SetState :)
Now I see it. T
Robert May wrote:
Piotr Kaluski wrote:
Hi,
When you read about button related messages in MSDN, BM_SETCHECK gives
you
an opportunity to set button's state to BST_INDETERMINATE, which is
presented by a gray color. Is there a way to gray out a button in
Win32::GUI (apart from using SendMe
Hi,
When you read about button related messages in MSDN, BM_SETCHECK gives you
an opportunity to set button's state to BST_INDETERMINATE, which is
presented by a gray color. Is there a way to gray out a button in
Win32::GUI (apart from using SendMessage directly)?
--Piotr
Glenn Linderman wrote:
>> It seams that you have a pretty complete and consistent vision on how to
>> do it. IMHO, it would be beneficial if you convert it to the code. It
>> would have 2 advantages:
>> 1. You yourself would be able to verify if your concept is consistent
>> 2. Others would be abl
ted in the other thread. Would this still work? I
guess what I'm trying to say is that if we do make all Win32::GUI
function calls work across processes, they should also work across all
threads within the same process that is running Win32::GUI.
Cheers,
jez.
I didn't test it bu
ion of memory in other process
address space is another. You can use either former or latter of them. You don't
have to use both methods together (you can, but you don't have to).
--
Piotr Kaluski
"It is the commitment of the individuals to excellence,
their mastery of the tools
;);
XST_mIV(3, lv_item.iImage);
XST_mPV(4, "-state");
XST_mIV(5, lv_item.state);
XSRETURN(6);
} else {
XSRETURN_UNDEF;
}
I am curious what do you think about it.
--
Piotr Kaluski
"It is the commitment of the individuals to excellence,
their mastery of the tools of their crafts, and their
ability to work together that makes the product, not rules."
("Testing Computer Software" by Cem Kaner, Jack Falk, Hung Quoc Nguyen)
to simply Reply-All to mailing list messages.]
OK. I understand the reason now. Go ahead with your standard way. After all it
is not a big deal if I receive some duplicates.
--
Piotr Kaluski
"It is the commitment of the individuals to excellence,
their mastery of the tools of their crafts,
Hi,
On Thu, 06 Oct 2005 22:08:13 +0100
Robert May <[EMAIL PROTECTED]> wrote:
> So, from a Win32:GUI point of view I would think that building
> Win32::Gui::Test on top of the existing Win32::GUI framework makes a lot
> of sense. From a Win32::GuiTest point of view I think there needs to be
> some
points above to be major obstacles. This is
definitely an idea worth consideration. Let's sleep on it. I will post your idea
in our group.
--
Piotr Kaluski
"It is the commitment of the individuals to excellence,
their mastery of the tools of their crafts, and their
ability to work togethe
Hi,
I am one of developers of Win32::GuiTest library. It is a module for GUI
test automation. I am actually pretty impressed with all the great work
you have done. Using your module should free us from writing some
functions ourselves.
I have one question. My impression is, that your library is obj
11 matches
Mail list logo