Here is a strategy that I used to migrate a project with my personal library packages from 8x to 9x: Copy your 8x project to new working directory Open the copied project <myProject>.vipprj with VIP 9x. You can do this with right-click from Windows Explorer after you copy the project. Do not build t...

Today I started migrating a project with several forms with menus in several of my 8x library packages and it's a bit more of a headache than I'd anticipated. I would suggest holding off on converting projects with many resource items (bitmaps, menus, etc.) because the conversion isn't straight forw...

VIP 7 & 8 had different task bar icons, so it was easy to tell them apart when using both versions at the same time. VIP 8 & 9 have the same icon -- could, perhaps, VIP 9 could have a different color on Saturn's rings? Maybe a different icon for the 32 and 64 bit IDE, too. This is probably the LEAST...

Aside from the issues I noted recently, I like 903 CE. It seems to compile faster and cleans up extraneous "open" statements. In general, conversion of 8x to 903 projects has been painless -- as Thomas suggested, just keep rebuilding until the IDE compiles smoothly.

Go forward with confidence!

Scenario: Create a bitmap named "myTestBitmap" Vip8 opens a dialog allowing one to specify the size and color depth and then creates a resource identifier idb_mytestbitmap . The default bitmap size is 32x32, but other sizes can be created, such as the 20x19 standard toolbar bitmaps. Vip9 the attribu...

VIP 903 raises an exception when running Optimal Set of Include Directives (OSID) , even on an empty package. VPI 8x optimizes the original copy of the same project without complaint. This happens on some projects, including virgin GUI or CONSOLE projects as generated by the IDE, but strangely not o...

I was testing the new VIP 9x installation and decided put together a tiny TicTacToe as a test project. Since it uses a number of common VIP constructs I decided to annotate it for new user users to browse to see how to do a few simple common tasks: How to handle getting a return value from dialog. G...

I found a file named ideStorage.DLL in the Exe folder of two of my very tiny Vip8x a testing project. One project is for testing code in console mode and the other for testing in GUI mode. The Project Settings directories are the default locations initialized when a new project is created. It is not...

I have had that occur with projects in which I have several code editor files open. It seems that the code actually is inserted but taskwindow.pro is not brought to the foreground. Sometimes there is a delay in response if the computer is busy doing other things. I got in the habit of clicking the [...

Here is a small point I noticed while working on this topic -- there is no code to retrieve legalTrademarks or originalFileName . constants % in fileVersion.CL companyNameApi = "CompanyName". fileVersionApi = "FileVersion". legalCopyrightApi = "LegalCopyright". fileDescriptionApi = "FileDescription"...

Now it is clear, thanks!

Got it!

It's simple to extend the File Version parameters in aboutDialog.pro, but I don't see how to access the File Flags Project Settings (i.e., "Debug", "Prerelease", ... ) or Product Version in versonControl.pro. These parameters are not defined in versionControl.i

Oh, now I understand!

"main.version" is use by the build system to create a version resource which is linked into your program. So "main.version" is a source file, the version resource is the corresponding target in your executable.

I'd want the resource, of course.

Ahhhhh ... thank you very much, Thomas! (2) Works better for me with the code modified as below, otherwise the properties are unassigned. Apparently the predicate doesn't fail or cause an exception if the file is missing. VersionData = vip\versionDataFactory::get(vip\versionData::interfaceVersion, @...

(1) Is there a built-in way to retrieve IDE variables (Tools > IDE Variables...) ? I am using this approach: run() :- % Existing IDE variable 'TestVar' set to "MyTestVariableAsString" console::write("\nStarting test ...\n"), RootKey = @"SOFTWARE\Prolog Development Center\Visual Prolog6\settings\tool...