Search results

I have never used anything like this before so am not sure if this is correct/works for deleting buffers: hQueryHandle:GET-BUFFER-HANDLE(hBufferHandle:NAME):BUFFER-DELETE (). Normally, the following is all that you require: hBufferHandle:BUFFER-DELETE(). Does that work? Another thing to...

I am not quite sure on this one. This compiles and if you try this does it work: hListViewItem = CAST(e:Data:GetData(Progress.Util.TypeHelper:GetType ("System.Windows.Forms.ListViewItem")), System.Windows.Forms.ListViewItem).

listView1:AllowDrop = TRUE. listView1:DragDrop:Subscribe(listView1_DragDrop). listView1:DragEnter:Subscribe(listView1_DragEnter). If in a class then: METHOD PRIVATE VOID listView1_DragDrop( INPUT sender AS System.Object, INPUT e AS System.Windows.Forms.DragEventArgs ): MESSAGE "DragDrop"...

I never knew window resized event fires like that but it does. I thought the solution was to make the window insensitive and make it sensitive after it has been made visible but it then fires: hWin:SENSITIVE = FALSE. ... hWin:SENSITIVE = TRUE. No idea how to solve this.

Does trapping the 'MOUSE-SELECT-CLICK' solve?: ON MOUSE-SELECT-CLICK OF BROWSE-1 IN FRAME DEFAULT-FRAME DO: MESSAGE "Mouse Select CLick" VIEW-AS ALERT-BOX. END.

I have some example code of dynamically adding nodes and sub nodes to a .NET TreeView and this is attached. It does not do exactly what you require as it dynamically adds when first run and not when a node is clicked, but hopefully it gives you some ideas and you can adapt.

Thanks Cecil, it has fixed it.

Do you want the information for the embedded windows or for the .NET forms? If for the ABL windows then usually these have been run persistently so one idea is to walk the widget tree for persistent procedures and obtain information from the procedure handle. If though it is the .NET form...

Really good to hear you have got it working. So in the propath you have something like this?: ,C:\Development\Webwiew\WebView2Loader.dll Just tried that but still find the same in that nothing appears.

It has been a long time since I used CREATE MENU-ITEM but think once created it is always available even if created in a trigger/internal procedure. So either delete or remove from the relevant widget: SELF:POPUP-MENU = ?.

I think you are correct in that it is a runtime issue and postings here mention an extra file - WebView2Loader.dll - required for runtime: https://community.progress.com/s/question/0D74Q000008IUBHSA4/detail This file is in the package so included that in the working directory but still no joy.

I have never used this control but had a quick look - Progress 11.7.4 - and found the exact same problem. Tried the following as well but nothing: webView21:Show(). Checking on the changed events and they never fired: METHOD PRIVATE VOID webView21_LocationChanged( INPUT sender AS...

I am really not sure on this. It may be possible you want something like this: /* Firstly create a dynamic temp-table for all the required fields */ CREATE TEMP-TABLE hTemp. /* Add all the fields */ FOR FIRST _file NO-LOCK WHERE _file._file-name = "test" ,FIRST _index OF _file NO-LOCK...

The error means one of your handle variables has not been created or set: If I had to guess it looks to be fh as you are referencing it but cannot see where it is being assigned/created: hTemp:ADD-LIKE-FIELD(fh:NAME,fh). ... ASSIGN fh = bh:BUFFER-FIELD( _field._field-name )...

As Stefan has posted it is really not easy to make heads nor tails of your code. Are you trying to create a single JSON file of all the tables or separate JSON files for each table? If the former then a bit of thought is required because as Stefan posted JSON is not a line based format, you...

With a dynamic temp-table it is the variable handle you use: hTemp:WRITE-JSON(vTargetType, vFIle, lformatted).

I came to the solution with a bit of trial and error. In most cases you can normally assign directly as in this example: DEFINE VARIABLE oStartInfo AS System.Diagnostics.ProcessStartInfo NO-UNDO. DEFINE VARIABLE oVerbs AS "System.String[]" NO-UNDO. oStartInfo = NEW...

I have not worked with System.Windows.Forms.DragEventArgs so a rough translation only but hope it points you in the right direction: PROCEDURE Form1_DragDrop: // or if a class METHOD PUBLIC VOID Form1_DragDrop (INPUT sender AS System.Object, INPUT e AS System.Windows.Forms.DragEventArgs)...

A bit of a long shot, but if you read each byte and add the characters together does the file name appear anywhere?: DEFINE VARIABLE i AS INTEGER NO-UNDO. DEFINE VARIABLE j AS INTEGER NO-UNDO. DEFINE VARIABLE vCharacters AS CHARACTER NO-UNDO. j = FileGroupDescriptor:Length - 1. DO i = 0 TO j...

Unfortunately I have not worked with memory streams or System.Bytes so cannot answer your questions of what everything is actually doing. The code posted was a best guess at what I thought the ABL code could be. Having a fresh look though I wonder if the two lines should be something similar...