I have this setup (WPArea and palette subform) displayed on pages other than page 1 of forms using a subform. It’s not straight-forward though.
1. The subform initially displays a placeholder form. 2. The placeholder subform form method uses CALL SUBFORM CONTAINER in the On Load form event to trigger a custom form event. 3. The subform object method handles that form event to determine whether the user is in the 4D Write access group and uses OBJECT SET SUBFORM to load a 4D Write subform (32-bit mode) or 4D Write Pro subform (64-bit mode). 4. The On Load form event of the 4D Write/4D Write Pro subforms handles moving/stretching objects to subform container size. At this point the 4D Write Pro areas seem to initialize properly. When loading a subform this way, the sizing (grow, move) attributes are not handed on the initial display, so you’ll need to also have your own UI code that handles growing/moving objects. Also keep in mind the 4D Write Pro palette does not include options to open, save, or print documents, so you’ll probably need to add UI elements to handle those functions. One of the advantages of using a 4D Write Pro project-level form displayed in subforms like this is that you don’t have to duplicate those elements everywhere you want to use 4D Write Pro. Jim Crate > On May 13, 2018, at 6:28 AM, Randy Jaynes via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > Just a word of warning to prevent headaches for anyone else in the future. > > I just finished spending a few hours trying to figure out why the widget in > the ‘4D Write Pro Interface’ component embedded in v16R6 (and some earlier > versions of v16) wouldn’t work in my database, I finally tracked it down. > > The widget that includes both a WPArea and accompanying palette subform will > not work properly unless it is on page 1 for your form. > > It’s a timing issue. The On Load event in the WPArea object is defining some > pointers and trying to get a selection from the WPArea C_Object, but 4D has > not created the WPArea object yet, so errors occur in the On Load. > Unfortunately, this prevents any of the code in the palette subform from > working. > > So the short is, you must keep the objects in this widget on page 1 of your > form. > > I submitted this as a bug, but until it is fixed, keep this in mind. > > Randy > > ---------------------------------------------------------------------- > Randy Jaynes > Senior Programmer and Customer Support > > http://printpoint.com <http://printpoint.com/> • 845.687.3741 • PrintPoint, > Inc • 57 Ludlow Lane • Palisades, NY 10964 > Please send all email contacts to supp...@printpoint.com > <mailto:supp...@printpoint.com> > > > > > ********************************************************************** > 4D Internet Users Group (4D iNUG) > FAQ: http://lists.4d.com/faqnug.html > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:4d_tech-unsubscr...@lists.4d.com > ********************************************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
