עבור לתוכן
Magic DevHub

yacovweiss

Members
  • הודעות פעילות

    16
  • הצטרפות

  • ביקר לאחרונה

מוניטין

0 Neutral

אודות yacovweiss

  • דרגה
    Member
  1. הגירסה החדשה מבוססת DOT NET ולכן חלק מהפקדים אינם זמינים , אבל יש תכנון להוסיף אותם בהמשך. מצורף העזרה על הנושא: < class="breadcrumbs" href="mk:@MSITStore::\Prog\Magic\uniPaas2\SUPPORT\mghelpw.chm::/uniPaaS_Reference_Guide.htm">Home > < href="mk:@MSITStore::\Prog\Magic\uniPaas2\SUPPORT\mghelpw.chm::/Migration/Migration.htm">Migration > < href="mk:@MSITStore::\Prog\Magic\uniPaas2\SUPPORT\mghelpw.chm::/Migration_from_eDeveloper_V10.1_or_uniPaaS_V1.x_to_uniPaaS_V2.0.htm">Migration from eDeveloper V10.1 or uniPaaS V1.x to uniPaaS V2.0 > What's Different in uniPaaS V2.0 < name="MiniTOCBookMark1">What's Different in uniPaaS V2.0 In uniPaaS V2.0, the Online GUI is based on the .NET framework instead of Win32. The .NET framework does not support all the appearances and controls behavior that were supported in previous versions, so there is change in the uniPaaS Runtime appearance as well. The major differences are described below. <>< href="mk:@MSITStore::\Prog\Magic\uniPaas2\SUPPORT\mghelpw.chm::/Whats_Different_in_uniPaaS_V2.0.htm#MiniTOCBookMark2">User State Persistency <>< href="mk:@MSITStore::\Prog\Magic\uniPaas2\SUPPORT\mghelpw.chm::/Whats_Different_in_uniPaaS_V2.0.htm#MiniTOCBookMark3">Online MDI <>< href="mk:@MSITStore::\Prog\Magic\uniPaas2\SUPPORT\mghelpw.chm::/Whats_Different_in_uniPaaS_V2.0.htm#MiniTOCBookMark4">Non-Supported Controls <>< href="mk:@MSITStore::\Prog\Magic\uniPaas2\SUPPORT\mghelpw.chm::/Whats_Different_in_uniPaaS_V2.0.htm#MiniTOCBookMark5">Control Properties <>< href="mk:@MSITStore::\Prog\Magic\uniPaas2\SUPPORT\mghelpw.chm::/Whats_Different_in_uniPaaS_V2.0.htm#MiniTOCBookMark6">Form Properties <>< href="mk:@MSITStore::\Prog\Magic\uniPaas2\SUPPORT\mghelpw.chm::/Whats_Different_in_uniPaaS_V2.0.htm#MiniTOCBookMark7">Logic Units <>< href="mk:@MSITStore::\Prog\Magic\uniPaas2\SUPPORT\mghelpw.chm::/Whats_Different_in_uniPaaS_V2.0.htm#MiniTOCBookMark8">Modifications by External Tools <>< href="mk:@MSITStore::\Prog\Magic\uniPaas2\SUPPORT\mghelpw.chm::/Whats_Different_in_uniPaaS_V2.0.htm#MiniTOCBookMark9">Functions <>< href="mk:@MSITStore::\Prog\Magic\uniPaas2\SUPPORT\mghelpw.chm::/Whats_Different_in_uniPaaS_V2.0.htm#MiniTOCBookMark10">Task Properties <>< href="mk:@MSITStore::\Prog\Magic\uniPaas2\SUPPORT\mghelpw.chm::/Whats_Different_in_uniPaaS_V2.0.htm#MiniTOCBookMark11">SDI <>< href="mk:@MSITStore::\Prog\Magic\uniPaas2\SUPPORT\mghelpw.chm::/Whats_Different_in_uniPaaS_V2.0.htm#MiniTOCBookMark12">I/O Devices <>< href="mk:@MSITStore::\Prog\Magic\uniPaas2\SUPPORT\mghelpw.chm::/Whats_Different_in_uniPaaS_V2.0.htm#MiniTOCBookMark13">End-User Functionality <>< href="mk:@MSITStore::\Prog\Magic\uniPaas2\SUPPORT\mghelpw.chm::/Whats_Different_in_uniPaaS_V2.0.htm#MiniTOCBookMark14">Status Bar <>< href="mk:@MSITStore::\Prog\Magic\uniPaas2\SUPPORT\mghelpw.chm::/Whats_Different_in_uniPaaS_V2.0.htm#MiniTOCBookMark15">Environment Settings <>< href="mk:@MSITStore::\Prog\Magic\uniPaas2\SUPPORT\mghelpw.chm::/Whats_Different_in_uniPaaS_V2.0.htm#MiniTOCBookMark16">Special Settings <>< href="mk:@MSITStore::\Prog\Magic\uniPaas2\SUPPORT\mghelpw.chm::/Whats_Different_in_uniPaaS_V2.0.htm#MiniTOCBookMark17">Planned Functionality for Future Version< name="MiniTOCBookMark2">User State Persistency The persistency is defined as in Rich Client tasks (Yes/No and not by giving form name). This change makes it simpler to use the form state persistency since you now do not need to define and maintain list of unique identifier names for your forms. In the Online form and model properties: < class="hcp1"> The Form state identifier property was removed. < class="hcp1"> The Persistent form state property was added. Note: Due to this change, existing users' form states are ignored. < name="MiniTOCBookMark3">Online MDI The Online Runtime MDI Frame is now defined as any other form in the Main Program (similar to the Rich Client MDI Frame). The benefit of this change is the gathering of all the form properties from the different locations they were once defined in, into single location. The following properties have been changed: < class="hcp1"> The Open task window task property in the Main Program now defines whether an MDI is shown. < class="hcp1"> The Main Display task property in the Main Program enables you to define several MDI frame forms and dynamically display the required form at runtime. < class="hcp1"> The Main Program's Task Properties dialog box contains new property called Run project as, which determines whether the Online or Rich Client MDI frame will be shown when running the project from the Studio (Ctrl+F7). < class="hcp1"> The Caption, System pulldown menu, and Icon file name properties were removed from the application properties and are now defined on the MDI Frame form itself. < class="hcp1"> The MDI Client area uses the color specified in the MDI Form property, giving you full control of the color. Controls on the MDI – In previous versions, it was possible to show Main Program form over the MDI and thus show static controls. This is currently not supported. Engine MDI The uniPaaS engine's built-in MDI was removed. This means that: <> The Runtime engine (uniRTE.exe) can run only if start application was defined. <> The runtime engine no longer provides environment editors. <> Modifying the environment settings (such as settings, colors, and fonts) or the users rights can be done in the following ways: using the Studio, text editor, or by designing ad-hoc application programs that utilize the INIGet and INIPut functions. Note that you can run the Studio without license to make these modifications. The internal events used to open the Settings repositories are not supported. < name="MiniTOCBookMark4">Non-Supported Controls The ActiveX, Rectangle, Ellipse, Horizontal slider and Vertical slider controls are not supported. Equivalent .NET or third-party controls can be used. Using ActiveX controls on Windows Forms is possible by wrapping them with .NET controls. Microsoft supplies the aximp utility to generate .NET controls from an ActiveX control. ActiveX controls will be kept by the migration process, but will generate Checker error. If you want to use an ActiveX control, you need to create the .NET wrapper for it using the aximp utility, and use the .NET control in your form instead if the ActiveX control. Note: The use of non-visual COM objects is unchanged and continues to be supported as in uniPaaS 1.x. < name="MiniTOCBookMark5">Control Properties < class="hcp1"> The Horizontal alignment property for List Box, Combo Box, Tab, Group, Rich Edit controls is not supported. Note: Right and Left alignment on some controls can be achieved using the RTL property. < class="hcp1"> Some of the Style and Border properties' values are no longer supported. < class="hcp1"> The Left and Top properties of GUI Display controls were changed to X and properties. < class="hcp1"> Visibility of controls behind container control – When control is placed on container control but is not attached to the container control, the control will not be seen at runtime. Specifically: <> for Tab container, it is not possible to have control shown on all the tabs (by not attaching it to specific layer). <> for Table control, it is not possible to have controls on the title area. < class="hcp1"> Location and placement of controls attached to container control – The location and placement properties' values of controls attached to container control is relative to the container control (instead of to the form in the previous version).This means that: <> Any expression used in the location properties of controls that are attached to container control will not work correctly and should be changed. <> Placement values of controls that are attached to container control may not work correctly and should be changed. < class="hcp1"> The background color of 3D controls will be seen (as opposed to White or Gray in the previous version). < class="hcp1"> Only TrueType and limited Open Type fonts are supported. Font Orientation is not supported. < class="hcp1"> In the previous Online version, the expression in some control properties was always re-evaluated when recompute occurred, even if there was no variable in the expression. This behavior was changed and the expression in these control properties is now re-evaluated only if the expression has variable that was changed. The properties are: Color, Context menu, Data, Enabled, Font, Format, Height, Range, Visible, Width, X, . Check Box Controls The Multiline property for Check Box controls is not supported when the Appearance property is set to Button. Combo Box Controls The height of the combo box is defined by the combo box's font and cannot be changed. Edit Controls The following properties are not supported in Edit controls: < class="hcp1"> Expansion Window – Only default internal window is supported (it is not possible to define form and use it as the size of the expansion window). < class="hcp1"> Show Scroll bars The Horizontal scroll property includes the Word Wrap option. The update value of Edit controls is displayed immediately before leaving the control. Image Controls The following properties are not supported in Image controls: < class="hcp1"> Image Effect < class="hcp1"> Parking and modifying properties – The following properties were removed from the Online Image control (and Model) – Must Input, Modifiable, Select Program, Select Mode, Help Screen, Help Prompt, Allow Parking, Tab Into, Allowed Directions and Tab Order. It will not be possible to zoom from the Image control and select file. Truevision targa (.TGA) images are not supported. Push Button Controls For Hyper Text buttons, the default color is taken from the CLR and not form the Internal Color Table. The Online Push Button control's Button Style property no longer has the Text on image option. It now works the same as Rich Client. The text for the button is defined according to the value of the Format property, and the button image is defined by the associated variable or the Default Image file property if no variable is associated with the control. Radio Button Controls The Multiline property for Check Box controls is not supported when the Appearance property is set to Button. RTF Edit Controls The RTF Edit control has no built in context menu. If you want to give the end user the ability to change the color or font of an RTF control, you can define menu with the uniPaaS internal events, such as Change Color, Change Font, Align Left, and Align Right, and assign this menu to the control's Context Menu property. The RTF Edit control no longer supports transparent background color. RTF Text Controls The RTF Text control does not support transparent background color. Static Controls The following properties are not supported in Static controls: < class="hcp1"> Static Type < class="hcp1"> Line Width < class="hcp1"> Line Style Tab Controls The Right and Left options of the Tab Control Side property were removed. If the tab has no default value, then the first tab will be selected and shown. Table Controls The Table in window, Keep Width and Last Divider properties for the Table control are not supported. It is not possible to use List box control in Table control. Tree Controls The Tree control does not support transparent background color. < name="MiniTOCBookMark6">Form Properties When migrating task with splitter on the form from previous uniPaaS versions, then an additional FrameSet form will be added. That form will include reference to the existing form in one of the frames. You then have to: < class="hcp1"> Manually define the called program in the other frame and remove the Call operation to that program. < class="hcp1"> Replace the explicit Call Program/Subtask operation with the Connect To properties of the relevant pane in the Splitter form. < class="hcp1"> model of splitter form is converted into two models – one for the frameset and one for the display form. If the form has model attached from component, you need to manually assign the display form model to the display form. The Left and Top properties of GUI Display forms were changed to X and properties. When the Startup Position form property is set to Default, the form size in the old Online and the new Online is different. Truevision targa (.TGA) images are not supported in the Wallpaper form property. Split Form The Split Window form property and Splitter child value of the Window Type form property are not supported. You can use the new Frames mechanism instead. It is not possible to call program or Batch task to run on splitter child area. You can now pass arguments to the called programs/tasks directly from the frame properties, and enjoy automatic refresh when these arguments are modified. For frames layout of more than two frames, you can call more than one program directly from the parent task. Note: < class="hcp1"> Splitter forms can run as child windows and have placement values, so when the host window is resized, the splitter form gets resized as well. Frames forms do not have placement, so when the splitter form is migrated to frames form and it is used as child window, the frames form will not be resized. To achieve the same runtime behavior, you need to create subform in the host and run the frames task in the subform. < class="hcp1"> The ability to call programs using Call operation to display in frame is currently not available in Online tasks. This will be added in future release. < name="MiniTOCBookMark7">Logic Units Until uniPaaS V2.0, in Online tasks, the Control Verification logic unit was executed when moving between the records only by using the mouse (and not when using the keyboard). < name="MiniTOCBookMark8">Modifications by External Tools Since the GUI layer is changed from Win32 to Windows Forms, any manipulation done on the uniPaaS forms and controls by external tools (such as get.dll) will not work. The CtrlHWND() and WinHWND() functions now return handles to .NET objects that can be used as reference in .NET library using the FromHandle() function. Existing Win32 UDF/UDP dll files that reference these objects will not work anymore. < name="MiniTOCBookMark9">Functions The following functions are no longer supported: < class="hcp1"> CLeftMDI < class="hcp1"> CTopMDI < class="hcp1"> HitZOrdr < class="hcp1"> SplitterOffset DirDlg function – The implementation of the DirDlg function in .NET libraries does not support the title and flags parameters. The syntax is the same as the ClientDirDlg function. The CLeft and CTop functions were replaced with the CX and CY functions (as in Rich Client). The CX and CY functions are now available in all task types. < name="MiniTOCBookMark10">Task Properties The Foreground Window property is not supported. In previous versions, It appeared only when the SpecialOldZorder special flag was set to . The following task modes are not supported for Online tasks: Delete, Locate, Range, Key, Sort, Files, and Options (when used as initial task mode and raised by the user). < name="MiniTOCBookMark11">SDI The SDI window type does not require the program to be parallel (since parallel execution is not supported in this version). Running non-parallel SDI window means that the window will be closed when closing the parent (as in any other window). At runtime, pressing Esc button will not close the SDI window. To hide the MDI window for an SDI style deployment, set the Open Task Window task property in the Main Program to No. < name="MiniTOCBookMark12">I/O Devices The Console Media type is no longer supported. Previous projects with Console media will be changed to Graphic printer. < name="MiniTOCBookMark13">End-User Functionality Some of the built-in end-user functionality that existed when running Online tasks is not supported in Rich Client tasks. This includes user range, user locate, user sort, change index, view by key and Print Data. new component was added to provide user range, user locate, user sort and Print Data with better graphical interface. The source code of this component is also provided, so you can modify it to fit your needs. It is not possible to open the Expression Editor while performing user range and user locate. < name="MiniTOCBookMark14">Status Bar The status bar does not show the user name. < name="MiniTOCBookMark15"> Environment Settings The following environment settings are not supported: < class="hcp1"> Deployment Custom Copyright < class="hcp1"> Display Copyright Messages < class="hcp1"> Display Toolbar < class="hcp1"> Indent Characters < class="hcp1"> Logo File < class="hcp1"> MDIClientEdge < class="hcp1"> MDIClientImageFile < class="hcp1"> MDIClientImageStyle < class="hcp1"> Pulldown Menu Close Timeout < name="MiniTOCBookMark16">Special Settings The following special settings are not supported: < class="hcp1"> ShiftEditCursor < class="hcp1"> Special3DStyle < class="hcp1"> SpecialAccessPhantomByHandler < class="hcp1"> SpecialAsyncCOMEvents < class="hcp1"> SpecialBatchOptions < class="hcp1"> SpecialCenteredFloatingWindow < class="hcp1"> SpecialExitControlOnClick < class="hcp1"> SpecialExitNoParkable < class="hcp1"> SpecialFlat2DCombo < class="hcp1"> SpecialGUILNF < class="hcp1"> SpecialNoSplash < class="hcp1"> SpecialOldTestEnv < class="hcp1"> SpecialOldWinRunner < class="hcp1"> SpecialOldZorder < class="hcp1"> SpecialPaintFormInCreate < class="hcp1"> SpecialShowDBLogin < class="hcp1"> SpecialSingleItemRadio < class="hcp1"> SpecialTabControl < class="hcp1"> SpecialTableComputePlacement < class="hcp1"> SpecialModalToolWindow < name="MiniTOCBookMark17"> Planned Functionality for Future Version The following Online functionality is planned for future version of uniPaaS V2.0: < class="hcp1"> Parallel execution – Programs that are defined as parallel will not run in parallel. Events that relate to parallel execution will be ignored. The property will remain in the task properties, but will be ignored. < class="hcp1"> Multi-Mark – All properties, events and functions related to multi-marking will be ignored. All properties will be kept in the application. < class="hcp1"> Window Menu – The MDI Window submenu (for selecting from list of open windows) will not display. MDI Window menu events will be ignored. Subforms in Tab controls In version 1.0, tasks defined in Subform controls that were attached to Subform control were loaded after the host Record Prefix and were not refreshed when the subform tabs were changed. In version 2.0, these tasks are initially loaded when the subform becomes visible and then loaded again every time the subform becomes visible. This change causes two main differences between V1.0 and V2.0: <> The subform task load timing is different. <> The subform is always displayed refreshed, but there are more calls to the subform task. This behavior is planned to be changed in the future versions.
  2. הייתי מחכה קצת לפני העברה של מערכת עובדת לV2 . רצוי לחכות עד שיצא גרסת תיקון אחד לפחות. בינתיים אפשר להשקיע את הזמן ללמוד את היכולות החדשות... בברכה, יענקי
  3. יצא גרסת ENT בתחילת שנת 2000 למידע נוסף : < href="http://spiegelwrites.blogspot.com/2011/02/magic-software-timeline.html">http://spiegelwrites.blogspot.com/2011/02/magic-software-timeline.html בברכה, יענקי וייס
  4. קשה לי להאמין שיש בעיה ברמה של מאיפה לוקחים את השעה , יתכן שהגירסה לוקח את השעה מהשרת. נשארת השאלה אם הישום של זהה לשל 9 בברכה, יעקב
  5. בעיה בפקודת - צא

    הוסף " לפני ואחרי הנתיב, אמור לפתור את הבעיה
  6. שגיאת 86 כבר לא קיימת מגירסה PEVASIVE 2000 {7} כנראה שמותקן אצלו שאריות של BTRIEVE תריץ ANALAZER של PERVASIVE עם סריקה מורחבת למחיקת כל הגירסאות הישנות. יעקב
  7. DBDEL מוחק גם טבלאות שנמצאים בזכרון .... The DBDEL function, when given table that is resident as parameter, will remove all rows from the resident table. Subsequent opening of this table will reload them from the database. Magic Software Enterprises 1998 All Rights Reserved בברכה, יעקב
  8. תודות

    כל מילה נוספת מיותרת בברכה, יעקב וייס
  9. משום מה לא צורף הקובץ... נסיון אחרון. Demo_BufGetSetVector.zip
  10. STEVE BLANK כתב דמו לגבי הנושא של וקטורים וBLOBS הנה הציטוט , ומצורף הקובץ: Re: magicu-l Saving and Retrieving Arbitrary Vectors It turns out that this is pretty neat way to enable "sticky" selections in multi-select list box. What mean by "sticky" is that, when the user executes an online program that displays list box control and which allows the user to select multiple list items, the program remembers the user's selections so that the next time they execute the program, their previous selections are automatically selected again. The demo slapped together for Andy only remembers the user's selections for the duration of the current session, but it would be trivial extension to write the SharedVal Blob out to disk and fetch it back in the Main program's TS and TP, respectively. For those of you that might be interested in seeing this, I'll upload the demo program to the shared files area under the name Demo_BufGetSetVector.zip Steve Blank
  11. STEVE BLANK כתב דמו לגבי הנושא של וקטורים וBLOBS הנה הציטוט , ומצורף הקובץ: Re: magicu-l Saving and Retrieving Arbitrary Vectors It turns out that this is pretty neat way to enable "sticky" selections in multi-select list box. What mean by "sticky" is that, when the user executes an online program that displays list box control and which allows the user to select multiple list items, the program remembers the user's selections so that the next time they execute the program, their previous selections are automatically selected again. The demo slapped together for Andy only remembers the user's selections for the duration of the current session, but it would be trivial extension to write the SharedVal Blob out to disk and fetch it back in the Main program's TS and TP, respectively. For those of you that might be interested in seeing this, I'll upload the demo program to the shared files area under the name Demo_BufGetSetVector.zip Steve Blank
  12. התכנות לSQL הוא למעשה שונה מאוד מISAM . באופן כללי ISAM תמיד יעבוד יותר מהר בכתיבה ובתחומים. SQL יעבוד מהר יותר בסיכומים ובהצגת VIEWS . כך שאם תכוב מחדש את הדוחות וחלק מההצגת הנתונים כן אמור להיות שיפור ב'משיכת מידע'. מנסיון זה די הרבה עבודה. הדרך הכי פשוטה לעבור לMSSQL לפי מה שכתבו אחרים הוא להשתמש בכלי של < href='http://www.mertechdata.com'>www.mertechdata.com . הביקורת עליו מאוד טובה , אבל שוב לי אישית אין נסיון איתו. בברכה, יענקי וייס
  13. בUNIPAAS יש פונקציה חמודה שנקראה 'FileInfo' . זה ביחד אם הפונקציה FileListGet צריכים לתת לך מענה. אם אתה עובד על גירסה יותר ישנה יתכן וכלי כמו GET.DLL או HOTFUDGE יתנו לך מענה. יתכן וגם תרצה לעיין ב: < href='http://www.ng-sw.de/mg-wikka/WindowsAPI'>http://www.ng-sw.de/mg-wikka/WindowsAPI בהצלחה! יענקי
  14. תייצר את הדוח כPDF. לאחר מכן תעביר את הקובץ ללקוח דרך פקודת clientblob2file ואז תוכל לפתוח אותו בעזרת פקודת 'צא' . בברכה, יענקי
  15. התכוונתי שהגישה על המחשב ישירות :\ ולא גישה מהרשת. בברכה, יעקב
×