entire .w window read-only

I remember having that happen to v9 .w's using App Builder, but never with Architect.

I had to delete comments to add new code.

Unfortunately I never figured out how to get it back to 100% normal.

Are you using App Builder?

btw it's Memorial Day over in the U.S. - so some of the normal responders may be afk.

In 11.2 ABL Source editor has been enhaced to protect Appbuilder auto generated code to avoid any possible file corruption that is part of Appbuilder Integration. Editor decide auto generated code based on ANALYZE-SUSPEND/RESUME tokens in the code. I am not sure how the file became read only, but there is quick option available to disable this feature in PDSOE. Go to Preferences>>Progress OpenEdge>>Appbuilde>>Editor and unselect "Mark Appbuilder generated code read-only".

Now you should be able to edit your file. Hope this will solve your problem.

Thanks

Yogesh Devatraj

I'm gonna tuck this tip away for when we get to 11.2. I still have some legacy AB .w's that I'll need to maintain.

Seems an odd setting. Are we supposed to strip App Builder markup and continue with a more native Eclipse source?

Yeah, it's the new 11.2 appbuilder with the fancy read-only sections

in the abl editor. Although not so fancy right now ...

no, it's actually very cool. When it works

It makes all the appbuilder generated code read-only so you can't mess

with it - like if you load a .w into notepad, and delete a line with

the thought "don't know what that does".

Next time you load the .w into the UIB it doesn't load.

This feature prevents from you from shooting yourself in the foot.

Perhaps it's decided that I am not to be trusted with any source ....

ahh that makes sense.  I've always been very delicate when editing AB-generated source in Architect.

Nice to know that if it works as intended, it will protect us against accidental edits.  Sometimes in v10 moving from the AB edit window to Architect source can insert wierd bits that cause syntax errors.

I look forward to testing this in v11 PDS.  I've just contacted Progress support to see if we can extend out eval edition.  We won't be able to migrate our live DB's to the latest version until later this year.

I'll be sure to check this out more when I extend the evail.  I'll comment to this thread if I can replicate your issue.

Thanks for the heads up!

Perhaps it's decided that I am not to be trusted with any source ....

And, to prove it right, you will work around the safeguard!

It will be interesting, though, to see if you can work out what was causing the problem.  While I understand why some people think the AppBuilder was cool, there is something about this Do Not Touch code idea which bothers me.

I'm on it

found the problem

CREATE WIDGET-POOL.

was missing a couple of lines ...

CREATE WIDGET-POOL.
/* _UIB-CODE-BLOCK-END */
&ANALYZE-RESUME
 

I really have no idea how those two lines went MIA

happens to me when I paste in code blocks, and I get careless. ^^

sometimes I'll revert to last saved and paste in again + works fine.

yeah - the problem is that I am not meant to be able to do that,

because of the read-only sections.

In theory, I shouldn't be able to delete those lines as they are

readonly. Unless I use an external editor. Which I didn't

I know that I sound like a user right now, but I honestly didn't use

another editor !!

Perhaps it's decided that I am not to be trusted with any source ....

>

I believe that's what's known as a softball ... will resist snarky reply ...

-- peter

Hi Yogesh,

I rather like the new AppBuilder integration as it is getting better and better. Keep up improving this! However there is one thing I cannot find anywhere: the good old procedure properties. Where are they tucked away?

-peter

they are on the toolbar. See image

oi! and don't hijack my thread Start your own ...

jmls wrote:
they are on the toolbar

Aha thanks!

-peter

jmls wrote:
oi! and don't hijack my thread  Start your own ...

Sorry I ran out of cash so I decided to borrow yours

yeah. ran out of cash. right ....