I'll try to reply to the last emails in one: 1- It works with compilers older than 4.7, they just changed the command line option in 4.7 from -std=c++0x to -std=c++11. Qt5 handles this but on Qt4 I have to do it manually.
2- I've checked in a fix for this but I don't have any files to test. I looked at the file you linked but I couldn't see any differences from before. Also, Philo mentioned LSynth,I don't have any files to test that either. 3- I agree that losing comments is a big problem but that's not easy to change so it will have to wait. I think the current version is almost ready for release and it's already a big step in compatibility and features so I don't want to delay until I can fix that. I've always been opposed to showing the text lines, I think it's not friendly for new or young users and I want to try to support everything you mentioned through the regular UI. A while ago I posted a screenshot of a timeline view but I don't think it was good enough so I didn't check it in. This is probably the most requested feature now so I'll work on it for the next version. Fading previous pieces could also be an option, would this help? I also updated the zip file with those changes. On Fri, Jan 9, 2015 at 8:02 AM, Milan Vancura <[email protected]> wrote: > On Wed 07-01-15 12:28:22, Leonardo Zide wrote: > > 1- They changed the command line option to enable c++11 on gcc 4.7, I've > > checked in a fix to the project instead of the patch since I know I'll > > forget and do the same thing again or use some other new language feature > > and it will break again. > > > > 4- This was a bug with the recent changes, it's fixed now. > > Thanks for these fixes. I checked that both work, at least with my gcc. > I'm not > sure what gcc < 4.7 does and if it was better to announce a dependency on > gcc > 4.7 or higher. > > > 2- This is a known issue, it's on my list but I haven't gotten to it yet. > > I'll take a look and if it's a simple change I'll fix it next. > > Thanks. (I can imagine this needs some time to fix.) > > > 3- Also a known problem. I've been working on making everything more > LDraw > > compatible but I haven't had a chance to fix this one. > > > > 3a- Not sure I understand, do you mean the text area with each line in > the > > file? > > Basically yes. But better to describe the use case: > > While preparing my model instructions I need to move bricks from one step > to > another, create, delete or merge steps and so on. Even some of these > actions > (if not all) are possible to do from graphical View in LeoCAD, there is > nothing > like 'Overview what's in each step'. > And more - if I used more applications while working on this .mpd file each > such application put its own 'comments' to the file. Then, when I need to > move > some bricks to a different step or submodel, I need to check such 3rd party > lines as well and decide if to move them too or not. > > So, in sum, the best would be some kind of "View sources", synchronized > automatically with what's in View. I believe not all text editing features > are > needed there, probably cut/copy&paste of whole lines + a context menu > offering > already existing LeoCAD popups (part properties etc.) would be enough. > We may discuss about that. > > I wanted to paint a picture of what this feature should be good for. > Does it make sense for you now? > > Milan > _______________________________________________ > Leocad mailing list > [email protected] > https://list.gerf.org/listinfo/leocad >
_______________________________________________ Leocad mailing list [email protected] https://list.gerf.org/listinfo/leocad
