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 ... 3 4 [5] 6
61
Nomads / Re: titlebar has impact on resize actions
« on: November 15, 2018, 09:19:45 AM »

Thomas,
  • Here is a quote from the Custom Title Bar Display section of the Custom Title Bars documentation:
    Quote
    If the standard Windows title bar is replaced using a caption-less frame style (see Frame Style above), certain Windows behaviours that are dependent on the caption bar will no longer be available or will be available in a different format. For example, the custom title bar will have no indication to show which panel is active, unlike the Windows caption bar that is dimmed when inactive. In addition, double-clicking the custom title bar will not maximize/restore the panel, nor will moving the panel against the top of the screen. Finally, moving the panel by clicking and dragging the Windows caption bar will be replaced by implementing full screen drag (see Full Screen Drag), which allows you to move the panel by clicking and dragging any blank area of the panel.
    Continue to use the Windows caption bar with your custom title bar to retain these features.
  • Depending on the type of frame is chosen for the title bar, Windows does not support re-sizing for all of them, so PxPlus had to add re-sizing logic to the right, bottom and corner edges to handle it. The sensitivity of the grabbing the edges to resize is slightly different, but is still there. If you use the Windows caption bar with your custom title bar it will retain the Windows resizing characteristics.
  • Maximizing PxPlus panels may not be exact, as the panels width and height are integral and are rounded to the nearest line/column. I found no difference in the size of the maximized panel whether it had a Windows caption or not, and whether it had a custom tool bar or not.



62
Nomads / Re: change caption using titlebars
« on: November 08, 2018, 08:42:37 AM »
Thomas,

If you have to PRINT 'CI', just do it prior to changing the caption so it doesn't swallow the -1109.

As for the merge-jumpto option, that is used for concurrent windows, and the Custom Title Bars documentation notes explicitly at the end of the Assigning Custom Title Bars section:

Important Note:
If a title bar has been assigned using any of the above methods, it will not be displayed on panels that:

  • Have been defined as Widgets,
  • Have Auto-Scroll Resizing set,
  • Are concurrent windows
  • Are not wide enough to display the title bar.

63
Nomads / Re: change caption using titlebars
« on: November 06, 2018, 01:17:57 PM »
I would not arbitrarily remove the 'ci' from statement 2473 in *winproc.
There is a Nomads variable called NO_FLUSH that you can set to 1 to avoid the buffer flush at 2473.

64
As of July 2018, if you are not a client of the Google Maps APIs Premium Plan, Google requires you to have a Google Maps API Key to do development using the Google Maps APIs. Without an API Key, the maps and their features are still functional, but the map display is darkened and displays a "For development purposes only" watermark. Also, a "This page can't load Google Maps correctly" message box is displayed. To display the maps cleanly, you must obtain an API Key from Google, and apply that key when using the PxPlus Google Maps interface.


For information about obtaining a Google Maps API Key, go here:
https://developers.google.com/maps/documentation/javascript/get-api-key
(Be sure to activate it for Maps and Routes.)


Once you have a key, you must apply it to the PxPlus Google Map interface. As of PxPlus 2018 Update 1, the PxPlus Google.Maps object has an APIkey$ property which you can set to do this. This can be set in one of two ways:
  • Set the APIkey$ property in the NOMADS map definition in the COM Control Properties interface. The API Key for each client will be different, so an expression would most likely be used to supply the value for the APIkey$ property.  This would have to be done for each map definition.
  • Leave the APIkey$ property blank in the map definition and simply load the %GoogleAPIkey$ variable with the API Key value prior to displaying any maps (such as in the START_UP program). The PxPlus Google.Maps object will retrieve the key value from this variable and set the APIkey$ property automatically without having to change any definitions or code.
Your maps should display cleanly once the API Key is in place.

65
Nomads / Re: change caption using titlebars
« on: November 02, 2018, 10:37:58 AM »
Thomas,
I'm sorry to say that I cannot duplicate what you are describing in v14 or v15.


I created a panel with Post_Display logic that does PRINT 'CAPTION'("new title"),
I process the panel using PROCESS "mypanel","mylib" and the title in the title bar changes.


I also created a panel using a Nomads object that does PRINT 'CAPTION'("new title") in the POSTLOAD() logic.
I instantiate the object and process the panel with myobj'Process(), and the title bar changes.


