Re: RDi download

["Hiebert, Chris" <chris.hiebert@xxxxxxxxxxxxxx>]

I'd say it depends on what IBM changed in RDI that suddenly broke the plugin.
But I think they both should have tested it a bit more before releasing.

For the first one. You open for Browse, but RDI decides you really want to Edit.

> From my observations, it appears to be caused by the new Lock decorator added to RDI.
Now RDI tries to lock the source after it has been open, then adds the little padlock to the open image.
So it seems like IBM caused the issue because they now try to lock the source after its open.
So the method Aldon uses to open for Browse is also triggering the "Lock this source" code added to RDI.
Which now changes the open from browse to edit.

I've reported both to Rocket-Aldon.


Chris Hiebert
Senior Programmer/Analyst
Disclaimer: Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.

From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of David Gibbs via WDSCI-L
Sent: Friday, October 22, 2021 9:44 AM
To: Rational Developer for IBM i <wdsci-l@xxxxxxxxxxxxxxxxxx>
Cc: David Gibbs <david@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] RDi download


On 10/22/21 10:37 AM, Hiebert, Chris wrote:

> 3.       RocketAldon open for Browse opens for Edit instead, allowing edits to non-checked out source members.

> a.       Work around, open the file twice for browse.

> 4.       RocketAldon compile from Aldon's compile-option causes Event File error.

> a.       Seems to generate an error without impacting the overall compile. So it's just annoying.



I don't think those are issues with RDi ... they are probably issues

with the Aldon plug-in.



david