Schedules in Layout

Dave R · 7 Oct 2013, 13:29

Yes, Kim, I agree, it would be nice to be able to create tables directly in LO but I don't have any trouble with RTF files either. I use tables in the majority of my LO projects and as long as I don't try to edit the table in LO, they are fine.

Krisidious · 7 Oct 2013, 14:33

I can just copy and paste out of excel and it brings the table with it.

Dave R · 7 Oct 2013, 14:44

If you do that, though, can you edit the table in Excel and update in LO (in the same way you can edit a sketchUp model and update the viewport? If you import the table as an RTF file, you can go back to the text editor, edit, save and the text is updated in LO.

MendoWill · 19 Dec 2016, 02:28

@dave r said:

... If you import the table as an RTF file, you can go back to the text editor, edit, save and the text is updated in LO.

This is where I'm having a problem, my table won't update in Layout. I created it in Word, saved it as an .rtf file, and successfully inserted it into Layout. The formatting was funny, but I was able to correct it easily.

I still can't update the table in Layout. My method is to edit the Word document, save it, overwrite the .rtf file, and then update the document reference in Layout. Layout will show the reference as "old", then show it as "current" afterwards, but the table itself does not actually change. I've also noticed that if I click "purge" the .rtf reference will disappear from my Document Setup window list, as if my inserted .rtf file is not actively linked to the document reference...

Any insight would be greatly appreciated, and a solution will be rewarded with beer when you visit my town.

Thanks!

MendoWill · 19 Dec 2016, 02:50

Just did some testing, the problem I describe above only arises after I edit the .rtf inserted table.

For example, if I insert a .rtf table, it will update as expected for a Layout document reference. But as soon as I give it a fill or "stroke" border it behaves like an independent shape and will not update with its reference document.

I cannot simply leave it in raw form without giving it a fill, it is ineligible.

Dave R · 19 Dec 2016, 12:08

Yes. This is the case. If you do anything to the text box in LO, (except resizing it with the handles) it disconnects from the original RTF file. Requests have been made to maintain the connection so borders and such can be added but that change hasn't been implemented yet.

If it's just a fill or a border, consider using a rectangle with fill and stroke placed under the text box. You could also create a grid under the text box if you need. I'd put them on separate layers, too.

@unknownuser said:

I cannot simply leave it in raw form without giving it a fill, it is ineligible.

why does no fill make it ineligible? Inelgible for what?

Do you mean illegible? If so, why is that? What is behind the text box that makes it impossible to read the text?

pbacot · 19 Dec 2016, 17:45

I'd rather that excel "print areas" are referenced in LO just like graphic files, rather than doing the tables in LO. Use the best tool for the job instead of trying to cram the program with more half-assed tools.

Dave R · 19 Dec 2016, 17:53

I agree to a point. I really don't have any problem importing RTF files into LayOut. I don't like grid lines, though and prefer to do the major formatting in Word or another text editor instead of Excel. I expect the new Tables feature in LO2017 is sort of the tip of the iceberg. I wouldn't be surprised if they are able to add a bunch of features that make use of auto text and direct links to the SketchUp model much like Labels can now.

pbacot · 19 Dec 2016, 17:59

Actually I don't know how to make RTF from Excel. I would just print a pdf and reference that in LO, if I needed to.

Dave R · 19 Dec 2016, 18:09

Copy it over to Word and use File>Save as...

At least with the RTF, you can go back to the RTF in Word and edit it to make changes. It's like modifying a SketchUp file or an image you might have in the LO file.

pbacot · 19 Dec 2016, 18:14

Right. But there's still a disconnect from the best source, the Excel file. My method is similar. You still have to output from Excel but it just prints to the same pdf which is linked. In word you still have to open and save the rtf. Almost the same.

Dave R · 19 Dec 2016, 18:18

Yeah. But since you can't import a PDF in the Windows version...

FWIW, you can insert an .xlsx, .csv, or .tsv file in LO2017.

pbacot · 19 Dec 2016, 18:53

@dave r said:

Yeah. But since you can't import a PDF in the Windows version...

FWIW, you can insert an .xlsx, .csv, or .tsv file in LO2017.

I'll have to try that!

MendoWill · 20 Dec 2016, 01:59

In response to Dave R:

Thank you for the clarification, and the suggestion of a box behind it with the fill and border to give it some definition, that is a good idea!

I meant "illegible", and it's because of the fine black lettering on gray background, which I realize now could not only be changed but also prints clear on your paper (which is probably white) anyways.

Dave R · 20 Dec 2016, 02:11

@mendowill said:

In response to Dave R:

Thank you for the clarification, and the suggestion of a box behind it with the fill and border to give it some definition, that is a good idea!

I meant "illegible", and it's because of the fine black lettering on gray background, which I realize now could not only be changed but also prints clear on your paper (which is probably white) anyways.

Question regarding the gray background. Are you putting the text box out in the gray region around the white rectangle?

If you are, the text will be very difficult to read in the PDF or printed exports since the white region represents the paper space. Anything outside of that area is ignored for exports. In other words, content out in the gray area won't be printed.

If the text is difficult to read in in the white paper space, you should probably switch to a large or more easily read font.