Visual basic （VB）完整-全部-函数大全-函数速查手册
Visual basic （VB）完整-全部-函数大全-函数速查手册，300多页，非常全面，还有例子，有解释。http://www.xufeispace.comvb函数速查手册较。VbBinary Compare进行二进制的比较。VbTextCompare进行文字的比较。vbDatabase Compare用于 Microsoft access(仅限于Windows),进行以数据库所含信息为基础的比较。Compiler常数Visual Basic for Applications定义了一些不能与#f.Then.#lse指令起使用的常数。这些常数除了其范围是全局的;也就是说,除∫可在工程中刭处应用,在功能上与#f.Then#lse指令定义的常数相同在16位开发平台上,编译常数定义如下:常数值描述Win16True指出开发环境是16位。Win32 False指出开发环境不是32位。在32位开发平台上,编译常数定义如下:常数值描述Win16 False指出井发环境不是16位。Win32True指出开发环境是32位。Date常数可在代码中的任何地方用下列常数代替实际值:参数值firstdayofweek参数具有以下这些值:常数值描述http:/www.xutelspace.comvb函数速查手册vbUseSystem0使用 NLS API设置。suNday星期日(缺省)moNday123星期tuEsday星期二weDnesday 4星期三thUrsday5星期四frIday星期五saTurday7星期六firstdayofyear参数具有以下这些值:常数值描述ybUseSystem使用 NLS API设置。VbUseSystemDayOfWeek0使用系统设置中为星期的第一天指定的星期数VbFirstJan1由1月1日所在的那个星期开始(缺省)。vbFirstFourDays由新的一年中第一个至少有4天的星期开始。ybfirstFullWeek由一年中第一个完整的星期开始。返回值常数值措述suNday星期口moNday123星期一tuEsday星期二weDnesday4星期三ybIhursday星期四http://www.xufeispace.comvb函数速查手册frIday67星期五saTurday星期六日期格式常数仅当您的工程对包含这些常数定义的相应类型库有一个显式引用时,才可以使用这些常数常数值描述vbGeneralDate 0显示日期和/或时间。对于一个实数,显示日期和时间。如果没有小数部分,则仅显示日期。如果没有整数部分,则仅显示吋问。口期和时问的显示由系统设置值确定。vbLongDate用计算机区域设置值指定的长日期格式显示日期。ybShortDate用计算机区域设置值指定的短日期格式显示日期longtime234用计算机区域设置值指定的长时间格式显示时间。ybShorttime用计算机区域设置值指定的短时间格式显示时间。Dir、 GetAttr和 SetAttr常数可在代码中的任何地方用下列常数代替实际值:常数值描述abNormal正常的(Dir和 SetAttr的缺省值)reAdonly只读的hidden隐藏的vsYstem01248系统文件vbVolume卷标vbDirectory 16目录或文件夹vbArchive 32文件自上一次备份后已经改变http://www.xufeispace.comvb函数速查手册驱动器类型常数仅当您的工程对包含这些常数定义的相应类型库有一个显式引用时,才可以使用这些常数常数值描述Unknown0不能确定驱动器类型。Removable驱动器具有可删除介质。包括所有软盘驱动器和许多其它种类的存储设备Fixed驱动器具有固定介质(不可删除的)。包括可删除硬盘在内的所有使盘驱动器。Remot网络驱动器。包括在网终上任何地方都可以共享的驱动器。CDROM驱动器是一个CD-ROM。包括只读的 CD-ROM和可读写的CD-ROM。RAMDisk驱动器是本地计算机上的一块随机存取内存(RAM),它工作起来就象是磁盘驱动器一样。文件属性常数仅当您的工程对包含这些常数定义的相应类型库有一个显式引用时,才可以使用这些常数。常数值描述Normal普通文件。没有设置属性Readonlyy只读文件。属性是可读/写。Hidden隐藏文件。属性是可读/写。System248系统文件。属性是可读/写。Volume磁盘驱动器卷标。属性是只读。Directory16文件夹或目录。属性是只读。Archive32自上次备份后已经改变的文件。属性是可读/写。Alias64链接或快捷方式。属性是只读。http://www.xufeispace.comvb函数速查手册Compressed128压缩文件。属性是只读文件输入/输出常数仪当您的工程对包含这些常数定义的相应类型库有一个显式引用时,才可以使用这些常数。常数值描述ForReading打开文件用于只读操作。不能对文件进行写操作。ForWriting打开文件用于写操作。如果存在具有相同文件名的文件,文件原有的内容被矍盖。ForAppending8打开文件并向文件的结尾写入。Dir、 GetAttr和 Setattr常数?可在代码中的任何地方用下列常数代替实际值:常数值描述abnormal正常的(Dir和 Setattr的缺省值)vbReadOnly⊥只读的hiDden隐藏的vsYstem系统文件ybVolume卷标diRectory16目录或文件夹vbArchive 32文件白上一次备份后已经改变IMEStatus常数可在代码中的任何地方用下列常数代替实际值。口文国别的常数如下所示:http:/www.xutelspace.comvb函数速查手册常数值描述ybIMEModeNoControl没有安装IME(缺省)ybIMEModeOn01234打开IMEybIMEModeoff关闭IMEybIMEModeDisable无效的IMEvbIMEModehiragana完整宽度 Hiragana模式ybIMEModekatakana完整宽度 Katakana模式vbIMEModeKatakanaHalf 6半宽度 Katakana模式vbImEmodealphaFull7完整宽度 Alphanumeric模式vbImEmodealpha半宽度 Alphanumeric模式韩国地区的常数如下所示常数值描述vbIMEModealphaFull7完整宽度 Alphanumeric模式vbIMeModealpha8半宽度 Alphanumeric模式vbIMEModehangulfu119完整宽度 Hangul模式vbIMEModehangull(0半宽度 Hangul模式中文地区的常数值如下:常数值描述vbIMeModenocontrol0没有安装IME(缺省)vblMeModeonlIme打开vblMEModeorr2ime ofrKeycode常数http://www.xufeispace.comvb函数速查手册可在代码中的任何地方用下列常数代替实际值:常数值描述vbKeyLButton Ox1鼠标左键vbKeyRButton 0x2鼠标右键vbKey Cancel0x3CANCEL键vbKeyMButton 0x4鼠标中键vbKey BackBACKSPACE键vbKey tabTAB键bEy clearOxCCLEAR键vbKeyreturnENTER键vbKeyShift0x10SHIFT键vbKeyControl0xllCTRL键vbKeymenu0x12MENU键vbKeyPause0x13PAUSE键vbKeyCapital0x11CAPS LOCK键vbKeyescapeOxIDESC键vbKey Space0x20SPACEBAR键vbKeyPageUp 0x21PAGE UP键vbKeyPageDown 0x22PAGE DOWN键vbKey end0x23END键vbKeyHome0x24HOAE键vbKeyleft0x25LEFT ARROW键vbKeyUp0x26UP ARROW键vbKey Right0x27RIGHT ARROW键vbKey Down0x28DOWN ARROW键8http://www.xufeispace.comvb函数速查手册vbKeyselect0x29SELECT键vbKeyPrint0x2APRINT SCREEN键vbKeyExecute 0x2BEXECUTE键vbKeySnapshot 0x2CSNAPSHOT键vbKeyInsert 0x2DINSERT键vbKeyDeleteOX2EDELETE键vbKeyHelpOxfHELP键vbKeyNumlock 0x90NUML0CK键A至Z键与A-Z字母的 ASCII码相同常数值描述veReyAA键vbKeyB66B链vbEc67C键vbKeyD68D键keYe69E键vbKeyF70F键beYg71键vbKeyh72H键obEy I73vbKeyJ71vbKeyk75K键vbKeyLL键vbKeyM77M键vbKeyN78N键9
- 2020-12-02下载
- 积分：1
RTCM3.3协议全
全新RTCM3.3协议完整版RTCM STANDARD 10403.3DIFFERENTIAL GNSS(GLOBAL NAVIGATION SATELLITE SYSTEMS)SERVICES – VERSION 3DEVELOPED BYRTCM SPECIAL COMMITTEE NO. 104OCTOBER 7, 2016COPYRIGHT©2016 RTCMRadio Technical Commission for Maritime Services1611 N. Kent St., Suite 605Arlington, Virginia 22209-214RTCM Paper 141-2016-SC104-STD000ocRTCMco00c30RTCM 10403. 3, Differential GNSS Global Navigation Satellite Systems)Services- Version 3, October 7, 2016This standard (referred to as version 3 has been developed by rtCm special Committee 104 as a moreefficient alternative to the standards entitled rtcm recommended standards for diffe rentialRecommended Standards for Differential gNss Global Navigation Satellite Systems Service, Version 2.x(Current version is 2. 3, now designated as RTCM 10402. 3. Service providers and vendors represented onthe SC104 Committee wanted a new standard that would be more efficient, easy to use, and more easilyadaptable to new situations. The main complaint was that the version 2. x parity scheme, which useswords with 24 bits of data followed by 6 bits of parity, was wasteful of bandwidth. Another complaint wasthat the parity was not independent from word to word. Still another was that even with so many bitsdevoted to parity the actual integrity of the message was not as high as it should be. Plus, 30-bit wordsare awkward to handle. the new standard version 3 is intended to correct these weaknessesUnlike Version 2. x, this standard does not include tentative messages The messages in Version 3 haveundergone testing for validity and interoperability and are considered to be permanent. amendments tothe standard may change the meaning of reserved bits or provide additional clarifying text, but no changeswill be made in the data fields. Changes will require new messages to be developed. In addition to themessages described in the current standard the committee continues to develop new messages whichare described in separately published amendments and periodically gathered into a new edition of thestandard. RTCM 10403x for dgNSS services is proving useful in supporting highly accurate differentialand kinematic positioning as well as a wide range of navigation applications worldwideNote that Version 3 messages are not compatible with Version 2. x. Since many receivers have beendesigned and programmed for use with Version 2. x messages, rtCm is maintaining both standards0402 3 and 10403, 3 as" standardsVersion 3.0The initial edition consisted primarily of messages designed to support real-time kinematic (RTK)operations. The reason for this emphasis is that rtk operation involves broadcasting a lot of informationand thus benefits the most from an efficient data format. Version 3.0 provided messages that supportGPS and gloNaSs rTK operations including code and carrier phase observables antenna parametersand ancillary system parametersVersion 3. 1(RTCM Standard 10403.1:The next edition, Version 3. 1 (RTCM Standard 10403. 1), incorporated GPS Network Corrections, whichenable a mobile receiver to obtain accurate rtk information valid over a large area. In addition, new GPSand GLoNaSS messages provide orbital parameters to assist in rapid acquisition a Unicode text messageis also provided for the transmission of textual data. Finally a set of messages are reserved for vendorswho want to encapsulate proprietary data in their broadcasts the gps Network Corrections enable amobile receiver to obtain accurate rtk information valid over a large area. the network rtk correctioninformation provided to a rover can be considered as interpolated corrections between the referencestations in the rtk network this interpolation is not perfect and varies with the actual conditions of theatmosphere. A residual interpolation error has to be expected. With sufficient redundancy in the RtKnetwork, the network server process can provide an estimate for residual interpolation errors. Suchquality estimates may be used by the rover to optimize the performance of rtk solutions The values maybe considered by the rover as a priori estimates only with sufficient tracking data available the rovermight be able to judge residual geometric and ionospheric errors itselfVersion 3. 1. Amendment 1:Amendments 1 was an extensive addition that adds rtcm messages containing transformation data andinformation about Coordinate reference Systems. For rtCm data supporting a rtk service, coordinatesare measured within the itrf or a regional realization surve yors and other users of rtk services mustnormally present their results in the coordinates of local datums. Therefore, coordinate transformationsare necessary. by having RTCM messages that contain transformation data and information about theCoordinate reference systems the users of the rtk service can obtain their results in the desired datumwithout any manual operations. the rtk service providers can then ensure that current information forthe computation of the transformations is always used. the convenience of this method will promote theacceptance of rtK servicesVersion 3. 1. amendment 2:Amendment 2 added residual error messages to support the use of Non-Physical or Computed referenceStations in a network rtk environmentVersion 3. 1. amendment 3:Amendment 3 addressed differences in the way gnss receiver manufacturers have implemented carrierphase encoding of some Version 3 messages so that carrier phase observations are in phase for all carrierphases of a specific frequency i e. they correct for quarter cycle phase shifts. others retain the quartercycle offset between the carrier phase observations in the data. this amendment documents the waydifferent manufacturers have handled the phase shift issue and prescribes a uniform approach for futureproducts.∨ersiⅰon3.1, Amendment4:Amendment 4 added sections 3.5.13 on glONASS Network rtK Correction Messages and 3.5. 14 on FKPNetwork Rtk Correction Messages Related revisions were also made elsewhere in the document.Version 3. 1. amendment 5Amendment 5 added section 3. 5. 12 on State Space Representation related revisions are also madeelsewhere in the document, along with some editorial correctionsVersion 3. 2(RTCM Standard 10403.2)Version 3.2 consolidates Version 3. 1 and all five amendments into a new edition, and it adds MultipleSignal Messages (MSM)as well. the Multiple Signal Message (MSm)format generates receiverobservables in the same way for all included satellite systems. the messages include compact and fullmessages for Pseudorange, PhaseRange, Carrier to Noise Ratio (standard and high resolution), andPhaseRangeratea table near the beginning of the standard lists which messages were included in each separate editionand amendment, so it should not be necessary for users to refer to older versions. Multiple signalMessages are a generic format that will be followed for all GNSs systems. version 3 originally consisted ofmessages for GPS and GLONASS, each in their own format Now with the imminent addition of signals forBeiDou, Galileo, and QZSS, as well as new signals provided by modernized GPS and GloNASS satellitesthe need for a consistent generic format became evident. service providers and users are urged to migrateto the MsM messages to make it easier to accommodate new gNss services(See The RTCM Multiple Signal Messages: A New Step in GNSS Data Standardization")Another newmessage is the gloNaSS Bias Information message. This message provides information which is intendedto compensate for the first-order inter-frequency phase range biases introduced by the reference receivercode- phase biasVersion 3.2, Amendment 1:Added Galileo F/NAv Satellite Ephemeris Data(msg. 1045 )and Bds MSM(msgs. 1121-1127)Version 3.2 amendment 2Added qzss ephemeris(msg. 1044 )and QZss MSm (msgs. 1111-1117Version 3. 3(RTCM Standard 10403.3)This new edition adds Satellite-Based Augmentation System Multiple Signal Messages to previouslydopted messages for GPS, GLONASS, Galileo, and QzssA new ephemeris message has been added for BeiDou(BDS)and a new I/NAV ephemeris message hasbeen added for Galileo. The new edition also reserves 100 messages be used exclusively by sc104 fornew message developmentFinally, the new edition makes consolidates previous amendments and makes numerous editorialImprovementsNavstar GPS Service, Version 2. x. Service providers and vendors represented on the scco000c30z1O2co00c30Contentsco00c30
- 2020-06-27下载
- 积分：1
|
联系客服（QQ：3324461878）
