Worksheet plugins and "libprc"

How about: user error? 😉

Your expectation is a bit off. This should work:

libprc:my_library/prc:my_proc

Although, I'm not sure where you are getting the URL for the prc from.

Daniel

Hi Daniel

"I'm not sure where you are getting the URL for the prc from."
This is the question 🙂

On activate the plugin I got only "libprc:my_library"
What I want is the extended version "libprc:my_library/prc:my_proc"

That's normal and as-documented:

"pObjectUrl—URL of the current main development object, in the format ObjectType:ObjectName. For example, cpt:MY_COMPONENT, ent:SALES_ORDER.SALES, aps:MY_APP, libsnp:MYSNIPPETS, and so on."

See (e.g.):

> Managing Development > IDE Worksheet Plug-Ins > Worksheet Plug-In Operations > ws_activate

When you switch between Editor tabs then the selected object is (currently) not remembered. In the plug-in you basically need to display the objects that belong to a main development object (like it's done in the Define Structure or Write Script tabs).

"That's normal and as-documented"
In documentation there is no word about, that subobjects not provided.
The list should be treated as an example

"main development object like it's done in the Define Structure or Write Script tabs"
And with my screen shoot I prove, that the "Write Script tab" contains only one object.
So this "like" could/should be read as "the object currently in the tab"

If this a bug or will not fixed at all, how to create a plugin working on individual global procs?
Working on the whole proc-libray is useless as the example "listings" show us

Ingo

Hi Ingo my friend,

so I am not the only one with this problem/wish (just nor yet reported to Uniface).

Also it is documented, it is not the expected behaviour.

I will do some special action on exacly ONE item (the one the cursor is on) of the library and not on the whole library. For this i need to know the exact element i have selected.

Kind regards

Norbert

Especially if there a syntax for transfer such information grumbel 

And the same problem occurs with the Projects.

I don't want to add a whole library to the Project, i want to add only one message/proc.

There are also no timestamps for the subobjects, so you will never know which part of the library has changed!?

Norbert

There is also no word that sub-objects are provided. If something is not mentioned in the documentation then you probably should not assume that it's somehow available.

At this moment the worksheet plug-in is only aware of the main development object in an Editor. In case you chose a sub-object then this currently is not communicated to the plug-in. Therefore this functionality is currently not available, so feel free to create a wish for this.

And your screen shot does not really prove that the "Write Script tab" contains only one object. If you check the structure of the Editor tab (on the left of the Code Editor) then you'll see the main development object on top (which is not visible in your screen shot). It's correct that the Code Editor will just show the code of the selected object. But this does not mean that only the selected object is present in (e.g.) the "Write Script tab".

And in the same way you can create a worksheet plugin that shows the "listing" of an individual global proc. You give the user the possibility to select a global proc from the library (or main development object) that currently is loaded in the Editor. And when the user selects a specific global proc then you can display the "listing". This seems really straight forward.

Hope this helps.

Daniel

Hi Daniel
"If something is not mentioned in the documentation then you probably should not assume that it's somehow available."

The line in to decomentation only tell us about a few exmaple.
And this examples are all belong the generic URL.
And this topic show us all possible combinations of objecttypes
In my opinion it's a strong indication, that plugins also support this URL 🙂

Ingo

That's one way of looking at it. But it clearly says: "URL of the current main development object". And prc-objects are not main development objects, but the library (in this case libprc) is. Therefore your argument is not really applicable here.

Could plug-ins support this? Sure they could. Is this currently supported or implemented? No.

If this is functionality you would like to see then please make a wish. This will give product management and the lab an indication on the things they probably should look into.

Thanks,
Daniel

Next question ins this sphere:
How to compile just on global proc?
Every time I modify one global proc and click "compile", all global procs  in a library will be compiled.
And this is time consuming 😔

Ingo

Hi Ingo,

I do make always the same "error"!

You have to rightclick on the proc and use the compile there for compiling only one proc.

Gruß

Norbert

ThanX Nobert 🙂

Back to the topic
Is there a global (IDE-)variable which contains the current subobject?
Or the whole URL in the format “libprc:my_lib/prc:my_prc”
As i did a lot programming with precompiler constants in globale procs, the only was to see, if the condtions/loops/constants are resolved correct is to have a look into the listing.
And this should possible with the IDE ….

BWT,I provoked an error once and behold, the refresh routine distinguishes between COLL (libprc) and OCC (prc).
So it shouldn't be a problem to also transfer the info as a URL.

    , operation WS_ACTIVATE:1, [NONEXIST = ""] Comp: IDE_X_LISTING/_ALIAS00000032
    , occOperation SETCONTAINERATT:19, [activate VINSTANCENAME."WS_ACTIVATE"( VURLSTRING ) ] Comp: UV_AREA_USER/_ALIAS00000031
    , occOperation VM_WO_REFRESH:23, [ $occhandle(AREA01.LAYOUT)->setContainerAtt(VSTATENODE,VATTVALUE,STATEROOT.AREA01,DATAROOT.AREA01)] Comp: UV_AREA_USER/_ALIAS00000031
    , collOperation VM_WE_REFRESHUDE:63, [ $occhandle(AREA01.LAYOUT)->vm_wo_refresh(VSTATENODE,PDATANODE,PSTATEROOT,PDATAROOT)] Comp: UV_AREA_USER/_ALIAS00000031
    , collOperation VM_WE_REFRESH:43, [ $collhandle(AREA01.LAYOUT)->vm_we_refreshUde(PWIDGETENT,PDATANODE,PSTATEROOT,PDATAROOT,VSTATENODE,VCUROCC,VSELLOCS,VSELOBJS)] Comp: UV_AREA_USER/_ALIAS00000031
    , entry LPREFRESHVIEW:34, [ $collhandle(VENTITYNAME)->vm_we_refresh(VSTATENODE,PDATANODE,PSTATE,PDATAROOT)] Comp: UV_AREA_USER/_ALIAS00000031
    , operation VM_REFRESH:57, [call LPREFRESHVIEW(PSTATE,PDATANODE,PDATAROOT)] Comp: UV_AREA_USER/_ALIAS00000031
    , entry VC_REFRESHVIEW:62, [activate VVIEWINSTNAME."VM_REFRESH"( PSTATE , PDATA->*{1} , PDATA , PCMDRESULT ) ] Comp: UC_LIBPRC/_ALIAS0000001E
    , entry VC_REFRESHVIEWHIERARCHY:1, [call VC_REFRESHVIEW(PSTATE,PDATA,PCMDRESULT)] Comp: UC_LIBPRC/_ALIAS0000001E
    , entry VC_REFRESHVIEWHIERARCHY:33, [call VC_REFRESHVIEWHIERARCHY($STATE$->"%%VCONTAINEDVIEWKEY",PDATA,PCMDRESULT)] Comp: UC_LIBPRC/_ALIAS0000001E