Hello all,
Here are a few rules and limitations while using FPSDK created screens in ScreenMaker
- Create a new Project or open an existing project.
- Open Project Properties. Select the Advanced Tab.
- Add the FPSDK Assembly.
- The Assembly must be of type TpsForm and not of type TpsControl in order to appear in ScreenMaker.
- Inorder to add the screen, click on Add Screen button from ribbon tab.
- The Screen would appear under MyTemplates section. Select the item and click the OK button.
- The screen gets added into the ScreenMaker Project.
Rules to add Screen
- Screens created using SDK must be of the type TpsForm.
- When user sees the screen in Add Screen dialog and selects the SDK screen, instance of the screen is created. So creating a Controller object should be avoided in the constructor.
- For example: Controller controller = new Controller
- This tries to create a controller object, but is not detected as there are no controllers available by default.
o Due to the above reasons exception can be thrown.
o The controller can be connected based on the guid of the system
- Disposing of objects and handling exceptions must be taken care by the SDK project and must follow the SDK programming guidelines.
- If there is any change to made the FPSDK assembly, no need to remove the reference from ScreenMaker and add it again.
Limitations
- The controller connected in ScreenMaker project and controller present in SDK project, now part of ScreenMaker must be the same to prevent exceptions.
- Screens imported from SDK cannot be made as the Main Screen in ScreenMaker.
- The controls present in the screen created using SDK would appear locked and non ?_" editable in ScreenMaker. None of the properties can be modified.
- Any modifications to the position, layout, binding of the screens imported must be done in the SDK project and built to reflect the changes in ScreenMaker.