Jump to content

normanicus

Members
  • Content count

    195
  • Joined

  • Last visited

Community Reputation

1 Neutral

About normanicus

  • Rank
    member

Profile Information

  • Gender
    Male
  • Location
    France/UK/New Zealand
  1. GetLayoutObjectAttribute() not working

    Apologies for being slow to report back. I recovered the file but it made no difference. I left if a couple of days and then thought to delete my Web Viewer and paste in the one from the test file Comment provided. It worked. So, it was the Web Viewer that had become dysfunctional, maybe corrupted. Thanks once again for your help.
  2. GetLayoutObjectAttribute() not working

    Went back to an old backup and found one that works. Did a Recover on the bad file and there were errors. Still the button didn't work. I'll paste your Web Viewer onto my layout and see what happens.
  3. GetLayoutObjectAttribute() not working

    Thank you. I tested your file and it works as it should. Copy/Pasted the 'Get Content' button to my file and changed the field to the one I use. Nothing. Chose another, non-global field on the same layout, nothing. So, as you said, something is going wrong. I never mentioned before but this was also failing on the client's computer so it looks like it is a corruption problem or similar. Your test has shown it is neither the browser or FM14 causing the problem. I'll try an older version of this file and then a 'Recover' and report back.
  4. GetLayoutObjectAttribute() not working

    I'm doing something like this: Set Field [ globalTextField ; GetLayoutObjectAttribute ( “Magento” ; "source" ) - where 'Magento' is the object name of the WebViewer. The contents of the Web Viewer is based on a URL stored in a field. I just put 'https://www.google.com' in that field and the Google search page appeared. Clicked the button with the above script step on it and the text field remains empty. When it is working I put the results into a variable and extract the page title. Let me know if more information is required.
  5. FM14, Mac Sierra, Google Chrome. I have set up a script to scrape the title from the page showing in the Web Viewer. This was working fine. Now I get nothing. One problem I solved. There was a message showing at the bottom of the web page referring to blocking third party cookies. I went into settings and allowed these. Still nothing. I was using the FM16 Trial which ran out so I reverted to FM14 Advanced. I think this may be the problem because, when running file from Soliant which demonstrates interaction with Web Viewer, each time I run script it opens FM16 telling me the licence has run out. In the Finder I changed the default opener for FM files to Filemaker 14. Still does the same thing. GetLayoutObjectAttribute is not exactly replete with error messages. Hopefully, I am just being dumb and somebody will put me right. Meanwhile I'm going through the hoop of trying to install the necessary packages in Python 3.6 so I can do this in Python. I know it's an aside but setting up Python in Sierra/OS X is not straightforward.
  6. FM 16 Variable Repetition limitation change?

    This may not be appropriate by why not use Get ( CurrentTimestamp ) as your repetition number? This, unless you are creating more than a window/second, is guaranteed to be unique, to be compatible with whatever version of Filemaker and has the benefit of being in historical order. As I said, maybe I'm missing the point.
  7. large transaction solution

    That wasn't meant as a dig at all. So, Consultant, if I've written something that could be taken badly, it was not meant. I have always thought since trying to wade through Marx, that one must be responsible for the consequences of what one writes so, I apologise. No, being on a Filemaker forum and involved in relational thinking we do tend to try to crack the nut with the hammer to hand. My reply was to suggest that there are solutions to searching massive data sets. I might be a bit odd but I almost never use Filemaker summary stuff. Without claiming to be an export the answer to speed and large data sets seems to be: data only fields (no calculations fields) Find Script to produce the report. I emphasise, I don't claim to be an authority, Norman
  8. Bash shell script to pull video frame

    I used this: BE_ExecuteSystemCommand Which is provided by the Base Elements free plugin. Description here: https://baseelementsplugin.zendesk.com/hc/en-us/articles/205350557-BE-ExecuteSystemCommand
  9. large transaction solution

    Consultant wrote "I am not aware of any system that can summarize millions of records on demand". Google?
  10. Is it just me?

    On OS X FM15 but, from memory, this problem has been around a while. In the Script Workspace when I try to edit the name of a script I get cast out of the editing process very rapidly. I click on the script name, it highlights but as soon as I start to type, no matter how fast, the cursor is ejected from the edit box before I can complete it. I resort to typing whatever I want in the Notes app and using copy/paste. This used to affect many more such edit boxes. I believe it is less now. I ask, "Is it just me?", as I don't see others referring to this irritation and expressing frustration as it not being solved after being around for so long. Maybe there is a trick I am missing. While I'm on the subject of the Script Workspace I find I can't see the line or lines I have highlighted. They are selected. This is not so on my client's computer so maybe I have a funny colour scheme?
  11. Script Workspace annoyances

    Apologies. I thought the ever vigilant moderator would block it if I was out of line.
  12. Script Workspace annoyances

    14.05 Advanced OS X 10.11.4 MacBook Pro (Retina, 15-inch, Early 2013), retina display Flashing still occurring. Now another problem has appeared. When I click a line of script it is not highlighted though it is selected. Worse, when I select multiple script lines, they are not highlighted. Anyone else getting this behaviour? When I try reporting this to Filemaker I get taken to the community site. I'm actually working with a later version (am I allowed to say that) so for Filemaker to accept feedback directly seems essential.
  13. Create a one record table. Create a calculation field that gets the 'ValueListItems' from the value list in question. Add any static elements you want in the calculation then reference this field as your value list. I'm a bit rusty but I think that should work. You could put the static items in a text field and add that to your list. That way the list is editable.
  14. Script Workspace annoyances

    I'm on 14.0v5. The option-tab works. Thanks. However, I can't remember another app where I had to do that. It's with existing scripts. While checking this out I noticed it is not now flashing. Just noticed that the grey 'fill in' parts of the workspace are slightly transparent. That's a relief as I noticed a red blur on the screen yesterday. Turns out it was a red button underneath the workspace. Then I looked closely and I can just see text. Is this normal?
  15. Script Workspace annoyances

    Hello, I'm working on a Retina Macbook with OS X El Capitan, FM14 Advanced. 1. I can't enter tabs in the edit window. When I try the cursor jumps elsewhere in the workspace. 2. I get flashing when in the workspace, like a screen refresh.
×

Important Information

By using this site, you agree to our Terms of Use.