PxPlus User Forum

Twitter Twitter Twitter

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Jane Raymond

Pages: [1] 2 3 4
Programming / Re: Radio Button Properties
« on: May 17, 2022, 11:52:39 AM »
If your radio buttons are called rb, then you can check the individual properties by setting the id property to the button index:
PRINT rb.ctl'enabled

Programming / Re: Report Writer Passing .pvr argument
« on: May 03, 2022, 08:59:38 AM »
I opened the report as instructed. The blue triangle in the left corner of the row header cell for the line tells me that the row has variable line height. If I click on the Note$ cell to highlight it, then right click and select Bulk Edit Cell Format, then the display indicates that Word Wrap is turned on for that cell.

What may be confusing things here is that if you right click on the cell and select Cell Format, then Word Wrap, there is no indication whether Word Wrap is on or off. Similarly, when you right click on the row header and highlight Variable Line Height, there is no indication as to the current setting. We enhanced the menus in PxPlus 2021 to add checkmarks to the menus to indicate current selections for the current cell. (If multiple cells are highlighted, checkmarks may not appear if the selection is not consistent across the multiple cells.)

Programming / Re: Report Writer Passing .pvr argument
« on: May 02, 2022, 02:08:41 PM »
Looking at the .pvr file, the Detail L1 is set to variable height, and column 17 of that line (with Note$) is set to word wrap.
Using PxPlus 18.20, I loaded the report definition into the Report Designer. When I checked column 17, word wrap was turned on and Detail L1 was set to variable height.
So I cannot duplicate what you have found.

If anyone can shed further light on this issue, please respond.

Programming / Re: Report Writer Passing .pvr argument
« on: May 02, 2022, 11:20:59 AM »
Does the cell with the word wrap have anything in it? If it is empty, the word wrap setting will be ignored. And if there are no cells with word wrap in a line, then variable line height is ignored.

If the above is not the case, then please refer this matter to our helpdesk:
Let us know the version of Pxplus that you are using, and if you could supply a sample .pvr file it would be very helpful.

Nomads / Re: Picture in TitleBar
« on: March 14, 2022, 09:16:55 AM »
Attached is an exported library text file titlebar.txt that you can import to a new library.
It contains a titlebar with a centered image.

Nomads / Re: Picture in TitleBar
« on: March 11, 2022, 06:28:36 PM »
Sorry, I did mean titlebar, not toolbar.
How is the panel sizing set? And how is the resizing for the image set?

Nomads / Re: Picture in TitleBar
« on: March 10, 2022, 03:32:15 PM »
To get an image centered in the toolbar, I did two things:
1. For the image, I defined the Image Format to be Centered (preserve aspect ratio)
2. I set Panel Sizing to Resizable/Custom, and set the image control have Stretch sizing.

Programming / Re: Check for damaged files
« on: November 18, 2021, 08:58:56 AM »
This is not a total solution, but you can use the *dirtree utility to walk a directory tree and return a list of files. (The program is self-documented if you list it.) You can then loop through the file list, opening the files and using the FIB() function to determine their type, and go from there.

Programming / Re: Error 99 in *plus/proj/pathinfo
« on: October 20, 2021, 03:03:28 PM »
Yes, turning off the flag the flag and updating should work, but switching the flag will make it attempt to update the non-existent SVN version one last time.
The issue for me is that the error 99 should not have occurred, so I have to fix that.
Our helpdesk is at:

Programming / Re: Error 99 in *plus/proj/pathinfo
« on: October 20, 2021, 02:42:06 PM »
Data files can be set to Convert to text for the Version Control system in Data Dictionary Maintenance. When such a file is changed by writing/deleting records, etc. when the file is closed it attempts to update its SVN source control version. The error you are experiencing is in the logic which determines if an SVN system exists. Could you please create a ticket on our HelpDesk for this issue so that we can better track it?

Language / Re: Nomads Adding Security Class to Control
« on: May 03, 2021, 03:54:54 PM »
You didn't mention which version you're using, but I think that as of PxPlus 2016 Upd1, you can change line 4240 of *winproc.dsp to:

4240 IF _ORIG_H<=1 AND _OBJ_QRY$<>"" AND POS("h"=_OBJ_STS$)=0 THEN GOSUB Do_Query_Button

Language / Re: Nomads Adding Security Class to Control
« on: May 03, 2021, 03:33:39 PM »
Yes, we have fixed this for the upcoming release.
I'll track down the code changes and post them.

Wish List / Re: lock file only if required
« on: April 01, 2021, 09:25:12 AM »

We have looked into this issue since you first requested it last year (c.f. Wish List - *dict/dd_updt)

We analyzed both *dict/dd_updt and *dict/maint to determine if files were unnecessarily locked during the physical file update. What we found was the following:

- Files are not locked during the analysis.
- If a file does not exist and is created, it is locked when it is open. This is a non-issue, as it did not previously exist and could not be accessed by any other session. (The lock is necessary for password processing.)
- If a file exists and just requires updating the internal dictionary, it is not locked.
- If the file requires conversion, it must have exclusive access to do this as files must be renamed and erased. The file is locked to check for exclusive use, and conversion does not occur if it is not available.

No changes were required for any of the above.

One issue we did change occurs in *dict/maint:
If a file with no records is busy, the physical update was not allowed to proceed. We changed it to proceed in case just the internal dictionary needs updating, and no conversion is required.

This change will be in the 2021 release.

Nomads / Re: Copy IT Editor colours
« on: March 30, 2021, 09:49:54 AM »
The IT Editor colours are stored in the pvxedit.ini file.
On my Windows machine, that's found in C:/Users/YourUserID/Appdata/Roaming/PxPlus/pvxedit.ini

Nomads / Re: Error 41 in _winproc.dsp
« on: January 25, 2021, 09:05:56 AM »
This issue has been reported previously and fixed. The update is slated for the next release.

Pages: [1] 2 3 4