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

Resolved Mystery DataWindow Property

  1. Misc
0
Votes
Undo
  1. Roland Smith
    Roland Smith
  2. PowerBuilder
  3. Thursday, 23 February 2023 20:09 PM UTC

I did a save of a datawindow in PB 2022 Build 1892 that was last updated in PB 2019. I didn't change anything, I just clicked the Save button.

The dropdown columns have a new property that is not in the help:

dddw.autofill=no

I also don't see the property in the painter.

Any ideas on what this is?

datawindow dataobject name
Creating a row indicator to a grid dw dynamically
Accepted Answer
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 23 February 2023 20:57 PM UTC
  2. PowerBuilder
  3. # Permalink

Hi Roland;

  That is an early "taste" of a new property that will be used in the PB2022 R2 release only coming out later this year for "Auto Scrolling" a DDDW on keyboard entry. Of course in the current GA release, it''s not used (active) yet. Basically, just a "place holder ATM".   HTH   ;-)

Regards ... Chris

Comment
There are no comments made yet.
Responses (3)
mike S
mike S Accepted Answer Pending Moderation
  1. Thursday, 23 February 2023 22:48 PM UTC
  2. PowerBuilder
  3. # 1

it is more bloat to the datawindow...

I wish it would just assign the default at runtime - like it does when the datawindow is from a release prior to the property being created.  instead, they add the property and the default value.  

more bloat = larger files which do make a difference when saving datawindow syntax in a database, or pulling it out to process at runtime.  

more bloat = harder to read through for stuff that is actually important when looking at the syntax

 

It also makes it harder to use the datawindow in a prior PB release - now you have to strip out those autofills

Comment
Roland Smith
  1. Roland Smith
  2. Friday, 24 February 2023 02:01 AM UTC
Agree
  1. Helpful
John Fauss
  1. John Fauss
  2. Friday, 24 February 2023 02:33 AM UTC
Wholeheartedly agree.

We always perform a "diff" comparison (we use ProDiff) on ANY changed object (including DataWindows) against the unchanged object as part of our normal change control process, to ensure that no unintended changes are incorporated into the code base. PB's insistence on bloating Data Object source with default syntax makes this task unnecessarily difficult whenever a Data Object hasn't been changed from earlier PB versions. To remedy, we open the original DW and immediately save it in a "diff" pbl used only for this purpose, then compare the changed Data Object against the "migrated, but unchanged" Data Object. It's a royal pain in the patootie.
  1. Helpful
There are no comments made yet.
John Fauss
John Fauss Accepted Answer Pending Moderation
  1. Thursday, 23 February 2023 20:26 PM UTC
  2. PowerBuilder
  3. # 2

Cool! If you Edit Source and change the setting to yes and use the DataWindow, does a rupture in space-time (or other cosmic phenomena) occur? wink

It'll be interesting to find out what it's intended to be used for.

 

Comment
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.