From: Staffan T. <sta...@gm...> - 2013-02-25 22:59:24
|
Mark, thanks for implementing support for popupAsChild with pSheets, much appreciated. I find when trying it that it supports psheet~popupAsChild(parent) but not psheet~popupAsChild(parent, "SHOWTOP"). Is it just my code or is it a limitation in the implementation or is it a bug? Staffan |
From: Mark M. <mie...@gm...> - 2013-02-25 23:27:17
|
On Mon, Feb 25, 2013 at 2:58 PM, Staffan Tylen <sta...@gm...>wrote: > Mark, thanks for implementing support for popupAsChild with pSheets, much > appreciated. I find when trying it that it supports > psheet~popupAsChild(parent) but not psheet~popupAsChild(parent, "SHOWTOP"). > Is it just my code or is it a limitation in the implementation or is it a > bug? > SHOWTOP is meaningless in this context isn't? What would show top add that isn't happening now? It's not a bug because the implementation purposefully only accepts 1 argument. What would differentiate popupAsChild(parent) and popupAsChild(parent, "SHOWTOP") ? -- Mark Miesfeld > > Staffan > > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_feb > _______________________________________________ > Oorexx-users mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-users > > |
From: Staffan T. <sta...@gm...> - 2013-02-25 23:47:31
|
> SHOWTOP is meaningless in this context isn't? > > What would show top add that isn't happening now? > > It's not a bug because the implementation purposefully only accepts 1 > argument. What would differentiate popupAsChild(parent) and > popupAsChild(parent, "SHOWTOP") ? > > I guess I don't know. In that case the documentation should probably state that all other parameters except the first are invalid for pSheets. Or maybe it already does, I haven't downloaded the latest version actually :( Staffan |
From: Mark M. <mie...@gm...> - 2013-02-26 00:47:26
|
On Mon, Feb 25, 2013 at 3:46 PM, Staffan Tylen <sta...@gm...>wrote: > > SHOWTOP is meaningless in this context isn't? >> >> What would show top add that isn't happening now? >> >> It's not a bug because the implementation purposefully only accepts 1 >> argument. What would differentiate popupAsChild(parent) and >> popupAsChild(parent, "SHOWTOP") ? >> >> > I guess I don't know. In that case the documentation should probably state > that all other parameters except the first are invalid for pSheets. Or > maybe it already does, I haven't downloaded the latest version actually :( > >From the PropertySheetDialog doc for popupAsChild(): Arguments: The single argument is: parent [required] Some other Rexx dialog object. A relationship is established with the parent dialog such that when the parent dialog is closed, this dialog is automatically closed also. So, it is documented as taking only a single argument. ;-) This is really a another case of a PropertySheetDialog dialog is unlike all other ooDialog dialogs. The operating system completely manages the underlying property sheet window. The underlying windows of all other ooDialog dialogs are completely managed by ooDialog. When an underlying window is first created, it needs to be positioned and shown. For the property sheet window, the operating system does that positioning and showing. For all other ooDialog dialogs, that positioning and showing must be done by ooDialog. That's where the show top comes from. As I said, show top is meaningless in the context of a property sheet, the operating system system does that. -- Mark Miesfeld |
From: Art H. <art...@ar...> - 2013-02-26 01:13:00
|
Mark, Do you have any plans to support the FileNameDialog to return the file name when it is not an existing file instead of giving a popup error message in a future update? There is a sample .oleObject that uses the UserAccounts.CommonDialog that works well for what I am trying, but the UserAccounts.CommonDialog is no longer available after XP. I can use an EditText control with some prompts, but having a dialog would look and work much better for me. Should I submit this as a req? -- Art Heimsoth - art...@ar... |
From: Mark M. <mie...@gm...> - 2013-02-26 03:08:02
|
On Mon, Feb 25, 2013 at 5:12 PM, Art Heimsoth <art...@ar...>wrote: > > Do you have any plans to support the FileNameDialog to return the file name > when it is not an existing file instead of giving a popup error message in > a future update? I have plans to add an interface to the newer Common Item Dialog which is the Vista / Windows 7 version of the open / save file dialog. I'm not sure if that supports what you want or not I will probably just leave the existing FilnNameDialog alone > There is a sample .oleObject that uses the > UserAccounts.CommonDialog that works well for what I am trying, but > the UserAccounts.CommonDialog is no longer available after XP. Is this a sample we distribute with ooRexx? If you give me the name so I can look at it, I'll try to support what you want with the Open Item Dialog. Which it already may do. Open Item Dialog is similar to the browse for folder I just did, as it is also a COM object. It may be an extension or enhancement of the UserAccounts.CommonDialog. > I can > use an EditText control with some prompts, but having a dialog would > look and work much better for me. Should I submit this as a req? > Yeah, you should. ;-) If you can attach a small example to the RFE that demonstrates what feature from the UserAccounts.CommonDialgo you would like to see, that would help. Since the UserAccounts.CommonDialog and the Open Item Dialog are both implemented through COM, I'm guessing they have similar features. -- Mark Miesfeld |
From: Art H. <art...@ar...> - 2013-02-26 08:35:02
|
> On Mon, Feb 25, 2013 at 5:12 PM, Art Heimsoth > <art...@ar...> wrote: > >> There is a sample .oleObject that uses the >> >> UserAccounts.CommonDialog that works well for what I am trying, >> but >> > the UserAccounts.CommonDialog is no longer available after XP. > > > Is this a sample we distribute with ooRexx? If you give me the > name so I can look at it, I'll try to support what you want with > the Open Item Dialog. Which it already may do. Open Item Dialog > is similar to the browse for folder I just did, as it is also a COM > object. It may be an extension or enhancement of the > UserAccounts.CommonDialog. > it is the OpenFileDialog zip file found on Lee's http://pragmaticlee.safedataisp.net/ site. > > Yeah, you should. ;-) If you can attach a small example to the > RFE that demonstrates what feature from the > UserAccounts.CommonDialgo you would like to see, that would help. > > > Since the UserAccounts.CommonDialog and the Open Item Dialog are > both implemented through COM, I'm guessing they have similar > features. > Thanks, a RFE will be coming shortly.. > -- > Mark Miesfeld -- Art Heimsoth - art...@ar... |
From: Staffan T. <sta...@gm...> - 2013-02-26 10:07:48
|
> From the PropertySheetDialog doc for popupAsChild(): > > Arguments: > The single argument is: > > parent [required] > > I didn't realise that popup and popupAsChild also are documented under PropertySheetDialog. I was looking at the description under the DialogExtensions mixin class. Staffan |