I have a 2-column SWT Table that uses TableViewer. Trouble is that I can only select (and edit) cells in the first column -- clicking on the second column does nothing.
I read from somewhere (lost the link) that there's no easy way to get such functionality (!) -- you're supposed to mess around with several extra concepts if you want to select (and edit) different columns in your table.
This snippet
(http://www.goneeded.com/snippet/eclipse/JFace/Viewers/Snippet035TableCursorCellHighlighter.html)
seems to be relevant, but it's not clear which part of it is necessary and it has depenendencies to other snippets. I tried to get it working but it did nothing.
Seems that new table editing and cell-selecting features were added in Eclipse 3.3 -- is there a tutorial or smth available on how to use them? The snippets are too cryptic for me.
You should be able to edit and select cells independently. You might have the SWT.FULL_SELECTION style bit set on the Table constructor. That forces every selection to span the whole row instead of a single cell.
I'd check out this tutorial for more on TableViewers:
http://www.eclipse.org/articles/Article-Table-viewer/table_viewer.html
Related
Using MySQL Workbensh 6.3.7 on Windows 10, I am finding the search behavior strange.
There is an entry box that you could use to enter the name of the table, however, this does not work every time! I mean it sometimes finds the table and sometimes it does not! When it works, it is very good. I can enter 1 or more chars from start and the tool would highlight the table in the diagram, for some tables, even entering the full name, it does not find the table!
If I go to a specific table from the tree on the left-hand-side nav, and double click the table, it opens its properties, but it does not select it on the drawing area!
I have generated the DDL and searched it as text to find columns and relations then traced that back manually but this is difficult for large diagrams.
I want to be able to search for a table (even with wild card) and find it in the drawing surface - Also, what does the dot at the right side of the table name in the schema treeview mean?
The search behavior sounds like a bug to me. It should always select the table figures that match. When you file a bug report for that (http://bugs.mysql.com) it can be fixed.
The dot in the catalog treeview is just an indicator which db object has been placed already on the current diagram.
A tip: use layers to organize bigger diagrams. Use colors for different groups of db objects, like this:
You can change the colors on the Properties tab in the lower left corner, even for multiple figures in one step.
And don't forget you can increase the size of the diagram to fit more figures on it. See the menu Model -> Diagram Properties and Size....
I'm operating in Word 2013 and 2010, so I can use code that works in either. I'm trying to create a word document to keep track of my recipes. At its most basic I want to have a TOC that updates based on headings. I also want it to have any category I want (eg: Appetizers, Drinks, Entrée, etc...) ordered alphabetically. Under each category I have tables. Each recipe gets a table that has it's name, directions, notes, tags, and potentially a picture. The second cell has another two column table inside of it that contains the quantity and name of each ingredient necessary for the recipe.
I have all of that so far and I'd like to automate adding new categories and recipes. Currently, I have to find the category, then scroll down to find where the name goes alphabetically and insert a quick table I made. I then fill in the info.
I'd like to be able to search the document for each category name, then insert the new category wherever it belongs, with a space before and after it. I found that my tables give me trouble if I don't have a space between everything. It tries to pull anything it's touching into the table and merge them.
I wanted to give the backstory, so you'd know where I was going to go eventually and could provide help that fits better with what I need. After I can add a new category, I plan to use vba to organize each table alphabetically by the name in the first cell of each table. It will also help when I start adding sorts to it. Eventually, I'd like to be able to sort it to say, only display recipes from a certain person, or display my frequently used recipes. I'd then have it either hide all the others or create a new doc with just these. So thanks for the help. Below I'll post the code I most recently tried. I tried a few other variations of this same code and keep getting an 'expected end of statement. I've gotten other errors when trying other variations of it, but this is the best I can come up with on my own.
Private Sub UserForm_Initialize()
For Each cat In ActiveDocument.Styles = "Heading 1"
lstCat.AddItem (cat)
Next
End Sub
I have a form called frmAddCategory I'm using as a test. I was going to have a listbox lstCat to show every category with the style heading 1. I have a textbox called txtAdd to type new ones and a cmdAdd button to add it to the form.
Edit: I've been playing around with my macro recorder after finding out about outline view mode. I set it to show only 'heading 1' level and selected the ones I wanted, not selecting the appendix or reference. Then I went to the home tab and sorted paragraph by ascending alphabetical order. I got some code I believe I can use to get it to run in VBA. However, it's not a complete fix as I don't want to select the last two with heading 1. It also works if I manually select the tables under each heading 1, but I can't set the spacing before and after. I'd like each heading and the tables under them to have a space or two between each for looks and editing purposes.
Also, if someone is going to give my question a negative rating, then please post a comment explaining. As far as I can tell from the faq about the forum and the other questions I've seen, it is a well posed question. A clear title, a good explanation of the problem, code examples, research. So if I am doing something wrong, please inform me, so that I can correct it.
first thanks for your bit about macro recorder and outline mode, I have been trying for long time to fill a list box with selection.text between two HeadingLevel(1) headings.
now to yours, sorry I can't think of way to do in word. BUT it would be real easy in Access. one table of categories like called tblCategories another for recipes tblRecipes. To make real easy, when the use autoID on ALL tables. But to avoid LOTS of headaches for tblRecipes rename its autoID to RecipesID same for other tables. in table of recipes you can use a memo field to hold large amount of data. the spot for text in Heading would be put in one field of the tblRecipes. once you have tables looking to have a field for each item you want to track. hit save, then use wizard to create a form based on table. repeat for all tables you want to have it real easy to put info into any table.
1.reportTOC based on query of Every Heading you want, can preview or print as want. reportByCategory and so on reports are sorted a to z unless you want to sort by Owner, then recipe all auto sorted a - z.
report wizard to get hard copy. if you want to sort real easy, built in. also if want to be able to pick all recipes for a holiday real easy, one table tblHolidays. one tblHolidayRecipes fields autoId (not used by you anywhere but needed), fldRecipesId (holds RecipesId) , fldHolidayId (holds HolidayId). the wizard will show how to get only what you want. in access 2013 you can include pix of food or.
TinyMCE editor seems to lack the capability of applying table cell properties to the whole table column (which would be much less trivial problem, than applying to the whole row - that functionality is there).
Is there a working soultion for that (patch, plugin..)?
i have a JFace table-viewer, which consists of large number of rows, i thought that it would be better if there is a short description for each row,as a workaround i was trying to implement doubleclick listner but that's not apt to my need,i don't know if there is an event like hover for this,which shows a tooltip containing a brief info about the particular row.
The answer to this question depends somewhat on the exact implementation of your table viewer. Having said that, the primary options are:
Add a MouseTrackListener to the underlying table
Add a SWT Listener for SWT.MouseHover to the underlying table
If you use a CellLabelProvider, have a look at the various getToolTip...(Object) methods
For the first two, you have to figure out the row element yourself - look at event.item.getData(), whereas that is provide to you in the last option...
I am writing code that generates both PDF and RTF documents, depending on the user's selection. The information in both documents is the same.
Until now, we were using classes like Table, Cell, HeaderFooter, etc., which are rendered into the correct form by the documentwriter (either PdfWriter or RtfWriter2).
However, the further I get into trying to make changes (mostly because the upgrade to iText 2.1 left the spacing a little quirky), the more I'm being told to "use PdfpTable", or "Use pageEvents to set headers". It seems like a lot of the generic classes are being deprecated.
I am thinking of revamping the code to separate out the table creations for PDF and RTF. However, all the iText tutorial stuff seems to actually recommend using Table in an instance where both PDF and RTF documents are needed.
Additionally, it appears that while there is a PdfpTable class, there is nothing similar for RTF, so I would be using Table anyway, which would leave me vulnerable to all the quirks that come along with the now unsupported Table class.
Basically, what are the benefits/downsides of separating the code into two sections -- one to create PDF documents, and one to create the same documents in an RTF format, if that was selected? And where does SimpleTable come in to all of this? Will it give me the flexibility that I need?
Thanks!
From the book iText In Action, end of chapter 6:
If you look at the iText API, you’ll also find some other table classes. com.lowagie.text.Table is the original table class; it dates from the early iText days. It uses class com.lowagie.text.pdf.PdfTable internally to render a table to PDF (don’t confuse this class with PdfPTable).
There’s also the newer SimpleTable class, which tries to form a link between
PdfPTable and Table. It’s able to translate itself to a PdfPTable if you add it to a
document that writes PDF or to a Table if you’re producing HTML or RTF. [...]
The major disadvantage of the Table class is that it’s no longer supported. Different
people have fixed most of the known issues, but today not a single person
understands if and how all the Table-methods work. If you decide to use this class,
you’re more or less on your own, and you’ll encounter lots of quirky layout issues
based on historical design decisions. However, this doesn’t mean you can’t make
good use of the Table class.
Advantages of the Table class
With the Table class, you can generate a table structure that can be rendered in
PDF, RTF, and HTML. If you compare the results, you’ll see there are small differences
in the way the table is rendered. This is normal; not every table feature is
supported in every document format.
You can generate a table in PDF, HTML, or RTF using the same code.
You can set padding and spacing the way it’s done in HTML.
You can use the row span without having to resort to nested table.
You can change the number of columns even after you’ve added cells.
You can add cells at specific positions (the number of rows is augmented
dynamically).
You can delete a column before adding the table to the document.
You can let iText add the Table as if it was a PdfPTable.
You get a PdfPTable object based on the Table object.
As opposed to PdfPTable, you can add cells to a Table in a random order, and add
or delete columns if needed. You can even translate a Table to a PdfPTable if you
didn’t use setRowspan().
There’s also the SimpleTable, class, which is a simplified version of (PdfP)-Table. When adding a SimpleTable to a PDF document, iText first attempts to add
the table as a PdfPTable; if this fails, it’s added as a Table. When adding a SimpleTable to an RTF or HTML document, it’s added as a Table. SimpleTable differs
from the Table and PdfPTable in the sense that it reintroduces the concept of rows.
This can be handy if you’re parsing an XML file that has a table-row-cell structure.
If the tag corresponding with the rows has attributes, you don’t have to define this
property for each cell in the row separately; you can set the property for the entire
row at once.
Summary
PdfPTable should be your first choice; but depending on the requirements defined for your project, there can be good reasons to opt for Table or SimpleTable.