visual basic 6.0 video tutorial 40 videos download

You can create a 'controller' component that do all the work and receive other component events from there, but it would be cleaner to have that in the main script. Being able to export the resulting dxpack directly from my build script will save me a lot of time! I'm using another instance of DX in a VM to export so I don't have to remove the dev version, load the final dxpack, export and then go back to the dev version. I'm post-processing dxpacks from outside DX to merge external scripts, modify scripts with #define/#ifdef/#ifndef, switch script components to release mode, etc. And you can't connect to events easily, see ) There is a lot of things to steal take inspiration from in Yahoo Widgets in terms of proper integration (using external ActiveX objects is nice, but each one has a different API, making using a lot of them a mess.Fix the bug that prevents using more than 2 plugins in a gadget/widget.

Better cloning support (clone groups/use template/etc.).

Zip/Unzip functions available from script.

Proper debugger support for DesktopX scripts (so we can debug scripts in VS or Script Debugger with call stack/variable windows and breakpoints).

Expose animation properties to script (total number of frames, interval, flags).

Expose and document more properties (some useful ones are already available but not documented like OnKeyDown events for listboxes).

Password mode for the edit box without having to use a custom font.

Integrated support for script components (with event handling), so we can receive script events from a DestopX script.

Command line support to build gadgets/widgets from a dxpack and a config file.

Visual basic 6.0 video tutorial 40 videos download