Am using Pdftron Xamarin Forms for our Android Application for viewing and annotating pdf documents. How to set ToolManager.ReadOnly property by using ToolManagerBuilder class?
In order to set a document as readOnly you will have to set the DocumentEditingEnabled(false) property in the ViewerConfig.Builder.
Please see here for more information : DocumentEditingEnabled
Related
I'm trying to update the Vendor's Remit Address values from inside the BLC - but I can't find the view "RemitAddress" associated with those fields. I have a graph extension "VendorMaintExt", and I'm trying to use the syntax:
var remitaddress = Base.RemitAddress.Current;
But Base doesn't have a RemitAddress view showing in the intellisense in Visual Studio.
Where would I find this view so I can update the values?
In Acumatica 2022 version the remit address view is named RemitAddress in the DefLocationExt graph extension
vendorMaintInst.GetExtension<VendorMaint.DefLocationExt>().RemitAddress
I created a custom entity with a string property qst_type. I would like to change this property programmatically before saving. I think you should use the hook_entity_presave or hook_ENTITY_TYPE_presave. Unfortunately I can not change this property with this hook.
I have created an ActiveX control in VC++ 2012 using ATL. I would like to add a Font property and benefit from the stock property page that displays a font picker.
I have created a new control that has such a stock property using the control wizard. I've modified my code to reflect what I need to do to add the stock property. (I now implement ISpecifyPropertyPages; I have the relevant PROP_ENTRY_TYPE and PROP_PAGE entries in the property map) but when I attempt to display the property editor in the designer I get a 'Not Registered' type error.
I have ATL dynamically linked which, as I understand things, means I shouldn't need to link to any external DLL for ATL. However, where are the stock property pages implemented? Could it be that I don't have them, and need to register them somehow?
The problem you are perhaps facing is that stock property pages are hosted by MSSTKPRP.DLL and this component is not necessarily present/installed in Windows and is readily available. I would suggest not using stock property page and implement your own to avoid the troubling dependency.
See also:
Is there a x64 version of MsStkPrp.dll
Redistributing ATL and OLE DB Templates - at the bottom
I've told a view to open using an XPage, but how do I open that XPage in edit mode?
I will suggest that you buy and read the Mastering XPages book to learn the basics of handling views and documents in XPages. The book contains material that describes exactly what you are looking for (how to open an XPage in read and edit mode).
I will assume your question relates to the XPage being used to open the selected document from the view and not the view itself as it is not possible to either define an XPage to to launch a view or for a view to be in "Edit Mode"...
When specifying the document data source for an XPage it is possible to define the default action as being Edit Document or Open Document. This sets the "action" property of the data source
The XPage itself has a "readonly" property that can be set to a specific value or computed. This is not tied to a specific data source.
It is possible to add a panel container control to the XPage and set the "readonly" property of the panel. This will allow all the controls inside the panel to be rendered as editable or readonly.
views and xpages cannot be in edit mode, only document data sources can be in edit mode.
In addition to the readonly properties that Peter mentioned:
It is possible that a custom control got its own data source while the one from a parent (e.g. the xpage) is in edit mode. That's the mistake i make often while binding controls to data fields.
I have a custom web part that has custom properties. To Edit the properties I have a custom EditorPart.
I need these properties to be able to be exported with the webpart. To do so I have to set the WebBrowsable attribute to true which makes the custom properties show up twice in the editor pane once with my editor part and my custom validation and once automatically.
Is there a way to get the properties to export with out setting WebBrowsable to true?
You might want to try setting the ExportMode property of your WebPart
There is a good explanation on MSDN here
http://msdn.microsoft.com/en-us/library/system.web.ui.webcontrols.webparts.webpart.exportmode.aspx