Visual LANSA Forum

We use a Reusable Part extending #PRIM_PPNL to popup a "Loading - please wait" message (ShowPopup) while we build and display other panels.

The process of displaying that popup greys out the screen behind it and then displays the popup with it's message

Then we trigger a ClosePopup to close that ...

Thanks Atostaine, Fit to Both does show a scroll bar but when there aren't enough records to fill the entire row of the Layout that the List is in, the List displays the Alternate Column styling below the data filled rows and it shows a border around the entire list including the empty space. I ...

What I want most of all though is "Control Vertical Size by Content Up to a Maximum of the Size of the Row that Contains the List then Contain it Within the Row and Display Scroll Bars".

It may be I'm overdoing this.

We can achieve the look we want without all this mucking around IF we don't apply a non white ThemeDrawStyle for every second column. If we leave each column white, then the native way the List box works looks fine using even Fit Both. But when we apply a Alternate ...

Oh except your list header scrolls off the page. I guess that is why you included a separate header outside the panel.

Thanks Joe, that worked great.

I was expecting that Content Height would respect the layout row boundaries. We had Content Height set for our list so that we didn't have all the blank rows showing but once it got too long it ran off the bottom of the screen, way past the next row. Enclosing it in ...

OK I will try that on the next attempt. Can a Task be re-opened once I've closed it? I have deployed this one to Live but we will be modifying it soon under the same task so I don't want to close it if that is permanent.

No. Does it need to be?

The LANSA menu option 10. Add all objects worked on under a task identifier(s) to list does not seem to do anything, No Tasks show up in the list to select. They do show up in the option 12. Work with Tasks so I know that LANSA knows about the tasks but for some reason doesn't show them for ...

The option is now always available for me every time. Based on what you have just said, I wonder if before, when I brought the file in with it's fields, somehow the fields weren't getting set to "checked out" status.

Whatever was going wrong is no longer going wrong.

Yes the option to "replace fields" makes perfect sense (and should probably be the default)

I can't think of a reason why you would want to bring the file back in and NOT automatically replace all the fields. Unless you had already changed the properties of the fields within the IDE and you wanted ...

Anyway, the old file and fields are all deleted now and the new version brought back in and all is working ok.

Yeah I suspect because the fields I didn't change all came across ok that it's only if you change the definition of a field that already exists in LANSA that it has a problem. Under those circumstances it brings the new field in with a modified name and leaves the old field alone (but seemingly no ...

It's completely screwed now. The original fields are now divorced from the file so even deleting the file won't get rid of them and I have to find each field and delete them separately. Basically, reloading the file when it already exists will cause it not to replace the fields that are already ...

I decided to try doing it via the usual way of adding a new file and the fields with new lengths created new fields in LANSA with 001 appended to the end of them.

Is there a separate reload option, or is it the same process as bringing it in as a new file?

If I change a Physical file on the Iseries that I already have brought into LANSA, can I refresh the definition of that in LANSA or do I need to delete the current version in LANSA and bring it in from scratch?

I've worked it out. The "User Information is not Valid" error is somehow related to me last week adding a library to the DCXPGMLIB library list. Something about that, LANSA didn't like.

My colleague was doing everything I was doing but it was working for him and not for me. I got him to delete the file so I could try again and this time it worked for me so I've no idea.

Still having the same "User Information Provided is not Valid" error but I'm chasing that up with Support

If ...

One of my colleagues has successfully got the fields to go across. He's going to show me what he did and I'll see how it differs from what I did.