Things I Wish Were in Lightroom

I just spent a while using Lightroom to prepare a stock submission and found a number of places where it really shines and a number where it might be improved. I thought I would list my experiences and perhaps find out whether others have found workarounds, agree, or disagree. I also hope Adobe spends time reading this board.
- Dual monitor support on Mac is missing. This was almost enough to make me switch back to Aperture. Maybe not everyone has two monitors, but enough do that Photoshop has supported that editing mode well for years, and it totally rocks on Aperture.
- Metatagging is not what it might be. For stock photography, metatags are more than just a nicety one uses to later locate images; they are mandatory, and I need to exercise fine grained control over the tags, as well as the exact ordering of subcomponents. So, for example, make it possible for my keywords to appear in arbitrary order instead of helpfully alphabetizing them.
- Metatagging is not what it might be (part 2). I have to use Photo Mechanic to get any measure of automation into this process. It would be ideal to have a tagging view where the image thumbnail appeared on the left and the IPTC/EXIF entry form appeared on the right. Then I could enter data, copy the whole entry, move from image to image, and so on. Presets would be extreeeeemely helpful here as well.
- Workflow is ambiguous. I finally settled on exporting to DNG so I could do final touch corrections in Photoshop. I don't really want multiple copies of the images so the edit in photoshop feature doesn't quite work. I'm not sure this DNG thing is best for what I'm doing, but it seems like a good stopgap measure. It would be nice to understand where Adobe envisioned this workflow going.
- UI elements constantly pop up when I don't want them. I've grown used to the Mac dock springing out but I can stop that from happening. However, it's one of the most annoying features of OSX. Great. Now I have it in Lightroom -- UI elements pop up when I'm in Develop and reach the cursor down to pick one of the tools.
- UI state feedback is minimal. Because of the keen black/gray color scheme, it's not clear when a UI modal feature is selected. For example, say I'm using the spotting tool but want to move to the next image. Right arrow does the wrong thing and the visual cues aren't sufficient to inform me of that. Even worse is the target adjustments for saturation/luminance/hue. It's seldom clear that I have selected or deselected this. I say this after adjusting hundreds of images using this tool so it's not just bonehead noob errors.
- Export to JPEG should have optimize to file size. C'mon, that's been in ImageReady forever.
I'm happy with LR overall, but still find myself wanting just a bit more. I recognize it's a 1-dot-oh release, so I'm hoping for great things. It's terrific that NAPP is putting their weight behind it because with that kind of critical mass thinking, the ramp-up to understanding LR's strengths and weaknesses will be faster.

Keyword problems.
I thought when I select a series of photo's I could edit keywords in the box where all the keywords are accumulated (at the right side of the screen). Some keywords have an asterisk, others not. So I thought when I edit the keyword that all pictures have, then that keyword is changed in all the files.
It is changed, but all the other keywords in that box are added to all photo's! So all photo's I had selected have now all keywords from all the other photo's in that selection too!
I didn't know that, so I edited a few more keywords because I used them wrong, and my whole database is not useable anymore.
I had a backup, but that was one week old. So that was a lot of work to bring it back.
So the lesson is: Don't edit keywords in the right keyword box when you have selected multiple pictures.
I see this as a bug. It should not be possible to edit something somewhere with such disastrous consequences.
Another problem is the way you use keyword sets, as far as I can see.
There are possibilities to use sets, but I couldn't add a whole set with nine keywords with one click. I had to click all the separate keywords in that set to be added.
And after all there are only nine keywords in a set.
I found a workaround for this problem, but not in Lightroom but is Bridge CS3.
There you can make sets of keywords and organize them. All keywords you want to add in one time with just one click, you can put them all in one line separated with semicolons. All the keywords you want to add are automatically written to the sidecar of the file (or inside the file with DNG). Later you can import the XMP metadata from files into your Lightroom database.
I wish that these possibilities which are in Bridge CS3 are also implicated into Lightroom
Laurens

Similar Messages

Wish list for Lightroom 4

I just put together my wish list for Lightroom 4.
http://davidnaylor.org/blog/2011/01/wish-list-for-lightroom-4/
What do you think? Did I miss anything important out?

I want soft proofing so bad, I didn't even upgrade to lr3, because the changes they did make meant so little in comparison to it.
Please Adobe, if you're reading this...SOFT PROOFING PUH-LEEZ!
Additionally, it would be very useful to be able to embed watermarks that are visible to printing services, but not visible when viewing files on screen. I don't know if that's even possible, but it would help photographers who want to provide the files to our clients, but don't want them to have unlimited usage. They can enjoy the photos on their computers, they could print too, but the printing services would be limited by whatever copyright limitations the photographer places on the invisible watermark. For example, I might put something like:
copyright 2011 Iconic Photography, Vancouver, Canada
This image may be reproduced to a maximum print size of 8" x 12"
Contact Iconic Photography at [email protected] for more information.
This would prevent clients from making their own albums or wall prints. Whaddaya say Adobe?

Things i wish SQL supported. The lazy man's list.

Things i wish SQL supported. This is the lazy man's list. Just to make things easier.
1) IT - refer to the first COLUMN in the SELECT clause.
- SELECT Name FROM Item WHERE IT is LIKE 'ABC%';
2) THEY - refer to each COLUMN in the SELECT list, individually.
- SELECT Name, Type FROM Item WHERE THEY ARE NOT NULL;
3) PK - refer to the PRIMARY KEY of the TABLE.
- SELECT * FROM Item WHERE PK = 12345;
Number 1 is what i'd like best.

"> Number 1 is what i'd like best.
That one is (arguably) the least useful. Just typing "IT" vs. the actual column name?"
Yep. For ad-hoc queries, it would save quite a bit of time.
3) is dangerous because constraints can be altered (granted, PK is less likely). And
then when I debug a sql statement like this, Firstly, i would not want this in production code. Just like i'd never use * in production code (outside of COUNT and EXISTS).
Secondly, the PK is not just a constraint, it defines the entire TABLE. Indeed, a FOREIGN KEYs default REFERENCING refers to the PK. So, this isn't something unheard of.
I would have to refer to the constraints to >see what column(s) are being used. Yuck.You run queries on TABLEs where you donlt know which COLUMN is the PRIMARY KEY? Shame on you! :)
2) I can't imagine ever using this one. I don't remember ever selecting a dozen columns
followed by a dozen and...is not null conditions.I have. But even if it's not for NULL, there are times where i want to check things like UPPER, or the like. Similarly, using them for IN, like WHERE THEY are IN (SELECT * FROM some_other_TABLE) or the like.
Just a thought. I appreciate your comments.

