good morning

for me it is eliminating PBLs

My top change would be if you open an object from the System Tray, or by clicking on a link in Search results, and the object is not checked out, give an option to check it out, not just a warning that it isn't checked out.

And if you are working on a bunch of Search results, often if you save a change in an object the Search results disappear and you have to do the Search again. Stop doing that!

If you use ProDiff for PowerBuilder as your diff program, it understands source code changes like that and the diffs are still correct. The only think it (pretty obviously) can't figure out is stuff like renaming methods. (Sorry, this was a reply to the user complaining about small changes in their code (like changing function args) changing the order of the methods in an object so diffs then messed up.)

The update properties issue is a nasty one, indeed. I don't know how often I forgot that.

My contribution: stop jumbling the entire source code whenever I change a function's signature.

This really makes tracking changes a nightmare. I mostly resort to direct source code editing when I need change arguments or return types.

IDE CHANGE REQUEST:

How about allow editing a DataWindow when in zoom mode and allow the user to choose the zoom size. 

Thanks,

Andy

Editor enhancement:

When selecting some text, show that text highlighted everywhere else in the script. (just like in Notepad++ or when doing a search in VS editor).

IDE CHANGE REQUEST:

Allow me to open an ancestor object or window while editing a descendant object or window even if it is in read-only mode. There are many times I need to review the ancestor's structure as a whole, not just the ancestor script, while building descendant objects.

(Sorry to reply twice but since the first one was about a bug I though it wouldn't hurt to reply about a feature change too).

Regards,

Ricardo

IDE CHANGE REQUEST #1:

How about a flag that sets the PBv12.5 icons in the Painterbars and Powerbar when set. The current ones all look alike.
      Design option, checkbox:  "Use PBv12 Toolbar Icons"

Or maybe an option to allow the user to specify which icon is to be used for each toolbar. Included in the list of available icons would be the PBv12 and PBv10 icons - some of those were quite good.
      Design option, checkbox:  "Use Custom Toolbar Icons"

IDE CHANGE REQUEST #2:

When duplicating an object, like a command button, provide the option to include the scripts and functions.

Thank You,

Olan

I'm sorry, Mike ... not possible to choose just one item I want to see fixed, addressed or improved in the IDE. It's like asking a parent to name their favorite child (when they have more than one, of course)!

We all realize and fully appreciate that Appeon has had to (and continues to!) prioritize and invest their limited development resources towards constructing critically-needed functionality, so I've been supportive and patient. At some point in the not-too-distant future, however, I would LOVE to see a new version focused on improving developer productivity and modernization of the entire IDE and in particular, the PowerScript Editor.

Thank you for asking!

This one has been bugging me for a long, long time...

When the Properties pane is closed in the DataWindow painter and I select two or more objects (e.g. texts, columns, pictures, whatever) and then select Properties from the View menu the Properties pane opens but starts behaving erratically and eventually the IDE crashes. If the Properties pane was already open, I can select multiple objects without any problem.

Dear AutoScript,

I know you'll never be IntelliSense, but I'm still happy to accept any help you can offer.

But if I catch your grubby little fingers touching my clipboard one more time, I swear I'll cut you!

Regards,
Markus

P.S. If you're ever thinking about expanding your horizon, consider builtin PowerScript functions and userobject function parameters

IDE CHANGE REQUEST:

When the libray list in the PROJECT file changes, don't simply add the new PBLs to the list of PBLs already there as UN-CHECKED. Either un-check ALL of the PBLs or check ALL of them after the replacement have been made.

It's very easy to foget to change the flags, especially when the replacements are below the first page of data and cannot be seen. This occurs in my environment when I update the Class Libraries of the application.



Thank You,

Olan