IMG Home PageIMG ProductsProduct DownloadsOrdering InformationTechnical Support and Frequently Asked QuestionsDeveloper's Corner and UtilitiesAbout IMG
CustomersIMG ResellersMedia InformationIMG Events / Trade ShowsUseful LinksIMG Contact InformationIMG Information / Policies

IMG KnowledgeBase & Frequently Asked Questions

IMG Logo



Search FAQ's

Keyword Keyword Search Help
Category Type Product Version

IL2010120645
The license file used in retail versions of My-T-Soft 2.10 will not license after July 19, 2010. Even if you have a valid Certificate of Authenticity for the software, if your system date is current (past July 19, 2010) the license authentication algorithm will not license. Refer to the options below for solutions to overcome this limitation.

The license algorithm uses a date embedded in the default (installation) license file. Build-A-Board 2.20 has been released and it is recommended that users upgrade, or refer to their annual maintenance options (or contact IMG Customer Service regarding Maintenance options). However due to standardization, validation issues, and the stability of the software, some customers require the use of 2.10 version.

Category: LicensingType: Information Product: Build-A-BoardVersion: 2.10



IU2007120565
How do I get Build-A-Board run-time My-T-Soft 2.10 (MYTSOFT.EXE 2.10) for XP working in Windows Vista?

When running the 95-XP run-time in Vista, you will get an "Improper Windows Version" message. You can enable the built-in compatibility mode for the software. For MYTSOFT.EXE, MACROBAT.EXE, LICENSE.EXE you can right-click, select properties, select the Compatibility tab and enable the compatibility mode for operation as Windows XP SP2. As an alternate workaround, you can download and overwrite the existing IMGVERS.DLL with this updated IMGVERS.DLL for Vista. (MD5: 4B235A355DAAF9E204F626EDB27175A9) Please note that this simply reports that Vista is the same as 2000/XP - this allows the software to run without the message, but no other accommodations for Vista (e.g. User Account Control/enhanced security/software manifests, etc.) occur.
Category: UsingType: Information Product: Build-A-BoardVersion: 2.10



IU2008120580
How do I install and run Build-A-Board 2.10 on Windows Vista?

Be sure to use the MSI (alternate download) install, e.g. BAB210.MSI

You must be an Administrator to install Build-A-Board. If Limited User, and User Account Control (UAC) is on, then SETUP.EXE should escalate and ask for an Administrator password. If UAC is Off, then it will not install. You must logon as Administrator to install Build-A-Board.

If using the 64-bit version, replace the \Program Files with \Program Files (x86) in the instructions below

Once installed, you must set compatibility to run, set permissions for licensing and operation, and move SOURCE and TARGET folder to a Public location

NOTE: Do not do this step for 64-bit Vista, i.e. do not set compatibility Use Windows Explorer, go into \Program Files\Build-A-Board\BIN, then Select BABTC.EXE, and Right-Click | select Properties, then select Compatibility Tab and select:
Run this program in compatibility mode for:
Windows XP (Service Pack 2)
Now do the same operations for BUILDER.EXE and LICENSE.EXE.

Now you must change Permissions - Under Program Files, select the Build-A-Board folder, and right-click | Properties. Under security tab, click on the Edit button below the users/groups list. It will ask for Administrator password. Then select the Users group, and give full control to the Build-A-Board folder. Then OK, OK.

At this point, you may update the IMGVERS.DLL, indicated at this help link - Updating IMGVERS.DLL for run-time MYTSOFT.EXE 2.10 to run in Vista. This file can be updated in \Program Files\Build-A-Board\BIN, \Program Files\Build-A-Board\BIN\MSWIN, and \Program Files\Build-A-Board\BIN\TEST.

Now you will be able to License Build-A-Board (License starting with BAB210??????). After Compatibility and permissions set, run \Program Files\Build-A-Board\BIN\LICENSE.EXE, and enter license code. You must be able to save to the file \Program Files\Build-A-Board\BIN\LICENSE.LIC, and the Permission step above should allow this. You can verify you have sufficient permissions by opening the LICENSE.LIC in Notepad, and enter a line, and save it, then re-open - the changes should be visible. Clear the line, and save it back in its original form, then run LICENSE.EXE

Working folders - For best results, move the SOURCE and TARGET folders to a public place (or your local user folders), and update Build-A-Board settings to reflect this change.

