![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
FMP Adv. 11, both platforms: I wonder if there's a setting I'm overlooking that would make the left-hand column in table view disappear? This is the column with the arrow that shows which record is active. I don't need it, and I'd rather have the extra pixels horizontally. Anyone know if there's a way to turn it off? Thanks, -J. |
)
#3
| |||
| |||
|
#4
| |||
| |||
|
|
Hi, Harry - The arrow column in Table view is new as of FM 10 (if I remember correctly). List view loses three pixels on the left side; Table view loses 16. When designing databases, I like to create layouts for each of the main tables in all three views, since each offers features that the others don't. For instance, in Table view users can change the width of fields and move fields around while still in Browse mode, whereas in List view they'd have to enter Layout mode to do the same thing. The issue is basically that in my designs I create an area at the top of the screen that provides navigation to the main tables along with buttons for commonly referenced functions so the database becomes more of a freestanding app than a program where people have to learn FM to use it. When clicking the List button, everything shifts 3 pixels, which feels jerky. To counteract that, I subtract three pixels from the header area and shift everything left by the same distance to make the transition smooth. When clicking the Table button, everything shifts 16 pixels. If I subtract 16 pixels and move the elements that much leftward, the header appears to stay in place when moving from Form to Table -- that is, it's not jumpy, so less disconcerting for users -- but it means having 16 pixels to spare to begin with, plus a little extra space to give things room to breathe. In Table view this looks fine, but building in that much padding in Form view -- say, 20 pixels altogether -- means a lot of dead space relative to how other elements are arranged at the top. To keep the aesthetics, it would be better if I could just turn off the arrow column, especially because it doesn't add much functionality (even the right-click context menu is pretty slim) and it's not necessary for letting users know which record they're on if field frames are being shown when the record is active. So it's strange that the FM designers would add something that takes up so much room and not offer a way to hide it. But so far I haven't found the off switch anywhere. |
)
#5
| |||
| |||
|
#6
| |||
| |||
|
|
Yeah, I think you're right. I redesigned the button bar to give extra padding for table view. It actually looks okay. Looks pretty normal, really. I'm actually a big fan of Table view. It gives users a list view in which they can resize fields and rearrange them if they want to compare data side by side. In fact, I almost began to think this time around that I should do away with List view and just have Form and Table view, since the only thing Table view doesn't offer is layout objects, which I use in limited quantities in List view anyway. Just my two cents. Thanks for your input. -J. |
#7
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |