![]() ![]() Keep in mind that with WebDirect a LOT of the processing is done on the server and this can mean that you need to make sure your server has enough horsepower. It's all or nothing for that particular object. In other words within a single text object on a layout you can't suddenly turn to italics for a few works. ![]() You can't have multiple STYLES inside the same text object. Use custom styles to format pretty much everything. ![]() you can't have a Print button that instead saves as pdf if user alt-clicks). The Get(ActiveModifierKeys) function doesn't work either, so those buttons will need to offer options explicitly (i.e. Keyboard shortcuts (say, Cntl-N to create a new record) don't work in WebDirect, so you have to create buttons for more or less everything your users will need to do. Basic advice here: WebDirect likes simple layouts. For example, WebDirect does not like it when objects overlap. As u/McDeth already pointed out, do NOT assume that your layouts will work well. In addition to the stuff that doesn't work at all in WebDirect there's a lot of stuff that doesn't work very WELL. The onLastWindowClose script trigger doesn't work if a user simply closes the browser window, so you have to work hard to encourage users to click the logout button that you provide rather than just typing Cntl-W. Card windows were not supported until the recent release of FileMaker 19. (Table view isn't supported in Webdirect at all. Keep in mind that some features of FileMaker Pro the client app simply are not supported in WebDirect. Feel free to contact me back channel but here are a couple of quick points. Been working this way for a couple of years. I have a large number of users at many different firms and 100% of them use a browser to access the apps. ALL of my FileMaker apps these days are deployed via WebDirect. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |