ContentsImporting Visual Patch 1.0 Projects

Introduction

Visual Patch 2.0/3.0 was rebuilt from the ground up to be infinitely more powerful and flexible than previous versions. As such, it required an entirely new "scripting engine" to process actions. This also means that an exact and automated one-to-one conversion of actions from the v1.0 format is impossible. Another significant change is the new format used for screens. While there are many benefits to the new screen design such as the ability to theme your patch, multilingual patches have never been easier to manage. Instead of having to include a new screen for each language in your project, you can now manage all language translations on each screen. Another exciting feature available in version is the addition of our state-of-the-art binary differencing and compressions algorithms. The result is a smaller and better performing software patch.

As a result, the conversion of projects created with v1.0 is not a fully automated process. In general, your versions and file listings will be converted automatically, however some of the file properties have been simplified, therefore they may not all exist. Areas that are not converted include all of your actions, screens, project settings etc.

Converting Projects from v1.0 to v3.0

Given that Visual Patch will only convert your version file lists, you may find it just as easy to create a new project in version using the new Project Wizard. The only reason that you may want to import the version file lists is if you have a large number of versions, or have customized the source and destination paths to a great extent. In most cases, we recommend starting your projects from scratch.

To import your project, simply go to File > Open..., select "Visual Patch 1.0 Files (*.vp1) from the Files of type dropdown and select your Visual Patch 1.0 project file. The conversion tool will take over and bring over your version data given the available options in Visual Patch.

Where Do I Go Next?

The first section to read in the help file should be the Key Features of Visual Patch section. This will help point out all of the new and exciting features available. The next section to take a look at is the topic The Visual Patch Interface. This will provide a brief tour of the design environment so you are familiar with the terms used throughout the rest of the documentation. If you have some underlying questions about Visual Patch, take a look at the Frequently Asked Questions topic. It answers many common questions that developers have about the program.

If you are still not sure how things work in Visual Patch, the User’s Guide is an indispensable tool. It is a topical task based manual describing the features and use of the product. It was written in such a way that you can simply jump to the sections that you need to learn at that moment. You can access the User's Guide from the Help program menu.

If you are planning to recreate an existing patch, before attempting to translate your actions into Visual Patch scripts, you should read over the Scripting Guide. This guide will provide you with tips, tricks, and professional-level techniques you should use when writing your Visual Patch scripts.

Learn More: Indigo Rose Software - Visual Patch - Buy Now - Contact Us