As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
The method suggested by Francis is one I would recommend you follow up. The way that the VAXIS and HAXIS settings are used will resize your overall graph area as you have requested.
If you are content with the overall graph area sizing and you want to change the rectangle in which your graph is plotted then I would recommend downloading a copy of the Graphing Manual (check tech documentation link above) and search out the method setRect, which has the syntax "setRect(object ,new Rectangle(VC left,VC top,VC width,VC height));". This manual should be invaluable to you if you are going to be concentrating on producing graphs.
T
In FOCUS since 1986
WebFOCUS Server 8.2.01M, thru 8.2.07 on Windows Svr 2008 R2
WebFOCUS App Studio 8.2.06 standalone on Windows 10
Posts: 5694 | Location: United Kingdom | Registered: April 08, 2004
Tony A is right about the manual being very helpful but only to a point. It helps document the individual functions but it's weak in seeing how the functions work with each other and how they fit into the overall FEX. Complete examples instead of code snippets would go far in solving this problem.
I was trying to develop a simiar dynamic graphing capability except I wanted to size based on the actual number of datapoints. This didn't seem to be possible with the graph engine but might have been possible with a pre-pass of the data (to calculate the optimum size) and then a call to the actual graph functions. I ran out of time and never got back to it so our graphs are kind of sloppy looking at the datapoint extremes.
I think if you check out the first link in Kerry's post you'll see a possible solution towards the end of the thread.