In Explorer, open another window and go into Users then into Public then into Public Documents, then create a folder called Build-A-Board. Now copy SOURCE and TARGET folders from \Program Files\Build-A-Board to \Users\Public\Documents\Build-A-Board

So now you should have 2 folders at:
\Users\Public\Documents\Build-A-Board\SOURCE and
\Users\Public\Documents\Build-A-Board\TARGET

Now run the Builder - Start Menu | All Programs | Build-a-Board | Build-A-Board Builder. Now select Edit menu | Properties, and click on the Global Settings Tab. Click on the ... button next to the source folder and select Public | Public Documents | Build-A-Board | SOURCE, and it should show C:\Users\Public\Documents\Build-A-Board\SOURCE for the Source.

Click on the ... button next to the Target folder and select Public | Public Documents | Build-A-Board | TARGET, and it should show C:\Users\Public\Documents\Build-A-Board\TARGET for the Target. Now click OK.

Once Build-A-Board is licensed by an Administrator, and the folders are moved to an area without limitations (the Program Files location is not available for storing data files in Windows Vista), you will be able to save projects, and operate Build-A-Board as a normal user - refer to the new location created above for Source files, and for Target files for built projects.

For more information about Windows Vista Click Here.

Category: UsingType: Information Product: Build-A-BoardVersion: 2.10



IU2009120614
How do I get Build-A-Board run-time My-T-Soft 2.10 (MYTSOFT.EXE 2.10) for XP working in Windows 7?

When running the 95-XP run-time in 7, you will get an "Improper Windows Version" message. You can enable the built-in compatibility mode for the software. For MYTSOFT.EXE, MACROBAT.EXE, LICENSE.EXE you can right-click, select properties, select the Compatibility tab and enable the compatibility mode for operation as Windows XP SP3. As an alternate workaround, you can download and overwrite the existing IMGVERS.DLL with this updated IMGVERS.DLL for Windows 7. (MD5: 6EF6AD0215549E697B8A56B5C5B1C266) Please note that this simply reports that 7 is the same as 2000/XP - this allows the software to run without the message, but no other accommodations for 7 (e.g. User Account Control/enhanced security/software manifests, etc.) occur.
Category: UsingType: Information Product: Build-A-BoardVersion: 2.10



IU2009120615
How do I install and run Build-A-Board 2.10 on Windows 7?

You must be an Administrator to install Build-A-Board. If Limited User, and User Account Control (UAC) is on, then SETUP.EXE should escalate and ask for an Administrator password. If UAC is Off, then it will not install. You must logon as Administrator to install Build-A-Board.

Once installed, you must set compatibility to run, set permissions for licensing and operation, and move SOURCE and TARGET folder to a Public location

After install you must change Permissions - Under Program Files, select the Build-A-Board folder, and right-click | Properties. Under security tab, click on the Edit button below the users/groups list. It will ask for Administrator password. Then select the Users group, and give full control to the Build-A-Board folder. Then OK, OK.

At this point, you should update the IMGVERS.DLL, indicated at this help link - Updating IMGVERS.DLL for run-time MYTSOFT.EXE 2.10 to run in 7. This file can be updated in \Program Files\Build-A-Board\BIN, \Program Files\Build-A-Board\BIN\MSWIN, and \Program Files\Build-A-Board\BIN\TEST.

Now you will be able to License Build-A-Board (License starting with BAB210??????). After Compatibility and permissions set, run \Program Files\Build-A-Board\BIN\LICENSE.EXE, and enter license code. You must be able to save to the file \Program Files\Build-A-Board\BIN\LICENSE.LIC, and the Permission step above should allow this. You can verify you have sufficient permissions by opening the LICENSE.LIC in Notepad, and enter a line, and save it, then re-open - the changes should be visible. Clear the line, and save it back in its original form, then run LICENSE.EXE

Working folders - For best results, move the SOURCE and TARGET folders to a public place (or your local user folders), and update Build-A-Board settings to reflect this change.

In Explorer, open another window and go into Users then into Public then into Public Documents, then create a folder called Build-A-Board. Now copy SOURCE and TARGET folders from \Program Files\Build-A-Board to \Users\Public\Documents\Build-A-Board

So now you should have 2 folders at:
\Users\Public\Documents\Build-A-Board\SOURCE and
\Users\Public\Documents\Build-A-Board\TARGET

