Search options

Merci Laurent,

It is ugly to have to do things outside QET but I understand the procedure and it's not too difficult.

I can even live with reentering the autonum schemes into each project, but I look forward to being able to save them as part of the QET config dialog...one day:)

Cheers
Patrick

Hi Scorpio,

Initially exporting my project still crashed QET, but deleting Sheet 2 and adding new Folio Summary back into project fixed the problem.
Now all sheets exported without crash.

Thanks Scorpio.

SUGGESTION:  Would it be a good idea to add the %idx (or folio label) as a prefix to exported file names?

PS. How do you "enable folio label"?

Our beloved leader has found something.

Now it's a question of where on the scale of difficulty the issue sits...

|--------------------|--------------------|
0                        5                       10
"Oops"            "Hmmm!"              "How the F#%! are we going to fix this?!*

Note: this scale may be logarithmic.

Yes, current scenario : I created a set of dwgs in QET - happy with the results, but now I have to pass dwgs to someone who will incorporate them into a larger set of AutoCAD dwgs - and AutoCAD is the only thing they use.

Generally speaking I think delivering documentation in DXF will be very important to anyone who might have to provide documentation to a customers in a recognised format that will work with their SW tools - typically some AutoCAD compatible format. 

You cannot argue with the customer that they can get QET as a free download. This is irrelevant because for them it is all about their workflow base on AutoCAD.

So for those who use QET only for internal documentation or pdf publications, there may be no issue.

For others, having DXF as an available export format is very important - unfortunately.

I completely understand Scorpio. It's really impressive what you and the guys do.

I can code a PLC but too little experience with coding for PC though it might be time to change the situation.

To understand QET would you recommend opening the sources in something like QT Creator? Or what does the Group use?

I know! I know! 

And it looks like the blade has come down on on the nightly branches?

The "head" revision, 4842, is missing! 

[EDIT-12Jan2017]  ...oh, no there it is.

Thanks for being flexible, Scorpio.

Just one final suggestion : can you have Save become enabled in the same way as the Save As button - that is, only when one or more projects are open. Having Save enabled with no projects open is a little freaky.

Cheers

Making the project path and filename visible in the SW was a good idea and generally speaking, very handy.

It was absolutely necessary to aid the work around of doing a "Save As".

FEATURE REQST: Any chance the project filename could be added as the default file name in the "Save As" dialog?

This would mean only requiring to pressing OK and you're done - safely.

Otherwise the work around leaves the possibility of making mistakes : you still have to enter the file name or click on a the matching file. In a directory filled with numerous and similarly named files there is a chance you could pick the wrong file.

Cheers
Patrick

PS : I still prefer the idea of just leaving the Save function enabled all the time - just One Click and you're done with no chance of making a mistake. 

It is not that I disagree with Scorpio - yes, ideally Save should only be needed when a change is detected, but hey!, we are at version 0.5 not 5.0 - the change detection code is incomplete.

"Save" enabled all the time is a workaround that would be easy to live with.

Apologies if I am being a PITA.