Yes. Please help. I wish to download Lightroom CC (preferably version 6). It doesn't appear in my creative Cloud list. I have been a CC member since it started. (The photographic version which SHOULD include Photoshop AND Lightroom.) I have the standalone

Yes. Please help. I wish to download Lightroom CC (preferably version 6). It doesn't appear in my creative Cloud list. I have been a CC member since it started. (The photographic version which SHOULD include Photoshop AND Lightroom.) I have the standalone versions of Photoshop 6 and Lightroom 5 already installed too!

Hi George,
Kindly try the below mentioned steps.
Sign in, Sign out | Creative Cloud desktop app
Click on download on Digital photography software | Download free Adobe Photoshop Lightroom CC trial
Please share the results once done.
Thanks,
Atul Saini

THIngs I wish my Iphone could do

Well I have had my iphone for a week now and so far pretty good.
My wish list of things I want my iphone to do...(if anyone knows how to do it would be great)
1 send pictures via text messaging and also email (I loved this option on my palm)
2 be able to download my programs that i had on my palm onto my phone. ( I use medical software like medical formulary that I would love to have on my iphone that way would be truly intagrated).
3 Use voice recognition for phone calls so did not have to go into phone then into favorites or contact or keypad to make a call, also great for 911 emergencies
4 Something that is really getting on my nerves is when you are on a call and you want to hang up the screen is blank you have to touch the screen to end the call and sometimes i accidently hit 3 way calling or whatever icons are avaialbe.
5. I hate the way the ignore phone call works, i will be on another call and hit ignore and I will accidently drop my current call somehow. This is something that is really getting on my nerves.
I do love the phone, the itunes features are great:) The phone component is something that i think apple should have investiagted a little more. OH and the gps and interenet are really cool also.

Welcome to the discussion groups!
This is all good stuff, but there's no guarantee that the right people at Apple will see it. These discussions are strictly for support.
For iTunes/iPod feedback go here.

Fake stories you wish were true

I saw an article online recently that I couldn't believe. It turns out that it was fake so I was right to not believe it. However, I kind of wish it was true...The headline went: Man arrested for sex with alligator.Now, I'm not advocating animal abuse, in fact, I generally like animals better than people and would love to see animal abusers be sentenced to receive the same treatment the animals did.However, could you imaging there being a guy in a prison somewhere with that claim to fame?"What're you in for?""Oh, I robbed a bank, you?""I hog-tied and f---ed an alligator." *drops mic**stunned silence all around*I don't know why (yes I do, I have a morbid and twisted sense of humor) but the whole thing is funny/interesting to me.Anywho... Have any of you ever seen a news story that you found out was fake but wished it wasn't?
This topic first appeared in the Spiceworks Community

Yes, Marshall, the well known manufacture of precision guitar amps, is now coming out with their own SMART PHONE! What!!??https://www.marshallheadphones.com/mh_us_en/phone/?utm_source=facebook&utm_medium=organic&ut...It's definitely made for musicand I'm intrigued."Marshall London delivers the promise of high-quality listening; thanks to its dual speakers using enhanced bass technology and the dedicated hifi-grade sound card. The London is capable of crystal-clear playback of lossless FLAC files, giving justice to your old music files. The stereo microphone is perfect for recording on the go and features excellent noise reduction.Two stereo jacks are located on the top of the phone, allowing two users to share music simultaneously and at different volume levels. A global wide equalizer allows the user to personalize music played on the...

Basic things I wish my iPod could do...

OK, here's my wish list. These are the features I wish I had on my iPod. They're small things. I'm hoping they will change some of these features in future updates.
1 - Why does shuffle mode have to be universal? I have some playlists that are just designed to listen to in shuffle mode. (Example: a smart playlist with all songs from one genre where My Rating is greater than two stars). I hate that every time I start that playlist I have to hit the Menu button three times, scroll down to Settings, scroll down to shuffle, and select Songs. Then, later if I want to listen to an album, I go all the way back out to the main menu to change the shuffle setting back to Off. Not all playlists should shuffle, though, so I should be able to set it for each playlist individually.
My wish: LET ME DEFINE A PLAYLIST AS A "SHUFFLE LIST" SO THAT WHEN I PLAY THAT PLAYLIST IT JUMPS INTO SHUFFLE MODE WITHOUT MY HAVING TO CHANGE THE SETTINGS MANUALLY EVERY TIME AND THEN CHANGE BACK WHEN I'M DONE.
2 - Why are audiobooks such a pain? If I take one of my books on CD and want to put it on my iPod, it's this long process where I change the file type I import as, and I merge the files together, and I run a little utility and change the file type. That kind of user-unfriendliness is very non-Apple, and does not fit with the kind of great design and interface I've come to expect.
My wish: LET ME IMPORT THE CD'S JUST THE WAY THEY ARE WITH ALL THEIR MULTIPLE TRACKS, THEN LET ME HIGHLIGHT ALL OF THEM AT ONCE AND GIVE ME A CHECKBOX IN THE INFO SCREEN THAT WILL DEFINE THEM AS ONE AUDIOBOOK.
3 - Audiobook pain, continued. Why does my iPod only keep track of where I left off in an audiobook if the audio file is one long, merged AAC? Since I can already set my audio files to "Remember Playback Position" regardless of their file type, how much harder would it be to have the iPod keep track of what chapter I'm in of my audiobook?
My wish: LET ME DEFINE AUDIOBOOKS OF ALL FILE TYPES TO REMEMBER WHICH TRACK I WAS IN, AS WELL AS THE PLAYBACK POSITION WITHIN THAT TRACK.
5th generation 30GB Windows XP Pro

Welcome to the discussion groups!
This is all good stuff, but there's no guarantee that the right people at Apple will see it. These discussions are strictly for support.
For iTunes/iPod feedback go here.

I have itunes songs that I wish were mp3 (for use on a SD Card)

Can they be changed in Itunes, or so I have to start over?
Also, I assume that there is a column available in Itunes to sort protected vs. unprotected.
Many thanks

