Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.clipper.visual-objects > #727 > unrolled thread
| Started by | james@multiexpress.com |
|---|---|
| First post | 2011-04-06 09:55 -0700 |
| Last post | 2011-04-06 16:46 -0700 |
| Articles | 4 — 3 participants |
Back to article view | Back to comp.lang.clipper.visual-objects
Converting a DATADIALOG to DATAWINDOW james@multiexpress.com - 2011-04-06 09:55 -0700
Re: Converting a DATADIALOG to DATAWINDOW Sherlock <sherlock@sherlock.com.au> - 2011-04-06 16:12 -0700
Re: Converting a DATADIALOG to DATAWINDOW Massimo Bighelli <info@arcasistemi.it> - 2011-04-07 01:44 +0200
Re: Converting a DATADIALOG to DATAWINDOW james@multiexpress.com - 2011-04-06 16:46 -0700
| From | james@multiexpress.com |
|---|---|
| Date | 2011-04-06 09:55 -0700 |
| Subject | Converting a DATADIALOG to DATAWINDOW |
| Message-ID | <b38c7949-df71-460d-8948-5ec1226499b8@k30g2000yqb.googlegroups.com> |
Hi all, I'm currently working on large a VO application that I didn't write and am having some difficulties, mainly because I don't yet understand VO well enough to figure them out. I am converting DATADIALOGs to DATAWINDOWSs so they can be displayed with Show() without being modal. The first one was easy, I simply changed it to INHERIT DATAWINDOW in the class file and it worked the same way. However the second one has a strange problem. For some reason it creates all the input boxes and elements in the parent window instead of it's own new window. Are there any common causes for this, or certain bits of code I should look for? Thanks!
[toc] | [next] | [standalone]
| From | Sherlock <sherlock@sherlock.com.au> |
|---|---|
| Date | 2011-04-06 16:12 -0700 |
| Message-ID | <64ea3cac-4ddc-4a4a-a351-300e5c4d5239@d12g2000vbz.googlegroups.com> |
| In reply to | #727 |
snip[ I am converting DATADIALOGs to DATAWINDOWSs so they can be displayed ] I think Paul Piko developed a simple tool to do this .. from memory. Phil McGuinness
[toc] | [prev] | [next] | [standalone]
| From | Massimo Bighelli <info@arcasistemi.it> |
|---|---|
| Date | 2011-04-07 01:44 +0200 |
| Message-ID | <inits9$ojm$1@speranza.aioe.org> |
| In reply to | #727 |
James, change the owner of the called window Massimo Il 06/04/2011 18:55, james@multiexpress.com ha scritto: > Hi all, > I'm currently working on large a VO application that I didn't write > and am having some difficulties, mainly because I don't yet understand > VO well enough to figure them out. > > I am converting DATADIALOGs to DATAWINDOWSs so they can be displayed > with Show() without being modal. The first one was easy, I simply > changed it to INHERIT DATAWINDOW in the class file and it worked the > same way. However the second one has a strange problem. For some > reason it creates all the input boxes and elements in the parent > window instead of it's own new window. Are there any common causes for > this, or certain bits of code I should look for? > > Thanks!
[toc] | [prev] | [next] | [standalone]
| From | james@multiexpress.com |
|---|---|
| Date | 2011-04-06 16:46 -0700 |
| Message-ID | <ca4f80e0-46b1-4ac2-8141-22c6af1add11@j13g2000yqj.googlegroups.com> |
| In reply to | #730 |
Thanks! I spent the day with trial and error, and this turned out to
be the key
I changed
SUPER:Init(oWindow,ResourceID{"ItemDialog",_GetInst()},iCtlID) to
SUPER:Init(oWindow:Owner,ResourceID{"ItemDialog",_GetInst()},iCtlID)
And now it works perfectly :) I believe it had something to do with
the fact the class calling it didn't have a window of it's own
visible.
I'll also look into the tool you mentioned Phil, that might be useful.
-James
On Apr 6, 4:44 pm, Massimo Bighelli <i...@arcasistemi.it> wrote:
> James,
>
> change the owner of the called window
>
> Massimo
>
> Il 06/04/2011 18:55, ja...@multiexpress.com ha scritto:
>
>
>
>
>
>
>
> > Hi all,
> > I'm currently working on large a VO application that I didn't write
> > and am having some difficulties, mainly because I don't yet understand
> > VO well enough to figure them out.
>
> > I am converting DATADIALOGs to DATAWINDOWSs so they can be displayed
> > with Show() without being modal. The first one was easy, I simply
> > changed it to INHERIT DATAWINDOW in the class file and it worked the
> > same way. However the second one has a strange problem. For some
> > reason it creates all the input boxes and elements in the parent
> > window instead of it's own new window. Are there any common causes for
> > this, or certain bits of code I should look for?
>
> > Thanks!
[toc] | [prev] | [standalone]
Back to top | Article view | comp.lang.clipper.visual-objects
csiph-web