[AGR] Problem with dialogs derived from org.eclipse.swt.widgets.Dialog [message #89416] |
Tue, 05 December 2006 14:22 |
Eclipse User |
|
|
|
Originally posted by: ffr.softwareag.com
Hm, is it possible that AGR (v4.2.1) is not able to record events on dialogs
that are derived from org.eclipse.swt.widgets.Dialog at all? No shell
element is created in the macro when some action leads to dialog activation.
I tried to find out what happens during some debugging sessions. My strong
feeling is that AGR is only aware of the JFace dialogs and wizard dialogs
but not of the SWT dialogs. Do I fool myself or isn't this a painful
functionality hole?
|
|
|
|
Re: [AGR] Problem with dialogs derived from org.eclipse.swt.widgets.Dialog [message #89521 is a reply to message #89435] |
Wed, 06 December 2006 14:14 |
Eclipse User |
|
|
|
Originally posted by: ffr.softwareag.com
As far as I understand native dialogs are those provided by the operating
system itself (like the open/save file dialog that is mentioned in the
bugzilla entry). Am I right?
My point is the following: In case of I create a dialog for my application,
I can chose to create a new class that extends the SWT dialog class
(org.eclipse.swt.widgets.Dialog) or one that extends the JFace dialog class
(org.eclipse.jface.dialogs.Dialog). AGR recording only recognizes those that
extend the JFace dialog class but not those that extend the SWT dialog
class.
During my debugging sessions I found out that there is some code missing in
method 'activateShell' of class Macro (package
org.eclipse.tptp.test.auto.internal.macro). This method is only aware of
JFace dialogs (and the Window class) but not of the SWT dialogs. My only
question is whether this is intended or was the SWT dialog simply forgotten
and how this can be repaired.
"Liz Dancy" <lizdancy@ca.ibm.com> wrote in message
news:el4btm$hhm$1@utils.eclipse.org...
From what I understand, you are inquiring about native dialog support. There
is currently a defect open to address native dialog support in AGR. Please
feel free to add your comments at:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=164192
Please let me know if you have any further questions.
Sincerely,
Liz Dancy
"Frank Froehlich" <ffr@softwareag.com> wrote in message
news:el3vbp$r2o$1@utils.eclipse.org...
> Hm, is it possible that AGR (v4.2.1) is not able to record events on
> dialogs
> that are derived from org.eclipse.swt.widgets.Dialog at all? No shell
> element is created in the macro when some action leads to dialog
> activation.
> I tried to find out what happens during some debugging sessions. My strong
> feeling is that AGR is only aware of the JFace dialogs and wizard dialogs
> but not of the SWT dialogs. Do I fool myself or isn't this a painful
> functionality hole?
>
>
|
|
|
Re: [AGR] Problem with dialogs derived from org.eclipse.swt.widgets.Dialog [message #89653 is a reply to message #89521] |
Thu, 07 December 2006 16:49 |
Liz Dancy Messages: 77 Registered: July 2009 |
Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_004D_01C719F5.BFFC8DB0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Thanks for your reply and clarification. You are correct that support =
for SWT dialogs is missing and needs to be added. I have opened a defect =
based on this request. Please see:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=3D167105.
Feel free to post additional comments to this defect and add yourself to =
the cc list to follow its progress.
Sincerely,
Liz Dancy
"Frank Froehlich" <ffr@softwareag.com> wrote in message =
news:el6j89$j2o$1@utils.eclipse.org...
> As far as I understand native dialogs are those provided by the =
operating=20
> system itself (like the open/save file dialog that is mentioned in the =
> bugzilla entry). Am I right?
>=20
> My point is the following: In case of I create a dialog for my =
application,=20
> I can chose to create a new class that extends the SWT dialog class=20
> (org.eclipse.swt.widgets.Dialog) or one that extends the JFace dialog =
class=20
> (org.eclipse.jface.dialogs.Dialog). AGR recording only recognizes =
those that=20
> extend the JFace dialog class but not those that extend the SWT dialog =
> class.
>=20
> During my debugging sessions I found out that there is some code =
missing in=20
> method 'activateShell' of class Macro (package=20
> org.eclipse.tptp.test.auto.internal.macro). This method is only aware =
of=20
> JFace dialogs (and the Window class) but not of the SWT dialogs. My =
only=20
> question is whether this is intended or was the SWT dialog simply =
forgotten=20
> and how this can be repaired.
>=20
>=20
> "Liz Dancy" <lizdancy@ca.ibm.com> wrote in message=20
> news:el4btm$hhm$1@utils.eclipse.org...
> From what I understand, you are inquiring about native dialog support. =
There=20
> is currently a defect open to address native dialog support in AGR. =
Please=20
> feel free to add your comments at:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=3D164192
>=20
> Please let me know if you have any further questions.
>=20
>=20
> Sincerely,
>=20
> Liz Dancy
>=20
>=20
> "Frank Froehlich" <ffr@softwareag.com> wrote in message=20
> news:el3vbp$r2o$1@utils.eclipse.org...
>> Hm, is it possible that AGR (v4.2.1) is not able to record events on=20
>> dialogs
>> that are derived from org.eclipse.swt.widgets.Dialog at all? No shell
>> element is created in the macro when some action leads to dialog=20
>> activation.
>> I tried to find out what happens during some debugging sessions. My =
strong
>> feeling is that AGR is only aware of the JFace dialogs and wizard =
dialogs
>> but not of the SWT dialogs. Do I fool myself or isn't this a painful
>> functionality hole?
>>
>>=20
>=20
>
------=_NextPart_000_004D_01C719F5.BFFC8DB0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2995" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>Thanks for your reply=20
and clarification. You are correct that support for SWT=20
dialogs is missing and needs to be added. I have opened a =
defect based=20
on this request. Please see:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><A=20
href=3D"https://bugs.eclipse.org/bugs/show_bug.cgi?id=3D167105">https://b=
ugs.eclipse.org/bugs/show_bug.cgi?id=3D167105</A>.</FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Feel free to post additional comments =
to this=20
defect and add yourself to the cc list to follow its =
progress.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Sincerely,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Liz Dancy</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2> "Frank Froehlich" <</FONT><A=20
href=3D"mailto:ffr@softwareag.com"><FONT face=3DArial=20
size=3D2>ffr@softwareag.com</FONT></A><FONT face=3DArial size=3D2>> =
wrote in=20
message </FONT><A href=3D"news:el6j89$j2o$1@utils.eclipse.org"><FONT =
face=3DArial=20
size=3D2>news:el6j89$j2o$1@utils.eclipse.org</FONT></A><FONT =
face=3DArial=20
size=3D2>...</FONT></DIV><FONT face=3DArial size=3D2>> As far as I =
understand=20
native dialogs are those provided by the operating <BR>> system =
itself (like=20
the open/save file dialog that is mentioned in the <BR>> bugzilla =
entry). Am=20
I right?<BR>> <BR>> My point is the following: In case of I create =
a=20
dialog for my application, <BR>> I can chose to create a new class =
that=20
extends the SWT dialog class <BR>> (org.eclipse.swt.widgets.Dialog) =
or one=20
that extends the JFace dialog class <BR>> =
(org.eclipse.jface.dialogs.Dialog).=20
AGR recording only recognizes those that <BR>> extend the JFace =
dialog class=20
but not those that extend the SWT dialog <BR>> class.<BR>> =
<BR>> During=20
my debugging sessions I found out that there is some code missing in =
<BR>>=20
method 'activateShell' of class Macro (package <BR>>=20
org.eclipse.tptp.test.auto.internal.macro). This method is only aware of =
<BR>> JFace dialogs (and the Window class) but not of the SWT =
dialogs. My=20
only <BR>> question is whether this is intended or was the SWT dialog =
simply=20
forgotten <BR>> and how this can be repaired.<BR>> <BR>> =
<BR>> "Liz=20
Dancy" <</FONT><A href=3D"mailto:lizdancy@ca.ibm.com"><FONT =
face=3DArial=20
size=3D2>lizdancy@ca.ibm.com</FONT></A><FONT face=3DArial size=3D2>> =
wrote in=20
message <BR>> </FONT><A =
href=3D"news:el4btm$hhm$1@utils.eclipse.org"><FONT=20
face=3DArial =
size=3D2>news:el4btm$hhm$1@utils.eclipse.org</FONT></A><FONT =
face=3DArial=20
size=3D2>...<BR>> From what I understand, you are inquiring about =
native dialog=20
support. There <BR>> is currently a defect open to address native =
dialog=20
support in AGR. Please <BR>> feel free to add your comments =
at:<BR>>=20
</FONT><A =
href=3D"https://bugs.eclipse.org/bugs/show_bug.cgi?id=3D164192"><FONT=20
face=3DArial=20
size=3D2>https://bugs.eclipse.org/bugs/show_bug.cgi?id=3D164192</FONT></A=
><BR><FONT=20
face=3DArial size=3D2>> <BR>> Please let me know if you have any =
further=20
questions.<BR>> <BR>> <BR>> Sincerely,<BR>> <BR>> Liz=20
Dancy<BR>> <BR>> <BR>> "Frank Froehlich" <</FONT><A=20
href=3D"mailto:ffr@softwareag.com"><FONT face=3DArial=20
size=3D2>ffr@softwareag.com</FONT></A><FONT face=3DArial size=3D2>> =
wrote in=20
message <BR>> </FONT><A =
href=3D"news:el3vbp$r2o$1@utils.eclipse.org"><FONT=20
face=3DArial =
size=3D2>news:el3vbp$r2o$1@utils.eclipse.org</FONT></A><FONT =
face=3DArial=20
size=3D2>...<BR>>> Hm, is it possible that AGR (v4.2.1) is not =
able to=20
record events on <BR>>> dialogs<BR>>> that are derived from=20
org.eclipse.swt.widgets.Dialog at all? No shell<BR>>> element is =
created=20
in the macro when some action leads to dialog <BR>>>=20
activation.<BR>>> I tried to find out what happens during some =
debugging=20
sessions. My strong<BR>>> feeling is that AGR is only aware of the =
JFace=20
dialogs and wizard dialogs<BR>>> but not of the SWT dialogs. Do I =
fool=20
myself or isn't this a painful<BR>>> functionality=20
hole?<BR>>><BR>>> <BR>> <BR>></FONT></BODY></HTML>
------=_NextPart_000_004D_01C719F5.BFFC8DB0--
|
|
|
Re: [AGR] Problem with dialogs derived from org.eclipse.swt.widgets.Dialog [message #89804 is a reply to message #89653] |
Fri, 08 December 2006 14:11 |
Eclipse User |
|
|
|
Originally posted by: ffr.softwareag.com
Thank you too! In the meantime I managed to add the missing functionality
for my own. Less than ten lines of code fix the problem.
"Liz Dancy" <lizdancy@ca.ibm.com> wrote in message
news:el9gnk$nln$1@utils.eclipse.org...
Thanks for your reply and clarification. You are correct that support for
SWT dialogs is missing and needs to be added. I have opened a defect based
on this request. Please see:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=167105.
Feel free to post additional comments to this defect and add yourself to the
cc list to follow its progress.
Sincerely,
Liz Dancy
"Frank Froehlich" <ffr@softwareag.com> wrote in message
news:el6j89$j2o$1@utils.eclipse.org...
> As far as I understand native dialogs are those provided by the operating
> system itself (like the open/save file dialog that is mentioned in the
> bugzilla entry). Am I right?
>
> My point is the following: In case of I create a dialog for my
> application,
> I can chose to create a new class that extends the SWT dialog class
> (org.eclipse.swt.widgets.Dialog) or one that extends the JFace dialog
> class
> (org.eclipse.jface.dialogs.Dialog). AGR recording only recognizes those
> that
> extend the JFace dialog class but not those that extend the SWT dialog
> class.
>
> During my debugging sessions I found out that there is some code missing
> in
> method 'activateShell' of class Macro (package
> org.eclipse.tptp.test.auto.internal.macro). This method is only aware of
> JFace dialogs (and the Window class) but not of the SWT dialogs. My only
> question is whether this is intended or was the SWT dialog simply
> forgotten
> and how this can be repaired.
>
>
> "Liz Dancy" <lizdancy@ca.ibm.com> wrote in message
> news:el4btm$hhm$1@utils.eclipse.org...
> From what I understand, you are inquiring about native dialog support.
> There
> is currently a defect open to address native dialog support in AGR.
> Please
> feel free to add your comments at:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=164192
>
> Please let me know if you have any further questions.
>
>
> Sincerely,
>
> Liz Dancy
>
>
> "Frank Froehlich" <ffr@softwareag.com> wrote in message
> news:el3vbp$r2o$1@utils.eclipse.org...
>> Hm, is it possible that AGR (v4.2.1) is not able to record events on
>> dialogs
>> that are derived from org.eclipse.swt.widgets.Dialog at all? No shell
>> element is created in the macro when some action leads to dialog
>> activation.
>> I tried to find out what happens during some debugging sessions. My
>> strong
>> feeling is that AGR is only aware of the JFace dialogs and wizard dialogs
>> but not of the SWT dialogs. Do I fool myself or isn't this a painful
>> functionality hole?
>>
>>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.02945 seconds