The way it works is this:
IF there is a title bar on the panel, the SignalCaptionChg option is set to -1109. This means that whenever a PRINT 'CAPTION'() is executed a CTL value of -1109 is generated.
When the -1109 CTL is detected, the new caption is retrieved using a MULTI_LINE READ 0, and the result is redrawn as a font image.
All of this should happen automatically if you have created a fonted text control called PX_TitleBar_Caption on your title bar.




66
Nomads / Re: change caption using titlebars
« on: October 29, 2018, 12:10:09 PM »
Thomas,
The title on the titlebar is displayed using a fonted text control called PX_TITLEBAR_CAPTION. You can change the panel title using:
PRINT 'CAPTION'(dte(0:"%Hz%mz%sz")),


Do not use a multi-line. We have an internal variable called PX_TITLEBAR_CAPTION$ that we manipulate when the title bar is changed with the PRINT 'CAPTION'() mnemonic.


The concept is that your old code which would have changed the window caption with a PRINT 'CAPTION'() still works with a title bar.

67
Nomads / Re: change caption using titlebars
« on: October 29, 2018, 08:34:54 AM »
Thomas,
Changing the caption of a panel is the same with or without a title bar:
PRINT 'CAPTION'("New Title"),


68
Nomads / Re: Query problems!
« on: October 18, 2018, 01:42:15 PM »
I have seen this type of error occur when the *providex.ddf does not get updated properly during installation. This can happen if the file is open when the installation occurs, or if PxPlus is installed over top of a previous Providex installation. My suggestion is to re-install the PxPlus in a new location.

69
Programming / Re: Chart Colours
« on: August 24, 2018, 03:37:51 PM »
David,
Check if you have colors set in the Chart Presets, as they will take precedence over the colors in %nomads'chart_colors$.

70
Programming / Re: Chart Colours
« on: August 24, 2018, 02:03:23 PM »

FWIW, there are several ways to control the colors used in a chart. They can be set in the Chart Presets, or using the global variable %Nomads'Chart_Colors$, and via a template file in iNomads. Here's the url for the doc:  https://manual.pvxplus.com/PXPLUS/Charting%20Alternatives%20in%20PxPlus/Colors/Overview.htm

71
Nomads / Re: Logic with Numeric Multi_lines
« on: August 17, 2018, 11:07:32 AM »
James,
It's a good thing you beg to differ, since after looking at the code I discovered that my assumptions were wrong, and you are right.


BTW, *winproc only maintains the one value.

72
Nomads / Re: Logic with Numeric Multi_lines
« on: August 17, 2018, 08:54:10 AM »

James,

When a File Maintenance panel is generated, the controls for numeric fields are generated as string fields. There  are conversion routines (NUM_TO_STR, STR_TO_NUM) to keep the numeric field and its control string field synchronized. Whenever the record is read, the string field is synchronized, and whenever the user changes the field in the control, the numeric field is synchronized. If the field value is changed by the user entering data or by browsing, etc., the fields are synchronized, so it doesn't really matter which one you use.
However, if you are changing the value programatically, it is important to keep both synchronized, so you should set them both.

73
Nomads / Re: Logic with Numeric Multi_lines
« on: August 16, 2018, 11:00:44 AM »
James,
If you want to effect a change that will be reflected in the control on the panel, use the control name. (This value will then be converted to the record field in the Str_to_num, so you're covered.)

74
Nomads / Re: Dictionary
« on: August 07, 2018, 08:52:28 AM »
  • When defining the data dictionary for a file in Dictionary Maintenance, select Expression for the Physical File and build the expression for the file name using your global variable, e.g. %Company$+dlm+"filename". You can set the value for the global variable in your START_UP program. Alternately, you can use a fixed simple name for your file, and set up File Search Rules using the PREFIX directive to find the file when it's opened.
  • Again, you can determine which files are used by looking at the search rules you have set up with the PREFIX directive.
  • Information on defining keys for a dictionary file can be found here.

75
Programming / Re: File maintenance panel creation for flat files,
« on: July 26, 2018, 09:03:19 AM »
There are two steps to defining a file in Data Dictionary Maintenance. First is creating the file definitions, consisting of file attributes, elements and key definitions. This meta data is stored in providex.ddf and providex.dde files. Second is applying the definition to the file, i.e. pressing the Update File button which creates the file and keys and embeds the definition right into the actual physical file  It is only after both steps have been completed that the physical file can be processed properly.  As you found, after you pressed Update File you were able to generate the File Maintenance panel.


As for the error 55, try doing a LOAD "*win/flmaint" to see if you have access to the file.

Pages: 1 ... 3 4 [5] 6