Answers inline... >Sorry to repeat things already answered, but I did try searches first at >least! > >Working with the demo/eval tools right now. > >1. Any pointers on or links to general guidance on when to use AddObject >vs. CreateObject()? AddObject appears to be related to *controls* and >not plain COM classes, but that seems overly simplistic so I'm probably wrong.
You're right. AddObject lets you create visual controls which have events that go back to your program. CreateObject is more limited. >2. Current script runtime: has the CreateObject()-related memory leak >ever been addressed? Is it truly related to using Set X = Nothing or a >general problem with object disposal (i.e. including object references >going out of scope)? CreateObject is built into VBScript. We always use AddObject - we have not investigated CreateObject. >3. Anyone have sample code or a wrapper component that will open a COM >IStream on a file and return it as an object? I'd need to close the >IStream and dispose of it cleanly (no leaks) as well. The SFStream object does this: <http://www.newobjects.com/pages/ndl/StoragesAndFiles/SFStream.htm> It's included in the NewObjectsPack1 control which ships with NS Basic. >4. Anyone have anything "lighter" than MGCEWin32 for basic clipboard >access? At least Unicode text but preferably files (from Explorer) as well. I would use the Clipboard control in the Win32API control: <http://www.nsbasic.com/ce/info/technotes/TN16.htm> MGCEWin32 is no longer supported. It might be possible to do this using API functions as well. <http://www.nsbasic.com/ce/info/technotes/TN26.htm> >5. Can NS Basic/CE accept vbs "modules" (.bas) obfuscated as .vbe using >the MS Script Encoder (SCRENC.EXE)? Also, what are .cod modules? Yes, >I realize "compiled" programs obfuscate my code and I realize .vbe is >weak obfuscation. .COD modules are normal text files with code in them. They are simply merged into the main module at runtime. If you want your code encrypted, using the Encrypt option in Project Properties. .vbe is not supported. >6. Basic.WM.cab is only needed to deploy the IDE to the device... is >that correct? TechNote 23 seems to be woefully out of date, I have no >BASIC.PocketPC4_ARM.cab in my dev system's folder indicated in that >article. When/how do I use the "Extra Feature Installers" (menu in >desktop dev. IDE)? You're right - Tech Note 23 is due for an overhaul. Version 8 of NS Basic automatically builds an installer for your program, so you no longer have to mess with things like BASIC.PocketPC4_ARM.cab. >7. I end up with sxehhhh.tmp processes on the desktop that I have to >kill off using Task manager. I assume this relates to aborted/pending >deployment attempts? Looks like it. >8. Is it practical and safe to detect available device display >resolution and resize Forms (moving/resizing controls) at runtime? Is >it practical to create programs that can sense and work properly on both >WinMobile Std and Pro (i.e. touchscreen and no touchscreen)? Yes, it's reasonable to resize at runtime based on the actual screen size. This kind of thing is done a lot. NS Basic does not support non-touchscreen devices. They gave pretty much died out in the marketplace. >Thanks for any input, please feel free to direct me to TechNotes (same >ones *again* if required). Answer any you can, I know I have quite a >list here. > > > >------------------------------------ > >Yahoo! Groups Links > > > -- You received this message because you are subscribed to the Google Groups "nsb-ce" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nsb-ce?hl=en.
