View previous topic :: View next topic |
Author |
Message |
Lynn
Joined: 27 Aug 2004 Posts: 89
|
Posted: Mon May 02, 2005 4:50 am Post subject: Necessary to rename common controls? |
|
|
In dfl\application.d, you rename the common controls:
const char[] CONTROL_CLASSNAME = "DFL_Control";
const char[] FORM_CLASSNAME = "DFL_Form";
const char[] TEXTBOX_CLASSNAME = "DFL_TextBox";
const char[] LISTBOX_CLASSNAME = "DFL_ListBox";
const char[] LABEL_CLASSNAME = "DFL_Label";
const char[] BUTTON_CLASSNAME = "DFL_Button";
const char[] MDICLIENT_CLASSNAME = "DFL_MdiClient";
const char[] RICHTEXTBOX_CLASSNAME = "DFL_RichTextBox";
const char[] COMBOBOX_CLASSNAME = "DFL_ComboBox";
const char[] TREEVIEW_CLASSNAME = "DFL_TreeView";
Is this really necessary? I am not familiar with the low-level programming involved, so this isn't a criticism if it is really the appropriate way to do this.
The reason I ask: I use VisualTest to write scripts to test an application. I've found it invaluable for q/a. There is a call to
WOptionSetClass("DFL_Button")
but I would prefer to avoid this.
I took a look at application.d and tried renaming to just "Button", but the call to superClass in _init failed.
Just checking ... works ok now but wanted to make you aware of VisualTest issue. |
|
Back to top |
|
|
Chris Miller
Joined: 27 Mar 2004 Posts: 514 Location: The Internet
|
Posted: Mon May 02, 2005 5:09 am Post subject: Re: Necessary to rename common controls? |
|
|
Lynn wrote: | In dfl\application.d, you rename the common controls: |
I super class them so that every single window doesn't need to be sub classed. Super classing creates a new window class based on another, which requires me to use a new name.
- Chris |
|
Back to top |
|
|
|