Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (3)

Resolved 2017 IDE

  1. Issue
0
Votes
Undo
  1. Allan Seagrott
    Allan Seagrott
  2. PowerBuilder
  3. Sunday, 2 July 2017 21:45 PM UTC

Hi

I've come across a minor behavioural difference with the new PB 2017 IDE Build 1666. When I search across the PBLs in my workspace, then edit from the search result set. It opens the object's script as expected. If do a CTRL-H to replace the searched text, it will not make the change unless I firstly set the cursor focus into the script area before doing the replace. The replace would work in previous PB versions without having to set the focus first.

The same applies to CTRL-F find. Has anyone else come across this?

Allan

  1. Build
Re: "Hands-on Look at PowerBuilder 2017" Webinar
PowerServer data source profile configuration prob...
Responses (3)
Andreas Mykonios
Andreas Mykonios Accepted Answer Pending Moderation
  1. Monday, 3 July 2017 14:11 PM UTC
  2. PowerBuilder
  3. # 1

Hi Alan.

I had the same issue. But the IDE seems pretty stable (with 12.x the IDE wasn't so stable).

Andreas.

Comment
There are no comments made yet.
Appeon Support Team
Appeon Support Team Accepted Answer Pending Moderation
  1. Tuesday, 4 July 2017 08:47 AM UTC
  2. PowerBuilder
  3. # 2

Hi Alan,

Thanks for bringing it to our attention.

We reproduced it on our end in PowerBuilder 2017.

And we tested to find that PowerBuilder 12.6 has this same issue as well.

Kindly please let us know the (previous) PB versions in which it works fine without having to set the focus first so we can test it when we try to fix it. Thanks.

 

Regards,

Appeon Support Team

Comment
Allan Seagrott
  1. Allan Seagrott
  2. Wednesday, 5 July 2017 01:19 AM UTC
Seems reply is a comment so ignore this thanks :)

  1. Helpful
There are no comments made yet.
Allan Seagrott
Allan Seagrott Accepted Answer Pending Moderation
  1. Wednesday, 5 July 2017 01:18 AM UTC
  2. PowerBuilder
  3. # 3

Hi

I don't get the issue on the last 12.6 build I was running which is 4091. I was developing on windows 10 x64.

Thanks

Allan

Comment
Appeon Support Team
  1. Appeon Support Team
  2. Friday, 7 July 2017 06:44 AM UTC
Hi Allan,



Thanks for reporting this problem!



We reproduced it on our end and will do further research to figure it out.



We will keep you posted about the progress. 



Regards,



Appeon Support Team

  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.