I have built a NUP 7 Datawindow SQL Server Select with a TOP 42 custom select statement to always return only 42 results.
At first, I removed all of the columns on the freeform styled NUP and added 7 computed items each with a custom BITMAP call to display 1 of 3 possible images in the 42 tiles based on data results returned.
Then in the mouse event I was planning to mouse over and then change the hovered on column "cell" so we could force the computed logic to change the image dynamically cell by cell. Yeah, didn't work out.
Appears that for NUP datawindows you cannot reference any 'peripheral' objects dropped on the datawindow to a specific row,
only actual database column objects will be detectable in datawindow event scripts using dwo.row because I guess technically their not part of a row result set, so that went out the window.
Is there a way to do this another way I dont know....
PB Devs : I wish we could have a separate property available to any object that can be dropped on a NUP datawindow that could be manually set.
The property would be numeric, and attach that object to a specific 'row' in the NUP which could be set by the properties screen somewhere or in script.
This would let me assign a bunch of different objects that should be attached to row 1 or row 5 of 42 as if they were 'row 1' or 'row 5' objects.
So that for example in pbm_dwnmousemove event the dwo.row during a mouse over on that peripheral non-database column object would return that special value row #.
To ensure original datawindows returned the original value, if this value is not set or is 0 pb could return the original number using the original dw logic. (IE: Returning the row # the peripheral object was placed on not the actual row # of the database)
