Database Search
TechHome
 |
- 1028 Error using Go rather than Run Button
- Add Separator to the WinBatch Studio Toolbar
- Adding File Types to Studio
- Background Check
- Bitness of WinBatch Studio
- Block comment and uncomment code
- Change File Save-Open Default
- Change Studio Default File Open Path
- CLR Files for Other Extensions
- Code to Convert Hex to Decimal in Studio
- Custom Syntax Colorization
- DirGet returning Winbatch System Subdir
- Disable Studio Keyboard Shortcut
- Extended ASCII Cursor Placement Issue
- F12 in WinBatch Studio
- Foreign Language Search
- Hitting n Key Causes Strange Behavior
- Interactive Debug Mode and GoSub
- Keyboard Shortcuts
- Keyword Lookup not Working
- Manipulate open file or highlighted lines in WinBatch Studio
- Null characters found
- Pass Params in Winbatch Studio
- Pass Parms to WBT while in WB Studio
- Problem wRight wLeft and wGetChar
- Recreate WinBatch Studio Environment
- Regular Expression searches in WinBatch Studio
- Save As Dialog in WB Studio
- Shift-F1 stopped working
- Turn off WinBatch Tips
- Unable to Run WIL Extension
- Using Debug to See Contents of Array in Studio
- WinBatch Studio Choppy and Slow
- WinBatch Studio Window Missing
- Wrap lines to a specific length
- WSHELP.DLL - WSHELP.INI question
- WSINIT.DLL Process Stays When Studio Opens
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
Extended ASCII Cursor Placement Issue
Keywords: Extended ASCII Cursor Caret Placement
Question:
The third party P6CryptAES extender and its output is having an issue in WinBatch Studio. I don't think its really a problem with the extender. I think it's a problem with the extended ASCII characters in the encrypted strings.The problem I experienced was with this line:
vstrRequiredKeywords = "SAPwd|p³ý’À ÙèP³´ xþ”^g5ƒvG+àa":@TAB:"ConfigFile|''"Once I pasted in the encrypted string, I had a devil of a time editing anything after the string. For instance, I forgot to put a colon between @TAB and "ConfigFile. To place the colon where it belonged, I had to place my cursor between the double quote and C in "ConfigFile, otherwise it would end up in the middle of the AB in @TAB.
Answer:
The problem is caused by the ASCII control character 01 (SOH) and not one of the extended characters. For whatever reason this value can cause font rendering to get a bit out of sync.In some instances this problem can be fixed by performing a little registry hacking. You can set a value that causes WBS to prompt you to replace control character values like SOH with ASCII 255 as it loads files.
However, this will not fix the issue when you paste a value into the editor nor does it help if you actually need the value to be present in a string constant in a script. In such cases, you can just use Num2Char(1) and the concatenation operator to embed the character in the string, once you id its location in your string constant.
In case you are curious, you can use Regedit to go to 'HKEY_CURRENT_USER\Software\Wilson WindowWare\WinBatch Studio\Settings\Main Window', create a DWORD value named 'FilterControlChars' and set it to 1. The next time you start WBS you will receive a prompt to replace each control character with character 255 as the file loads. Of course this could be done with WinBatch "RegSetDword" function, as well. Again, this will not fix your specific problem, since you apparently need the character presence in your script.
Article ID: W18451
Filename: Extended ASCII Cursor Placement Issue.txt
File Created: 2012:07:16:08:26:44
Last Updated: 2012:07:16:08:26:44