Index » PageStream Support » General » Tables - transparency |
Sign in to add a comment. | Pages: 1 |
2012-02-19 13:03:05 CT | #1 |
---|---|
Joseph Hogan From: Canada Registered: 2008-03-23 Posts: 25 |
Hello, I have been experimenting all weekend, and I have gotten to tables. I I read through the online manual, and figured out how to manipulate them.
Any ideas would be appreciated. Joseph
|
2012-02-19 19:37:14 CT | #2 |
---|---|
T.J. Zweers From: Netherlands Registered: 2006-02-07 Posts: 331 |
Hi Joseph, yes it can be done. Select the cells (one by one) you want to make transparent with the There you go. Next to the Fill button in the Edit Palette are T (Top), L (Left), R You are not planning to learn all of PGS this weekend, do you? Theo Op 19-2-2012 19:03, Joe Hogan schreef:
|
2012-02-19 14:23:54 CT | #3 |
---|---|
Joseph Hogan From: Canada Registered: 2008-03-23 Posts: 25 |
Hello Theo, Thanks! It worked. One note though. Why is it that when I pull up the same menu from the drop down menus, Thanks Joseph On 02-19-12 1:37 PM, Theo Zweers wrote: [Non-text portions of this message have been removed] |
2012-02-19 21:59:02 CT | #4 |
---|---|
T.J. Zweers From: Netherlands Registered: 2006-02-07 Posts: 331 |
Joseph, mmm, odd. I'm trying to learn a new (for me!) 3D program, Hexagon. Boy, does that Theo Op 19-2-2012 20:23, Joe Hogan schreef: -- |
2012-02-19 16:50:03 CT | #5 |
---|---|
Tim Doty From: United States Registered: 2006-02-06 Posts: 2939 |
Hi Joe, Tables are particularly problematic area of PgS: they are clumsy to use being more of exposing the underlying data structure rather than a polished user interface. A while back I was working on a script to improve on the situation (scripts in PgS can have GUI's), but never got that far and my time availability has dropped to nearly zero. Which is to say: IMO the best way of dealing with the table configuration issues is to have an improved interface built on top of PgS (at least unless/until Deron does something) and if you are planning on doing a lot with tables it might be worth your while to look into the scripting. Here's kind of a brain dump of issues you may encounter with tables: 1. tab does not move between cells. This is because each cell is a full-fledged text frame and thus can have tabstops for the text inside of it. Doing some macros for previous/next up/down cell bound to function keys may be useful for keyboard navigation. 2. Fill. You already discovered this one with respect to transparency, but if you wanted different colors for say a header row, footer row, that sort of thing it gets to be a pain going through each cell. 3. Stroke. If you want to alter the defaults for having lines between cells not only do you have to edit each cell, but each cell (being its own text frame) has its own border that can be stroked. 4. Adding/Removing cells. When you add a new column or row it doesn't change the sizing of existing cells/rows so if you sized the table, realized you needed another column and add it you have to go back and resize the table. 5. Resizing cells. This gets very interesting when you want to have a certain overall table size and are trying to get cells appropriately sized. The lack of click-drag controls is a real PITA. 6. Stability. PgS is *much* more stable than it once was when doing table operations (add/remove/resize), but it pays to save frequently when tweaking tables. Because PgS tables are so awkward I think it is a good idea to take a step back and consider what you are trying to achieve. There may be an easier/better way to do it in PgS even if a table would seem like the obvious solution. In particular, if you are wanting tabulated fields IMO using a text frame and tab stops is probably easier/better. If you wanted each field 'boxed' then you can do that by using a grid object placed over the text frame. If you need multiple rows per field -- that is a real PITA with a conventional text frame and tab stops so it would become a consideration. In cases where this has come up for me it has been easier to use a text frame and tab stops because text flow hasn't been a real issue in the cases I've had. But it is easy to see where it could be. If you are doing a mini-spreadsheet complete with calculations… well, that *is* something that requires tables. Now, I'm not sure what purpose there would be to using PgS for that instead of a spreadsheet and then importing the results (which is what I've always done since before PgS got tables) but there might be a good use case for it. Tim Doty On Feb 19, 2012, at 1:23 PM, Joe Hogan wrote: > Hello Theo, |
Sign in to add a comment. | Pages: 1 |
Index » PageStream Support » General » Tables - transparency |