Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

problem: extra pixel between parts in 7.0v3


This topic is 7264 days old. Please don't post here. Open a new topic instead.

Recommended Posts

  • Newbies
Posted

I've just installed 7.0v3, and discovered that if you expand a part (header, body, footer, etc.) temporarily to work with something in the part, then try to reduce the part back to its original size, it makes the part one pixel larger than it originally was.

The great majority of my layouts have objects that appear to continue across multiple parts. This new system creates a one-pixel-wide horizontal white line between parts, which obviously is a huge problem.

Does anyone know if there is an easy way to get FM to act like it used to? If not, what other methods are there to solve the problem without going through a ton of laborious single-pixel moving of objects?

Posted

I am not sure if this is related, but reducing the part (by dragging) always ends up 1 pixel shy of what the part can be. I find the best way to reduce a part is to type 1 in the height reference of size box. The layout will then reduce as small as is genuinely possible.

Cheers, Peter

  • Newbies
Posted

Cool... this workaround works. But it's still one more step each time than the way it used to be in v6. Any idea why this got changed? And any FM people listening here who know if there's a chance the problem might be corrected?

Posted

No idea, I have just migrated from FileMaker 5. Version 7 really is cool, but there are some very strange things that do go on. Hopefully 7.0v4 will fix them all!

Cheers, Peter

This topic is 7264 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

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