Now run the Builder - Start Menu | All Programs | Build-a-Board | Build-A-Board Builder. Now select Edit menu | Properties, and click on the Global Settings Tab. Click on the ... button next to the source folder and select Public | Public Documents | Build-A-Board | SOURCE, and it should show C:\Users\Public\Documents\Build-A-Board\SOURCE for the Source.

Click on the ... button next to the Target folder and select Public | Public Documents | Build-A-Board | TARGET, and it should show C:\Users\Public\Documents\Build-A-Board\TARGET for the Target. Now click OK.

Once Build-A-Board is licensed by an Administrator, and the folders are moved to an area without limitations (the Program Files location is not available for storing data files in Windows 7), you will be able to save projects, and operate Build-A-Board as a normal user - refer to the new location created above for Source files, and for Target files for built projects.

For more information about Windows 7 Click Here.

Category: UsingType: Information Product: Build-A-BoardVersion: 2.10



PI2005120129
Downloaded File / CD Install Hangs
Install completes, but Program Group Shortcuts do not point to valid files


Original ID: PI223703
Category: InstallingType: Problem/Resolution Product: Build-A-BoardVersion: 2.10



PI2009120607
I have installed the BAB210.MSI and am running Build-A-Board, but after I successfully build a board and try to run it, nothing happens.

The 2.10 MSI install does not establish the registry entries for the Target and Source locations. To do this, after install, run the Build-A-Board builder, go to Edit | Properties, click on the Global Settings tab, then make some modification to the settings so the Apply button is enabled (e.g. click on the . . . Button, then click on Cancel, or click on the Single File Keyboard Layout button), then click Apply. This will save the settings for the Source, Target and Bin folders.
Category: InstallingType: Problem/Resolution Product: Build-A-BoardVersion: 2.10



PU2005120231
Problems typing


Original ID: PU225145
Category: UsingType: Problem/Resolution Product: Build-A-BoardVersion: 2.10



PU2005120232
Unable to open projects
Unable to build projects (Builder hangs)
BABTC.EXE processes do not complete (Task Manager)
Build-A-Board Text Compiler Errors (Windows visible indicating compile problems)

  • Resolution: Update BABTC.EXE to version 2.11
  • This only affects a small number of systems - see technical notes below.
  • Since 2005, this update has been rolled into the available 2.10 versions.

  • Original ID: PU225146
    Category: UsingType: Problem/Resolution Product: Build-A-BoardVersion: 2.10



    PU2005120233
    Caps Lock / Shift state operation problems
    Stuck keys (dragging off board while button down)
    Transparency (Requires Windows 2000 or later)

    Resolution: Update MYTSOFT.EXE to version 2.16
  • IMPORTANT: This is only a direct replacement to the Build-A-Board run-time component MYTSOFT.EXE. This may not be used in Windows CE, as MTS2.EXE, or MYTSOFT2.EXE!

  • Original ID: PU225147
    Category: UsingType: Problem/Resolution Product: Build-A-BoardVersion: 2.10



    PU2005120234

    Character keys do not generate characters in application
    I need support for a different processor
    My application is topmost and above the My-T-Soft window
    I need an "L" layout or a framed layout
    I need the Alt combination keys for my application and wan't user control vs. pre-built macros

    2.17 Notes
    Please refer to the above regarding the replacement/updating of the MYTSOFT.EXE appropriate for your system. For the following processors, you can download the 2.17 version, which includes the following options:

    The following processors are supported with the 2.17 versions
    Note: If your processor is supported, the 2.17 is preferred to the 2.14 version


    Original ID: PU225148
    Category: UsingType: Problem/Resolution Product: Build-A-BoardVersion: 2.10



    PU2005120235
    30 character limit is too short for the macro I need.


    Original ID: PU225149
    Category: UsingType: Problem/Resolution Product: Build-A-BoardVersion: 2.10



    PU2005120236
    Trying to Pause macro while typing, or need other input / mouse capabilities.


    Original ID: PU225150
    Category: UsingType: Problem/Resolution Product: Build-A-BoardVersion: 2.10



    PU2005120237
    Run Time error (indicated as KEYBOARD.KBF)


    Original ID: PU225151
    Category: UsingType: Problem/Resolution Product: Build-A-BoardVersion: 2.10



    PU2005120238
    Need X86 Processor Support, Windows CE 3


    Original ID: PU225152
    Category: UsingType: Problem/Resolution Product: Build-A-BoardVersion: 2.10



    PU2005120239
    Current Project replaced by Older Project


    Original ID: PU225153
    Category: UsingType: Problem/Resolution Product: Build-A-BoardVersion: 2.10



    PU2005120240
    Not all characters in Build-A-Macro portion operate (or generates an incorrect keystroke).


    Original ID: PU225154
    Category: UsingType: Problem/Resolution Product: Build-A-BoardVersion: 2.10



    PU2006120495
    Working with Remote Desktop Connection, Shift-State acts inconsistent, or lowercase/uppercase characters not sent as expected (especially longer sequences of characters). Works fine in Terminal Server Client to the remote machine, or locally.

    Category: UsingType: Problem/Resolution Product: Build-A-BoardVersion: 2.10



    PU2007120523
    I just moved my Run-Time Win32 My-T-Soft 2.10 to a new machine, have transferred the license, and when I run MYTSOFT.EXE, I don't see anything - What should I do?

    Category: UsingType: Problem/Resolution Product: Build-A-BoardVersion: 2.10



    PU2010120654
    Default hand cursor is visible when entering passwords / or in use in secure location
    My-T-Soft window falls behind task bar or other windows

    My-T-Soft with blank cursor

    Use updated MYTSOFT.exe with default cursor as "blank" or "null" cursor - this will display no cursor when mouse pointer is over the keyboard window (My-T-Soft window).

    Download MYTSOFT.exe with blank/null cursor as M217W32.ZIP (MD5: 0AD220CFFB98B23687499D515AF8B751) (26KB) (Unzips as MYTSOFT.exe)

    For installation notes, and additional capabilities in this update, refer to this item: PU2005120233

    Notes: The version is tagged as 2.17, but will work with 2.10 licenses - this is a direct replacement for the MYTSOFT.exe in Build-A-Board 2.10 (or Build-A-Board run-time Win32) - it should not be used for any other purpose. This is essentially similar to the 2.16 update (see link above), except it uses the blank cursor, and has a version of 2.17.

    My-T-Soft with forced topmost

    Use updated MYTSOFT.exe with a forced topmost action so My-T-Soft window will position above other topmost windows.

    Download MYTSOFT.exe with blank/null cursor as M219W32.ZIP (MD5: A987A44B790F5CED834ADDEEC8B86132) (30KB) (Unzips as MYTSOFT.exe)

    For installation notes, and additional capabilities in this update, refer to this item: PU2005120233

    Notes: The version is tagged as 2.19, but will work with 2.10 licenses - this is a direct replacement for the MYTSOFT.exe in Build-A-Board 2.10 (or Build-A-Board run-time Win32) - it should not be used for any other purpose. This is essentially similar to the 2.16 update (see link above), except it has the forced topmost code, and has a version of 2.19.

    By default, the topmost attribute is used when creating the My-T-Soft window, and if My-T-Soft is launched after other topmost windows, will be the topmost window. However, if other windows position themselves as topmost, My-T-Soft may fall behind. This build uses a timer and sets itself as topmost, which will overcome this type of normal action. However, if another window forces itself to be topmost, you may get a flickering type action, as the windows will constantly swap topmost position. Because of the cooperative type of environment in use, this solution may not be ideal for all situations.

    Category: UsingType: Problem/Resolution Product: Build-A-BoardVersion: 2.10



    QD2006120471
    I tried running Mytsoft.exe .kbf from a command line while a different keyboard is active and the software does not switch to the new configuration. I am running the exe from within the directory containing the .kbf file. Any suggestions?

    This approach works with Build-A-Board layouts only when starting MYTSOFT.EXE - it does not allow you to change the layout from the already running process.

    In MYTSOFT.EXE 2.10, you can select different layouts via a button using the CMD:NKBF (New KBF) if you want the user to switch on-the-fly. If you want to externally change the displayed layout on-the-fly, you need to do some dancing. It will make a bit more sense if I describe first what is going on, and then the details.

    Assume there is a keyboard.kbf, and a mylayout.kbf.

    In the code, everything is triggered off of an action (typically represented by a button press & the actual action is then generated by Build-A-Board). So the built-in way to change the layout is to execute the [CMD:NKBF=mylayout.kbf]. This can be put behind a button & this command (macro) placed into the Key Action in Build-A-Board. The trick is to generate this command externally. The TYPEFILE.EXE (see Tech Item PU2005120235, keystrokes longer than 30 characters) allows an external command to be triggered. The naming is unfortunate, since it can do more than just type a file. The salient point is that it can trigger a macro/command just as if the Key Action generated it. So the dance is to create a file with the [CMD:NKBF...] in it, save it as a file, then use TYPEFILE.EXE to execute from an external program - this will allow the layouts to change on the fly externally.

    So here are the details. Download the TYPEFILE.EXE from our website (see link above). Place this & the mylayout.kbf in MSWIN folder of the project you are working with. Use a windowed command prompt to test, then once you have the syntax down, integrate it with your application.

    Create 2 simple text files with the commands embedded in it (e.g. NOTEPAD or EDIT or COPY CON MYLAYOUT.KMF) Note I am using KMF for Keyboard Macro File, and the layout is KBF for KeyBoard File

    Category: Integrating(Developing)Type: Question/Answer Product: Build-A-BoardVersion: 2.10



    QD2007120547
    I have a Build-A-Board KBF file used on a system and I want to modify it, but I can't find the source files. How can I work with this keyboard layout and modify it?

    You will want to download the KBFDUMP Utility, that can extract the data from the KBF file, and optionally, extract the data and re-create source files, usable by the Build-A-Board builder.

    IMPORTANT - the following is ONLY for 2.10 KBF files

    Download KBFDUMP.EXE command-line utility KBFDUMP.EXE (56K) (MD5: 6FD0E051602E06DDD7A50043CBEA3E83)
    Download KBFDUMP.EXE command-line utility as ZIP file: KBFDUMP.ZIP (22K) (MD5: FAAC0E95FF3CCB37CB3FDAA165075F75)

    IMPORTANT - the following is ONLY for 2.20 KBF files (see specific instructions below)

    Download KBFDUMP.EXE (beta) command-line utility as ZIP file: KBFDUMP220.ZIP (22K) (MD5: 099D1FB026F9DA6630A76DD94B6D83C1)


    KBFDUMP.EXE for 2.10 files Usage Notes:

    Usage: KBFDUMP [KBFFileName]
    (If no file name specified, KEYBOARD.KBF is used)
    To extract SOURCE projects from KBF files, use "-extract"
    Usage: KBFDUMP -extract [KBFFileName]
    (If no file name specified, KEYBOARD.KBF is used)
    Extracted project files will be saved to ExtractedKBFProject[#]
    These source files will be located in Build-A-Board\Source folder


    KBFDUMP.EXE for 2.20 files Usage Notes:

    Usage: KBFDUMP [KBFFileName]
    (If no file name specified, KEYBOARD.KBF is used)
    To extract SOURCE projects from KBF files, use "-extract"
    Usage: KBFDUMP -extract [KBFFileName]
    (If no file name specified, KEYBOARD.KBF is used)
    Extracted project files will be saved to ExtractedKBFProject[#]
    These source files will be located in Build-A-Board\Source folder


    Extracting File from KBF (Linux command line example)

    In this example, we will use dd (Linux command line utility) to extract IMG00000.PNG from an existing KBF.
    If you use kbfdump FILENAME.KBF[Enter] you will get a listing of headers, files, and offsets. Record the Startoffset from KBF header (1102), and the Startoffset from the file interested in (57534), as well as the file size (524138) - relevant output results below:
    ===========
    KBF HEADER
    ===========
    BYTE Sig[2] = M+
    BYTE Ver[3] = 220
    DWORD Startoffset = 1102 | 0x044E
    BYTE Level = 2 | 0x0002
    ... ...
    ... ...
    ... ...
    ======================
    KBF Files/Offsets 44
    ======================
    BYTE FileName[13] = IMG00000.PNG
    DWORD Startoffset = 57534 | 0xE0BE
    DWORD Length = 524138 | 0x7FF6A

    Now, at Linux command prompt in directory containing KBF file:
    dd if=FILENAME.KBF of=WANTEDIMG.PNG bs=1 count=524138 skip=58636[Enter]
    Explanation:


    IMPORTANT NOTES

    Category: Integrating(Developing)Type: Question/Answer Product: Build-A-BoardVersion: 2.10



    QU2006120472

    One thing they would like to change is that when the keyboard is minimized (I have a "Min" button), they would like this to end up on the Taskbar. Currently, the keyboard minimizes to a very small icon on the System Tray. Since we are using a touchscreen, it is very hard to "double touch" the small icon in the System Tray in order to reopen the keyboard.

    Can I specify something else that will force the keyboard to minimize to the Taskbar? The code behind my "Min" button is your standard Minimize command ( [CMD: MINIMIZE]).


    -or-

    I want My-T-Soft for Build-A-Board to minimize like the original (pre 2.00) My-T-Soft - How do I do this?


    Build a single button layout & use the CMD:NKBF, rather than the CMD:MINIMIZE - there is no regular icon available (part of this is that the keyboard window does not have a caption bar, it is not a normal application window). Here is a quick overview of what would be involved:

    You will need a new project, e.g. BUTTON. For example, lets say your current project is NUM. Instead of CMD:MINIMIZE, use CMD:NKBF=BUTTON.KBF, then save & build your NUM project. Now create a new project, and call it BUTTON. Create a single button, and set its action to CMD:NKBF=NUM.KBF - label / size / position as desired. Now save & Build BUTTON. From \Program Files\Build-A-Board\Target\BUTTON\MSWIN copy BUTTON.KBF to the \Program Files\Build-A-Board\Target\NUM\MSWIN folder. (In the end, make sure BOTH KBF FILES (NUM.KBF / BUTTON.KBF) are in the same folder as MYTSOFT.EXE. Now when you run the keyboard, and hit "minimize" it will go to the layout as managed in BUTTON. When the single button in BUTTON is pressed, it will reopen the NUM layout.

    The key thing to manipulating Build-A-Board is to realize each display presented to the user is just another layout (which can have 1 or (typically) more buttons). By using a single button layout, the "minimize to button" result can be achieved using the built-in "New KBF" command, e.g. CMD:NKBF=???

    Category: UsingType: Question/Answer Product: Build-A-BoardVersion: 2.10



    QU2006120489
    Is there a way to create a audible click when a key is pressed (run a short sound file)?

    You can assign a sound to run with the [CMD:SND=???.wav] entry in the key action (uses the Windows API PlaySound internally). If used at the end of the key action, you will still get the keystrokes, along with the wave sound playback.
    For example, in Key Action: Test[CMD:SND=click.WAV]
    This will type Test & play the CLICK.WAV, (The click can be any wave file, or you could copy the file from our My-T-Soft software - the current version includes a KEYCLICK.WAV file in the Sounds folder in the installation folder - you would have to download & install, get the file, then un-install).
    Notes:
    There is a 31 character limitation in the action, so naming it to c.wav, will still work, and save 4 characters in the action.
    It needs to be the last entry in the key action, as the commands are treated special, and no further interpretation of the action will be performed once a CMD is processed.
    The appropriate wave file needs to be in the same folder as MYTSOFT.EXE. In Build-A-Board, the "test" version is \Program Files\Build-A-Board\TARGET\[Your Project Name]\, and for a standard windows target, it is \Program Files\Build-A-Board\TARGET\[Your Project Name]\MSWIN\ - you manually need to copy the wave file(s) into the target folders.
    Category: UsingType: Question/Answer Product: Build-A-BoardVersion: 2.10



    QU2007120531

    I am trying to make a keyboard that will issue the following commands in a 5250 AS/400 environment. I read a knowledgebase article that says the following:

    How do I tell Build-A-Board to use the left or right control keys and how do I tell it to use a + from the num pad? Also, I need to do a Reset. What key should be used for that?


    You should refer to the notes & reference material in Build-A-Board Help | My-T-Soft Macrobat

    The %%s162 will generate the scan code for the left control and the %%s163 will be the right control. It is possible you will need an extended attribute for the right control, which would be %%e163. Using our tool KEYBOARD\KeyWatch.exe (in the developer's kit - see C:\Program Files\Build-A-Board\SDK) you can watch what the physical keyboard generates & see what the virtual keys generate for comparison. The latching keys (Shift/Ctrl/Alt) can be problematic in that they can need handling & support from the virtual keyboard software MYTSOFT.EXE. For example, the Shift key needs to "latch" the shift state down, e.g. press the shift key & release. Press a letter & release. You will get an unshifted character. On the virtual keyboard, due to the pointing device, nothing "latches" the key (i.e. you can't press 2 keys at once with 1 pointing device). If the keys are discrete & the application software is triggered by Windows virtual key codes, then the existing implementation will work. If software monitors the physical keyboard, or requires latching capabilities, then there may be issues. If so, please let us know & we will try to assist further.

    Category: UsingType: Question/Answer Product: Build-A-BoardVersion: 2.10



    QU2007120568

    When I used Build-A-Board to make a very simple keyboard with just those five operations, the Up, Down, PgUp, and PgDn all worked. However the Ctrl-G did not open the channel guide - it did nothing that I could see. I added some more keys to try alternatives and tried these action codes:
    [Ctrl-Down]G[Ctrl-Up]
    ~~G
    Why won't these work?


    The issue is pretty simple - Ctrl-Shift-g is not the same as Ctrl-g. There are mentions in various places about lowercase being preferred, but this problem is inherent in computers doing what they are told. To generate a capital letter from a physical keyboard, the shift key needs to be held down, and when the macro handling part of the software sees an uppercase character it faithfully generates the sequence of keystrokes necessary to create the letter. When doing straight text, e.g. "Hello World" - ",Shift-h,e,l,l,o, Shift-w,o,r,l,d" this works just fine, all is well, and everyone is happy. When trying to use control/alt type sequences, this can sometimes cause problems, as the extra shift state causes the underlying application to treat it differently. To get a keystroke for g, and g alone, you must specify "g" in the macro, NOT G. G generates a [Shift-Down]g[Shift-Up] macro sequence. Therefore [Ctrl-down]G[Ctrl-Up] generates [Ctrl-down][Shift-Down]g[Shift-Up][Ctrl-Up], not the [Ctrl-Down]g[Ctrl-Up] sequence you want.

    Some apps work fine in either upper or lower case, but when the app doesn't, you must stick with the lowercase letter in the macro.

    Category: UsingType: Question/Answer Product: Build-A-BoardVersion: 2.10



    QU2009120608
    I want a key to select a field on my application. How can I do that?

    In general, and in most cases, leaving the user in charge of the keyboard focus is recommended. In cases where you have a fixed screen resolution/fixed situation, and want to move and select, using a "fake" mouse click can accomplish this goal. We have modified our mouse click utilities (available in the IMG Developer's Kit) to add some flexibility. You can download MSCLK.EXE here:
    Download MSCLK.ZIP (MSCLK.EXE/MSCLK.INI) (17K) (MD5: B0FA955741C130EA2E4A5F13768070D4)
    There are various notes in MSCLK.INI (or you can run "MSCLK.EXE HELP").

    Here are implementation notes for integrating with Build-A-Board.
    You will want to assign an EXEC command function to the appropriately labeled key in Build-A-Board, e.g. [CMD:EXEC=MSCLK.EXE]. If the file MSCLK.INI exists, this will generate the action used by MSCLK.EXE. The files MSCLK.EXE/MSCLK.INI MUST be in the same folder as MYTSOFT.EXE when running. If developing, you will need to place these files in the \Program Files\Build-A-Board\TARGET\[Your Project] and \Program Files\Build-A-Board\TARGET\[Your Project]\MSWIN folders.

    Category: UsingType: Question/Answer Product: Build-A-BoardVersion: 2.10



    QU2010120622
    Why does Alt-Tab only switch between the top two windows? How can I go deeper?

    Because the full Alt-Tab key sequence releases the Alt state, the Window Manager "resets" the window Z order, and so the next Alt-Tab just switches to the next window in-line, pushing the current topmost window down. This results in each event switching correctly, just not as expected, or desired. You can duplicate this with a physical keyboard by simply releasing the keyboard after a window switch - only the top 2 windows will switch. You should try Shift-Alt-Tab, which will switch to the bottom window, and switch among all the windows. Because of the key action text limit in 2.10, use the "@@[Tab]" macro for Alt-Tab and "[Shift-Down]@@[Tab][Shift-Up]" macro for Shift-Alt-Tab without having to use TYPEFILE.
    Category: UsingType: Question/Answer Product: Build-A-BoardVersion: 2.10

    Notes:



    IMG Home PageIMG ProductsProduct DownloadsOrdering InformationTechnical Support and Frequently Asked QuestionsDeveloper's Corner and UtilitiesAbout IMG
    CustomersIMG ResellersMedia InformationIMG Events / Trade ShowsUseful LinksIMG Contact InformationIMG Information / Policies


    As seen in ...

    Yahoo!finance