One way of sorting could be creating a smart playlist with this rule
<Playlist> <is not> <Purchased>
Of course that would exclude the iTunes plus songs also
There are probably other ways but thats what I can think of right now
As for changing the songs to mp3 go to iTunes Preferences>Advanced>Importing and set Import using *mp3 encoder* then select all the songs in the new playlist and right click then *convert selection to mp3*.

Is Lightroom 1.3 commercial quality yet?

I blindly rushed out and purchased Lightroom when it first came out (i.e., v1.0) -- bought Scott Kelby's Lightroom book and jumped in head first. It didn't take long to determine that Lightroom v1.0 wasn't a viable product, so I removed it from my computer and resumed using Bridge CS3. I'm still somewhat confused as to what is so much better about Lightroom than Bridge/Camera RAW, but I'm curious to give Lightroom another try -- after all, I did *pay* for this unusable software! Is it worth me reinstalling Lightroom and upgrading to 1.3 to check it out again?
Regards,
Greg

Interesting responses. Sorry that I didn't provide specifics as to my workflow. Here goes:
- I process several hundred images at a time.
- I pull the images off my datacard with Bridge CS3, rename the files, and stamp them with metadata -- this is all automated via Bridge CS3. I'll also add keywords if necessary at this point from Bridge. I didn't see any discernable difference between Lightroom and Bridge.
- I rank/review the pictures, delete the duds, and pick the keepers. Again, this functionality looked the same between Lightroom and Bridge.
- I then use ACR to make adjustments to white balance, exposure, contrast, color, etc. The amount of "automation" in this step depends on the batch of photos. For example, for batches with the same lighting, I can adjust white balance on one photo and with 2 clicks I can update the white balance on the rest of the photos from bridge. As best as I can tell, ACR is the same as Lightroom's Develop module. The sliders are the same, listed in the same order, etc.
- For pictures that require photoshop edits, I'll launch them in photoshop directly from bridge, make my edits, and save. I'd have to do the same thing if I were using Lightroom.
- When all edits are done, I'll review them in Bridge's slideshow mode. Slideshow is primarily for me -- I don't have to show a slideshow to clients, so I don't really need a "prettier" slideshow mode than Bridge already provides.
- I don't print very many of my pictures. When I do print, I just print them from Photoshop directly to my Epson 3800 -- they turn out great. Ironically, I've seen people that think Lightroom's Print module is amazing, and I've seen people that think Lightroom's Print module stinks.
- I don't have a need to generate web galleries of my pictures. If I did, I know that Photoshop can do this. Maybe Lightroom's Web module is better? Again, I've seen very polarized opinions about this as well.
- If I need JPEGs, I just convert the images from Bridge via the Image Processor command (which invokes Photoshop).
And there you have it -- a high level view of my workflow.
It's been a while since I used Lightroom 1.0, but I'll try to remember the specifics that led me to my comments about 1.0 not being a viable product. (Although, I suspect I wouldn't have received this same reaction back in the 1.0 days -- almost everybody was complaining about the quality of the product.)
- Overall quality/stability was poor. I have a s/w engineering background and felt that the 1.0 release was definitely a bit premature.
- Performance was awful. When I would drag a slider in the Develop module, it would take a few seconds for the screen to update. ACR had the same sliders, but without the sluggishness.
- There was some other weird quirk about the linkage between Lightroom/Photoshop that escapes me at the moment. Not sure if I posted anything to this forum about it.
Regarding the "try before you buy" comments, I find these reactions somewhat humorous. You guys are reacting as if Lightroom were your mom and I just insulted your mom. If Lightroom really is your mom, then I truly am sorry for offending you. :) My first real Photoshop experience started with CS2. My impression of Adobe was VERY high. I also happen to think very highly of Scott Kelby and his NAPP organization. When Lightroom came out, Scott Kelby was making so much noise about how amazing and groundbreaking Lightroom was -- this really caught my attention. Given this, along with my high regard for Scott Kelby, I just jumped into Lightroom. Only after using the tool for several weeks and then finally reading the reaction to 1.0 on this forum did I realize that I had made a mistake. I simply removed Lightroom from my computer and resumed using Bridge CS3. Now that there have been 2 relatively major releases to Lightroom, I'm just trying to determine if the quality/performance of Lightroom has improved to the point where I should give it another try. Yes, this is subjective; however, I can't possibly be the only person out there that was underwhelmed with Lightroom 1.0. Just looking for someone else who shared a similar 1.0 experience as I had that has maybe given 1.3 a try. Sorry if I offended anybody because I didn't like Lightroom 1.0.
Regards,
Greg

No DataGrid component?

I believe JavaFX seriously needs a DataGrid component to render tabular data as a GRID, where data can be paged, sorted, filtered like other data grid solutions (Adobe Flex, jQGrid, DataTables etc).
This is one of the basic controls, any serious application would definitely need. TableView is the only closest thing I found, but that doesn't fit the bill at all.
The DataFx project looks promising, but is very primitive.
I hope Oracle will come up with a pretty GRID control soon, to beat the competition. We were planning to go with JavaFX and the only thing that is stopping us is the lack of a GRID component, we have to look for other web-based alternatives now.

