On Nov 1, 2008, at 11:07 AM, Bob Mathias - Sysero llc Dev wrote:
> My next project is to create a Main Application Window using
> ClassEditor that will have a panel at the top with Buttons. When a
> button is pressed another panel on the left side will appear with the
> related action buttons. The user will select a button on the left
> that
> will fire up a Business Function like Payroll. What I want to do is
> Design with the ClassEditor a independent Window called Payroll. I
> think I need to save this in the ClassEditor as a Class. When the
> user
> is done with the Payroll Window I want to free up the memory by
> Closing
> the Payroll Window and returning to my Main Application Window.
>
> Can this be done with Dabo? If not is there any idea of working
> around the problem.
Save your forms as normal cdxmls, not using the 'Save As Class'
function, which saves controls and groups of controls, but not the
entire form. All "windows" that are opened must be either a dForm or a
dDialog subclass.
To run your form, just call: dabo.ui.createForm("payroll.cdxml"). If
you want, you can also hide() the main form if that makes sense, and
show() it when the payroll form is closed.
-- Ed Leafe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]