I think there's more to the TableView API than you're seeing, as it's supported by the JavaFX Properties and Collections APIs. The columns are exposed as a mutable, observable List, as is the data. So the columns are dynamic and can be readily changed as necessary, the table will update automatically.
I used you example as a way to test this out; I've made no effort whatsoever to make this look good, the css is relatively straightforward. Also, I have no knowledge whatsoever of your business domain, so this will likely look somewhat naive. I think the code structure might be helpful though. There are some things I wish were a bit different but I'll come to that after the code.
I'm going to assume you have some kind of data model and some way of knowing when the data's changed. I've mocked this up with a DataModel class with listener notification, but there are other ways this could happen (could be an EJB, for example). I've made this completely agnostic with respect to JavaFX.
DataModel.java (a mockup of something I assume you already have existing):
import java.util.ArrayList;
import java.util.List;
public class DataModel {
     private double minDeviation ;
     private double maxDeviation ;
     private int numDeviationCategories ;
     private int numRows ;
     private List<DataListener> listeners ;
     public DataModel(double minDeviation, double maxDeviation,
               int numDeviationCategories, int numRows) {
          this.minDeviation = minDeviation;
          this.maxDeviation = maxDeviation;
          this.numDeviationCategories = numDeviationCategories;
          this.numRows = numRows;
          this.listeners = new ArrayList<DataListener>();
     public String getValue(int row, double deviation) {
          int category = (int) ((numDeviationCategories - 1)*(deviation - minDeviation) / (maxDeviation - minDeviation)) ;
          return String.format("f(%d, %d)", category+1, row+1);
     public double getMinDeviation() {
          return minDeviation;
     public void setMinDeviation(double minDeviation) {
          if (minDeviation != this.minDeviation) {
               this.minDeviation = minDeviation;
               fireDeviationRangeChanged();
     public double getMaxDeviation() {
          return maxDeviation;
     public void setMaxDeviation(double maxDeviation) {
          if (maxDeviation != this.maxDeviation) {
               this.maxDeviation = maxDeviation;
               fireDeviationRangeChanged();
     public int getNumDeviationCategories() {
          return numDeviationCategories;
     public void setNumDeviationCategories(int numDeviationCategories) {
          if (numDeviationCategories != this.numDeviationCategories) {
               this.numDeviationCategories = numDeviationCategories;
               fireNumDeviationCategoriesChanged();
     public int getNumRows() {
          return numRows;
     public void setNumRows(int numRows) {
          if (this.numRows != numRows) {
               this.numRows = numRows;
               fireNumRowsChanged();
     public void addDataListener(DataListener l) {
          listeners.add(l);
     public void removeDataListener(DataListener l) {
          listeners.remove(l);
     private void fireDeviationRangeChanged() {
          DataEvent event = new DataEvent(this);
          for (DataListener l : listeners) {
               l.deviationRangeChanged(event);
     private void fireNumDeviationCategoriesChanged() {
          DataEvent event = new DataEvent(this);
          for (DataListener l : listeners) {
               l.numDeviationCategoriesChanged(event);
     private void fireNumRowsChanged() {
          DataEvent event = new DataEvent(this);
          for (DataListener l : listeners) {
               l.numRowsChanged(event);
}And there are two almost trivial supporting classes to support the listener notification:
public interface DataListener {
     public void deviationRangeChanged(DataEvent event);
     public void numDeviationCategoriesChanged(DataEvent event);
     public void numRowsChanged(DataEvent event);
public class DataEvent {
     private final DataModel source ;
     public DataEvent(DataModel source) {
          this.source = source;
     public DataModel getSource() {
          return source;
}The TableView exposes ObservableLists for the columns and the data. We need to update those lists when the data or column structure changes. So we need an adapter to sit in front of our generic DataModel and manipulate those lists when the data changes. This class will take a reference to a DataModel in addition to references to the column list and data list; it will listen for notifications from the DataModel and update the lists as necessary. (I'm implementing each row in the table simply as a List<String>, and we retrieve each element from the row using a custom CellValueFactory.)
TableDataModel.java:
public class TableDataModel {
     private DataModel model ;
     private final ObservableList<TableColumn<List<String>, ?>> columns ;
     private final ObservableList<List<String>> items ;
     public TableDataModel(DataModel model, ObservableList<TableColumn<List<String>, ?>> columns, ObservableList<List<String>> items) {
          this.model = model ;
          this.columns = columns;
          this.items = items ;
          buildColumns();
          buildItems();
          model.addDataListener(new ModelListener());
     private void buildColumns() {
          int numCols = model.getNumDeviationCategories();
          List<TableColumn<List<String>, String>> colList = new ArrayList<TableColumn<List<String>, String>>();
          double minDeviation = model.getMinDeviation() ;
          double maxDeviation = model.getMaxDeviation() ;
          double colDeviationIncrement = (maxDeviation - minDeviation) / (numCols-1) ;
          Format percentFormat = DecimalFormat.getPercentInstance();
          for (int col=0; col<numCols; col++) {
               String colTitle = percentFormat.format(minDeviation + col*colDeviationIncrement);
               TableColumn<List<String>, String> column = new TableColumn<List<String>, String>(colTitle);
               final int colIndex = col ;
               column.setCellValueFactory(new Callback<TableColumn.CellDataFeatures<List<String>,String>,ObservableValue<String>>() {
                    @Override
                    public ObservableValue<String> call(
                              CellDataFeatures<List<String>, String> cellDataFeatures) {
                         List<String> data = cellDataFeatures.getValue();
                         return new SimpleStringProperty(data.get(colIndex));
               colList.add(column);
          columns.clear();
          columns.addAll(colList);
     private void buildItems() {
          List<List<String>> itemList = new ArrayList<List<String>>();
          int numCols = model.getNumDeviationCategories() ;
          for (int row = 0; row<model.getNumRows(); row++) {
               List<String> data = new ArrayList<String>();
               double minDeviation = model.getMinDeviation() ;
               double colDeviationIncrement = (model.getMaxDeviation() - minDeviation) / (numCols-1) ;
               for (int col = 0 ; col < numCols; col++) {
                    double deviation = minDeviation + col * colDeviationIncrement ;
                    data.add(model.getValue(row, deviation));
               itemList.add(data);
          items.clear();
          items.addAll(itemList);
     private class ModelListener implements DataListener {
          @Override
          public void deviationRangeChanged(DataEvent event) {
               double minDeviation = model.getMinDeviation();
               double maxDeviation = model.getMaxDeviation();
               int numCols = model.getNumDeviationCategories();
               double colDeviationIncrement = (maxDeviation - minDeviation) / (numCols-1);
               Format percentFormat = DecimalFormat.getPercentInstance();
               for (int col=0; col<numCols; col++) {
                    String colTitle = percentFormat.format(minDeviation + col*colDeviationIncrement);
                    columns.get(col).setText(colTitle);
          @Override
          public void numDeviationCategoriesChanged(DataEvent event) {
               buildItems();
               buildColumns();
          @Override
          public void numRowsChanged(DataEvent event) {
               buildItems();
}To test this out, I have a simple UI for changing the range of "deviations" displayed, the number of columns, and the number of rows. The controller for the UI simply instantiates a DataModel and passes calls to it when the user changes these values. In real life, of course, the changes to the data model could come from anywhere - likely from polling a server or server push. The UI also contains the TableView, retrieves the columns and items from it, and passes those, along with the data model to a TableDataModel which ties it all together. This isn't really part of the infrastructure, but for completeness here's the controller:
Controller.java
public class Controller {
     @FXML private TableView<List<String>> tableView ;
     @FXML private TextField minDevTF ;
     @FXML private TextField maxDevTF ;
     @FXML private TextField numColsTF ;
     @FXML private TextField numRowsTF ;
     @FXML private Button minDevIncButton ;
     @FXML private Button minDevDecButton ;
     @FXML private Button maxDevIncButton ;
     @FXML private Button maxDevDecButton ;
     @FXML private Button numColsIncButton ;
     @FXML private Button numColsDecButton ;
     @FXML private Button numRowsIncButton ;
     @FXML private Button numRowsDecButton ;
     private DataModel model ;
     public void initialize() {
          model = new DataModel(0.8, 1.2, 5, 6);
          final TableDataModel tableModel = new TableDataModel(model, tableView.getColumns(), tableView.getItems());
          model.addDataListener(new DataListener() {
               @Override
               public void deviationRangeChanged(DataEvent event) {
                    if (model.getMaxDeviation() - model.getMinDeviation() <= 0.01) {
                         minDevIncButton.setDisable(true);
                         maxDevDecButton.setDisable(true);
                    } else {
                         minDevIncButton.setDisable(false);
                         maxDevDecButton.setDisable(false);
                    Format percentFormat = DecimalFormat.getPercentInstance();
                    minDevTF.setText(percentFormat.format(model.getMinDeviation()));
                    maxDevTF.setText(percentFormat.format(model.getMaxDeviation()));
               @Override
               public void numDeviationCategoriesChanged(DataEvent event) {
                    numColsDecButton.setDisable(model.getNumDeviationCategories() <= 2);
                    numColsTF.setText(Integer.toString(model.getNumDeviationCategories()));
               @Override
               public void numRowsChanged(DataEvent event) {
                    numRowsDecButton.setDisable(model.getNumRows() <= 2);
                    numRowsTF.setText(Integer.toString(model.getNumRows()));
          Format percentFormat = DecimalFormat.getPercentInstance();
          minDevTF.setText(percentFormat.format(model.getMinDeviation()));
          maxDevTF.setText(percentFormat.format(model.getMaxDeviation()));
          numColsTF.setText(Integer.toString(model.getNumDeviationCategories()));
          numRowsTF.setText(Integer.toString(model.getNumRows()));
     public void decrementMinDeviation() {
          model.setMinDeviation(model.getMinDeviation() - 0.01);
     public void incrementMinDeviation() {
          model.setMinDeviation(model.getMinDeviation() + 0.01);
     public void decrementMaxDeviation() {
          model.setMaxDeviation(model.getMaxDeviation() - 0.01);
     public void incrementMaxDeviation() {
          model.setMaxDeviation(model.getMaxDeviation() + 0.01);
     public void decrementNumColumns() {
          model.setNumDeviationCategories(model.getNumDeviationCategories() - 1);
     public void incrementNumColumns() {
          model.setNumDeviationCategories(model.getNumDeviationCategories() + 1);
     public void decrementNumRows() {
          model.setNumRows(model.getNumRows() - 1);
     public void incrementNumRows() {
          model.setNumRows(model.getNumRows() + 1);
}Here's the FXML for the UI:
root.fxml:
<?xml version="1.0" encoding="UTF-8"?>
<?import javafx.scene.layout.BorderPane?>
<?import javafx.scene.control.ScrollPane?>
<?import javafx.scene.layout.HBox?>
<?import javafx.scene.layout.VBox?>
<?import javafx.scene.layout.FlowPane?>
<?import javafx.scene.control.TextField?>
<?import javafx.scene.control.Button?>
<?import javafx.scene.control.Label?>
<?import javafx.scene.control.TableView?>
<?import javafx.scene.shape.Path?>
<?import javafx.scene.shape.MoveTo?>
<?import javafx.scene.shape.LineTo?>
<?import javafx.scene.shape.ClosePath?>
<?import javafx.scene.paint.Color?>
<?import javafx.scene.control.ProgressIndicator?>
<BorderPane xmlns:fx="http://javafx.com/fxml"
     fx:controller="edu.marshall.denvir.tests.gridlike.Controller">
     <top>
          <FlowPane>
               <HBox>
                    <Label text="Min Deviation:"/>
                    <TextField fx:id="minDevTF" editable="false" />
                    <VBox>
                         <Button fx:id="minDevIncButton" prefWidth="20" prefHeight="10" minWidth="20" minHeight="10" onAction="#incrementMinDeviation">
                              <graphic>
                              <Path fill="BLACK">
                                   <elements>
                                        <MoveTo x="0" y="4"/>
                                        <LineTo x="2" y="0"/>
                                        <LineTo x="4" y="4"/>
                                        <ClosePath/>
                                   </elements>
                              </Path>
                              </graphic>
                         </Button>
                         <Button fx:id="minDevDecButton" prefWidth="20" prefHeight="10" minWidth="20" minHeight="10" onAction="#decrementMinDeviation">
                              <graphic>
                              <Path fill="BLACK">
                                   <elements>
                                        <MoveTo x="0" y="4"/>
                                        <LineTo x="2" y="0"/>
                                        <LineTo x="4" y="4"/>
                                        <ClosePath/>
                                   </elements>
                              </Path>
                              </graphic>
                         </Button>
                    </VBox>
               </HBox>
               <HBox>
                    <Label text="Max Deviation:" />
                    <TextField fx:id="maxDevTF" editable="false" />
                    <VBox>
                         <Button fx:id="maxDevIncButton" prefWidth="20" prefHeight="10" minWidth="20" minHeight="10" onAction="#incrementMaxDeviation" styleClass="increment-button">
                              <graphic>
                              <Path fill="BLACK">
                                   <elements>
                                        <MoveTo x="0" y="4"/>
                                        <LineTo x="2" y="0"/>
                                        <LineTo x="4" y="4"/>
                                        <ClosePath/>
                                   </elements>
                              </Path>
                              </graphic>
                         </Button>
                         <Button fx:id="maxDevDecButton" prefWidth="20" prefHeight="10" minWidth="20" minHeight="10" onAction="#decrementMaxDeviation">
                              <graphic>
                              <Path fill="BLACK">
                                   <elements>
                                        <MoveTo x="0" y="4"/>
                                        <LineTo x="2" y="0"/>
                                        <LineTo x="4" y="4"/>
                                        <ClosePath/>
                                   </elements>
                              </Path>
                              </graphic>
                         </Button>
                    </VBox>
               </HBox>
               <HBox>
                    <Label text="Number of columns:" />
                    <TextField fx:id="numColsTF" editable="false" />
                    <VBox>
                         <Button fx:id="numColsIncButton" prefWidth="20" prefHeight="10" minWidth="20" minHeight="10" onAction="#incrementNumColumns">
                              <graphic>
                              <Path fill="BLACK">
                                   <elements>
                                        <MoveTo x="0" y="4"/>
                                        <LineTo x="2" y="0"/>
                                        <LineTo x="4" y="4"/>
                                        <ClosePath/>
                                   </elements>
                              </Path>
                              </graphic>
                         </Button>
                         <Button fx:id="numColsDecButton" prefWidth="20" prefHeight="10" minWidth="20" minHeight="10" onAction="#decrementNumColumns">
                              <graphic>
                              <Path fill="BLACK">
                                   <elements>
                                        <MoveTo x="0" y="4"/>
                                        <LineTo x="2" y="0"/>
                                        <LineTo x="4" y="4"/>
                                        <ClosePath/>
                                   </elements>
                              </Path>
                              </graphic>
                         </Button>
                    </VBox>
               </HBox>
               <HBox>
                    <Label text="Number of Rows:" />
                    <TextField fx:id="numRowsTF" editable="false" />
                    <VBox>
                         <Button fx:id="numRowsIncButton" prefWidth="20" prefHeight="10" minWidth="20" minHeight="10" onAction="#incrementNumRows">
                              <graphic>
                              <Path fill="BLACK">
                                   <elements>
                                        <MoveTo x="0" y="4"/>
                                        <LineTo x="2" y="0"/>
                                        <LineTo x="4" y="4"/>
                                        <ClosePath/>
                                   </elements>
                              </Path>
                              </graphic>
                         </Button>
                         <Button fx:id="numRowsDecButton" prefWidth="20" prefHeight="10" minWidth="20" minHeight="10" onAction="#decrementNumRows">
                              <graphic>
                              <Path fill="BLACK">
                                   <elements>
                                        <MoveTo x="0" y="4"/>
                                        <LineTo x="2" y="0"/>
                                        <LineTo x="4" y="4"/>
                                        <ClosePath/>
                                   </elements>
                              </Path>
                              </graphic>
                         </Button>
                    </VBox>
               </HBox>
          </FlowPane>
     </top>
     <center>
               <TableView fx:id="tableView"/>
     </center>
</BorderPane>and finally the test driver:
Gridlike.java:
public class Gridlike extends Application {
     @Override
     public void start(Stage primaryStage) throws Exception {
          Parent root = FXMLLoader.load(getClass().getResource("root.fxml"));
          Scene scene = new Scene(root, 600, 400);
          primaryStage.setScene(scene);
          primaryStage.sizeToScene();
          primaryStage.show();
     public static void main(String[] args) {
          launch(args);
}So that seems to me not to be too bad. Obviously in the real world there's likely to be way more functionality in the data model and table data model implementations, but the structure is pretty clean and it should integrate pretty nicely with existing structures without much effort.
One thing I don't like is having to pass the ObservableLists to the TableDataModel. I'd prefer the TableDataModel simply to instantiate it's own lists and expose them, the way it is seems like too much strong couple from the model to the view. The problem is that the TableView only exposes ObservableLists. If it exposed ListPropertys, then those properties could just be bound to arbitrary list properties (or observable lists) exposed by a TableDataModel, which I think would be a bit cleaner.
In terms of having APIs for binding directly from TableViews to JDBC code, or similar, I think that would be nice but is probably a bit unrealistic at this stage. What happened in the web app world was that this kind of functionality was implemented by third party frameworks, and only after the use cases had really settled down did Sun/Oracle provide standard implementations (JPA and JSF, depending on what you're looking for). I don't think we'll have to wait as long as we waited for those, but I'd guess it will be a while.
The row headers, however, would be pretty nice, and it seems those could be fairly easily added to the TableView API. It shouldn't be too hard to create a column for them and style it so it looks different, but it would mess with the cleanliness of the data model.
Just my $0.02 worth...

When I import photos to lightroom CC I get a message Some import operations were not performed. The following files were not imported because they could not be read.

Dsc_5122nef dsc_5123JPG Everything worked fine for the last week. The only thing changed is I removed lightroom 5. How can I reinstall Lightroom 5

Its a 100% failure. I was trying to import 37 photos all failed. I can still import into Lightroom 5. I also can import into Lightroom CC on my other Mac. I tried importing from different cards, my other 7100 and my 5300 same problem. I have tried every combination of card reader, camera and computer I have. The only only time the message shows up is when I try to import into Lightroom CC on my 27 in Mac. Thanks Art

Is Lightroom really a professional tool?

I try for a second time to convince a professional photographer, which uses the DAm features of Lightroom heavily, to upgrade from Lightroom 2.7 to Lightroom 3.
A year ago it was the editing of hierarchical keyword, which prevented her upgrading, because this feature did not work.
Now, it is the issue that in keywprd hierarchies some features known from Lightroom 2 are not present or do not work:
1) In LR 3.5 the count of keyword is not applied hierarchical anymore. In LR 3, if I had a hierarchy like this.
Animals
Dogs
Cats
the following was calcualated:
Animals 12
dogs 4
cats 8
In,Lightroom 3 the total amounts of animals (12) is not calculated:
Animals
   dogs 4
   cats 8
Additionally, clicking on the arrow to the right of animals, in LR2 the images were filtered to all images having keywords which includes all animals and its childs.
Is is a bug, or was this new behaviour applied on purpose?
Now, the workflow of her does not work anymore, probably causing her not to upgrade.
Additionallly, and this should be a bug, if clickling on the arrow at the right of Animals, the images aren't filtered accordingly.
I have no sympathy, that such serious bug in the DAM sections slip through and are still prevalent in the product, or if the new behaviour is intentional, that this is implemented without the option that old behaviour can be recovered.
All in all, I think these are real bugs, which haven't been addressed. This all shows that Lightroom is hardly a professional tool.
May I remember that the keyword editing features aren't resolved completely, still? Keyword completion for keywords with spaces still does not work with parent keywords. And this after how many months / years after the first final release?
This all is absolutely disappointing.
Regards
Thomas

AlanUniqueName wrote:
I never used LR 2 and if the tag count behaviour has changed then I sympathise.
In your example I think it is because the photos have not been tagged with “Animals” and only the child tags of dogs and cats have been applied.   The counting as it currently implemented works nicely for me – why … because it means I can adopt a lazy “do later” hierarchical decomposition tagging of my shots.
For example if I have some photographs of mushrooms I will tag them as mushroom but not actually assign a child tag for the type of mushroom until I have got the book out properly identified it.    Although I have hundreds of mushroom shots tagged with child tags of mushroom, I am quite happy to have a count of say 2 against the “mushroom” tag as this is telling me at some point I need to properly identify the mushroom, assign a child tag of mushroom and remove the “mushroom” tag.
For me when I click on the right arrow next to a parent keyword then I do see all parent and child tagged photos as well – I do not know why you are not getting the same as me.
As an aside, to support the way I do things I wish I could have an optional setting called “Should not use” for parent keywords and allow filtering or smart collection showing photos which use any such tags.   This would allow me to see at a glance all photos which require some additional child tagging i.e. anything simply tagged “Mushroom”, “Owl”, “Flower” or “Animal” is not good enough.
In Lightroom 2, the count for parent keywords was calculated as the sum of the counts of assignments of the parent keyword plus the counts of assigments of all child keywords (drilled down to the last tree leaf).
Now the count method is as you describe.
There are certainly reasons to prefer the current method, but it is unprofesional to drop the one method and replace it with another, because you don't know if people depend on the former. This is well known good practice.

Error 88 or Support Code 88 in Canon Driver printing on art paper from Lightroom

Re: Error 88 (Support Code 88) of Canon Printer Driver, using Pixma Pro9500 - April 20, 2014
I'm replying to myself from two years ago, and to the rest of you, regarding Error 88. (My question of April 2012 is in the Photoshop department of Adobe Community. For those who don't know but are reading this anyway for some reason, Error 88 is a message from the Canon Printer Driver that tells you you haven't set the paper size correctly for printing on fine-art paper. But it may appear anyway, even if your settings are correct.)
At the time I found no resolution to the problem, just a workaround: to print from Lightroom itself. Too bad this was after months of hassle and expense, including a probably fraudulent (and certainly useless) repair (supposedly replacing the Pixma's logic board and paper sensor), and the ministrations of a techie who could only conclude there was something wrong with my copy of Photoshop which provoked the Error 88. But he made me realise I could print from Lightroom, and that's what I've been doing ever since. (The possibility had never occurred to me, as my routine of printing from Photoshop was working fine.) This has been a good move after all, since Lightroom offers many advantages over PS where printing is concerned: tonal controls and more in Develop, and the possibility of creating a Saved Print.
But to print from Lightroom, I had to crop my printing files to the image. (In PS I had always created a document the same size as the paper I planned to use – A4 or A3+ – and positioned the image where I wanted, with margins all around. But in Lightroom I set margins and position in Print Mode, starting with a borderless file.) This was a bit of work, but unavoidable, and a good thing on the whole. So for a couple of years I printed in this way.
But meanwhile, my 2009 iMac was developing other problems, and finally I had to replace it. (After only two or three years of use, it was shutting down spontaneously, a problem no one was able to resolve, about which every techie has a different opinion, and about which Apple is completely mute and unresponsive; thank you Apple Computer for your supposedly ultra-reliable products – I can only say it’s a good thing you don’t make pacemakers).
So for about ten weeks now I have a nice shiny new 2013 iMac, but I’m keeping my fingers crossed. Also I have the new OS Mavericks, new versions of Photoshop CS6 and Lightroom 5, the new Canon Driver. I have my complaints about the OS (particularly a few interface/viewing design choices that strike me as colossally stupid and unnecessary), but that's beside the point here.
Having not yet printed with the new setup (nor for a few months before), and knowing that it's good to use your Pixma now and then, I thought I'd dedicate a few hours to printing. I figured it could work out easy, since I planned to print from Saved Prints. But as soon as I hooked it all up, checked my settings, and clicked Print, I see the printer icon bouncing in the Dock with its little yellow trouble flag. I check that out and am very dismayed to see my old nemesis, Error 88, which tells me I haven't set the paper size correctly. But it's correct, of course. (As before, I'm printing on fine art paper, A3+.) Beg your pardon, Canon now calls it "Support Code 88", thinking of all the Support you'll get from them.
I tried a few of the obvious things: start/restart computer, printer, Lightroom, etc., but to no avail. Also, supposing that my Saved Prints were perhaps no longer valid in the new LR, I tried to print directly from the file, bypassing the Saved Print, but no go.
I should also note that, in Page Setup, the Default paper size “Super B/A3” (330x483mm) was new to me – seems to me you could set “A3+ Art Margins”. A3+ as I know it from the fine-art papers I use is 329x483mm anyway (also as given in Page Setup), if that makes any difference.
If it's any use, here are some particulars on the current situation:
iMac 27”, late 2013, 3.4 GHz Intel Core i5, 8 GB, Mac OSX 10.9.2
Lightroom 5.3 (Camera RAW 8.3)
Photoshop CS6 (version 13.0 x64)
Canon PrinterDriver_Pro9500 series_108420 (10.84.2.0)
And my settings: LR Page Setup: set “Art A3+ (Margin 35)”System Prefs/Printers & Scanners – set Default paper size “Super B/A3” (330x483mm) (found via “Format For:” in Page Setup)LR Print Settings:
Printer: Canon Pro9500 series (exclamation point – not recognized?)
Presets: Last Used Settings
Color Matching: Canon
Paper Handling: All Pages – Automatic – NO “Scale to fit paper size” (but “Destination Paper Size, though grayed out, reads “Suggested Paper: Art A3+ (Margin 35”)
Quality & Media: Media Type: Fine Art “Photo Rag” (or “FA Museum Etching” or “FA Matte”); Paper Source: Front Tray; Print Quality: High; YES Grayscale Printing
Color Options:
Color Mode: Standard; C-M-Y and Tone all left at zero
Brightness: Normal; Intensity and Contrast both left at zero
It all looks kosher to me. Does anybody know anything about this problem? I'll be very grateful.
AlienAl - still alien after all these years

Apple and Canon programmers don't read here.
You need to tell them about this at www.apple.com/feedback

Missing Features, Bugs, and Wish List for Apple Engineers

I LOVE my iPhone. It is by far the best phone I have ever had. The interface is awesome. Great job Apple, but there are missing features and bugs that all of us want updated or wish were added. I know they were probably already thought of by Apple, but in an effort to make the phone perfect removed to make it more stable. Now that it is out lets make it perfect.
This thread will hopefully give you guys guidance from the early adopters who share your love for the phone (and others who want to chime in). I want to separate the list into a few categories and hope everyone will add to this thread with their ideas:
1) BUGS/CHANGES TO EXISTING APPS:
- Period should be in alphabet keyboard (make space smaller) or when you go to symbol keyboard and hit period it should automatically go back to the alphabet keyboard (unless you double click the symbol button which means stay there like caps lock)
- Individual delete (like Mail) of all lists (eg. call list, bookmarks list, history etc.
- Multiple item in a List delete (see below for how to select). This is also so un-Mac like to not be able to select multiple items to delete. It is all or none for clear/delete on the iPhone.
- Implement double finger slide...in maps double finger tap zooms out so the OS recognizes this, why don't you use a double finger drag to mean "select". There is no way to select some words in a sentence or a group of items. This could be how. eg. In a list (eg Mail) double finger slide over items you want to select (instead of singer finger drag which moves the list) then one finger slide to the right to delete the selected items from the list.
- Copy and paste. Since there are no menus this would require a gesture (ala newton)
- when you tap the battery icon it should bring up a battery status dialog (ala wifi join dialog where the screen dims): present charge, big battery icon (like the charging one), time left. In addition, instead of giving battery usage details only after a full charge, give it at any point.
- Since you know that nights and weekends are at set times (and not variable like it was on Sprint where I came from)...the phone usage details should be broken down into: peak minutes used and N+W minutes used (not hard to figure out since you know the time and dates of calls)
- Be able to change font/background etc in Notes app
- faster way to get to favorites in the killer phone app after turning on phone. Just seems like it takes too many taps to get there to make a call on a phone.
2) WISH LIST FOR NEW APPS (apps that can be added with existing hardware, see #3 for other wishes)
- iChat (obvious and probably almost done)
- VOIP (probably not going to happen, and wouldn't work in Europe where I would need it most gven network speeds there)
- Flight tracker widget
- Exchange support (probably in the works)
- Push email from gmail and .Mac (probably in the works)
- Bluetooth sync
- DUN (probably not going to happen since AT+T does not want it)
- Data/File storage with sync
- TODO APP that syncs to to do in iCal
- Ringtones, definitely from songs from iPod side (obvious and coming soon I am sure)
-Search function like spotlight. Global would be awesome, but even just in contacts
3) FUTURE HARDWARE RELATED WISHES (stuff we wish could be in hardware version 1 but know require a version 2):
- GPS
- 3G
- LED that changes color and/or pulses (like MacBooks sleep light) that indicates things (eg charge status, Voice mail status, roaming status etc) without turning on the phone
- Move camera to front to allow video conferencing (I doubt Steve would allow since it would mess up the clean front look)
Well I could go on and will add to this thread later, but I need to go to work to show everyone (and sell more apple stuff since many of my colleagues have been converted to macs). Now, all you pioneers, start adding things to help our beloved phone become better!
Peter
iMac Mac OS X (10.3.6)

I agree with your post! I'm amazed by the simplicity, the screen, and the apps on the iPhone. They all have worked wonderfully for me, with just a few crashes while surfing or loading big email images. (I heard that shutting down the phone and restarting helps that.)
The single flaw for me is that the phone app itself should be primary, with more options (quicker access, unique ringtones, voicedial?) and ease of use. The other applications are so elegant, but I need my phone to be very accessible and practical too.
My wish list:
1) Make it fewer taps to get to the point where you can make a phone call. How about the main button can be programmed to take you wherever you want. I'd choose to go to Phone Favorites, so I could speed dial right away.
2) Be able to set a preference as to what app you're in when you wake up the phone. I'd choose phone keypad, some might choose iCal, etc.
3) Add the period and comma symbols to the alpha keyboard.
4) Allow different ringtones for specific caller ID's.
5) Copy and paste.
V2) With new hardware, add a "back" button to return to prev. screen. It could be small, on the side near volume?
2.33 ghz dual core Intel Imac Mac OS X (10.4.9)

How do I correctly import images into Lightroom?

Before installing Adobe Creative Cloud, I deleted Adobe Elements and all files in My Pictures on my hard drive so I could start fresh. I copied groups of images from CS5 Bridge on my old pc onto an empty flashdrive and tried to import them to Lightroom. In addition to those copied images, whole bunches of other images imported. Even worse, those added images were sorted strangely, not even belonging to the groups as I had them in my old pc.

Since you used the Copy import type, at least the images are also where they originally were, other than those on the flash-drive which was a temporary location for images from another location except when you plug it in.
So there seem to be two unexpected things: more images were imported than you wanted to be imported, and some of the images are in folders that don't match the date they were taken.
The folder-date mismatch might be due to some of the photos not having a taken-date in the exif information so the date they were last modified is used, instead. You should check your destination naming options in LR to see if you have things set to import into date folders or not. If not, then you actually specified that LR import a particular import's photos into a specifically-named folder that you typed the name of.
As far as how extra photos got imported, only you can answer that. It would have to do with where you told LR to import from and if you have Include Subfolders selected. There is a way to specify an Auto Import folder using LR / File / Auto Import where LR will watch for photo files and import photos it see show up in that folder, but I doubt that is the problem.
You'll have to decide on what to do now. If you have all the photos still on the flash drive, then you might want to start over. However, also think about if you want to be doing a Copy Import into your pictures folder from everywhere else, or if you want to use Explorer to copy the photos, yourself, outside of LR and do an Add import. A Copy import from the flash drive could make more sense, since that is only a temporary location for the photos, but for other photos already on your computer, an Add import might make more sense. If you use your OS copy commands to move photos from the flash drive to your computer's internal drive, you can decide what to name the folders, instead of LR choosing, if you have LR Import set to use dates.
If things aren't in completely the wrong places, you can drag-and-drop within the LR Library Folders panel to put things where you want, and you can also right-click Remove (without deleting from disk) any extra photos.
Also, there is nothing magic about the Pictures folder. You can choose to make a new folder and put your LR photos under it.
The bottom line is that LR isn't doing anything more than what you told it to do, and it sounds like you just aren't aware of all the settings enabled during your imports so unexpected things happened.

Things I Wish Were in Lightroom

Similar Messages

Maybe you are looking for