Polyline - Simplify option, the icon is missing.

The tool still functions as expected.

In Windows, set up say 2 or 3 new blank drawings.Then close them down one by one and notice the behavior when closing these drawing windows down!

Selecting print from Main menu > File > Print - not working.

Print function only working from selecting the Print icon button from within the Print preview stage!

How to reproduce:
Go into App Preferences, in Graphics View→Navigation, enable pan gesture. Now add any drawing and pan around for ten seconds quickly, not taking the fingers off the mouse/touch pad. Take the fingers off the pad now.

What goes wrong:
QCad will pan around the drawing for another 30 seconds or so, dutifully executing all the buffered mouse moves.

Suggested solution:
Qt buffers more mouse pan-moves than QCad can handle. QCad executes every move in the buffer, making the pan feature close to unusable. The zoom function has the same bug, but it much less pronounced.

This is easily solved: when receiving a pan event (two finger scroll), just check if there are more events in the queue. If there are, accumulate the effect, but don’t draw yet. As soon as the buffer is empty, kick off the redraw. The result is a *much* more fluent and responsive user interface.

Please fix soon. This wonderful feature makes life so easy, but currently it is unusable. Thanks. Matthias.

When loading a block that has a drawing set to “color by layer” into any layer but “0”, it will still always show the color of the “0” layer.

However, it should show the color of the layer that this Block is in (this is likely true for all the other attributes).

Compare.markDifferences = function(newAndMissingIds) {
...
            entity = Compare.doc1.queryEntity(id);
            entity.setColor(new RColor("green"));
            op = new RModifyObjectOperation(entity.data());
            Compare.di1.applyOperation(op);

ECMA code:

         QScriptValue
        REcmaSharedPointerEntity::setColor
        (QScriptContext* context, QScriptEngine* engine) 
        {
            QScriptValue result = engine->undefinedValue();
                    // public function: can be called from ECMA wrapper of ECMA shell:
                    REntity* self = 
                        getSelf("setColor", context);
=>               Q_ASSERT(self!=NULL);

Stacktrace:

Thread [1] 18673 (Suspended : Signal : SIGABRT:Aborted)	
	__kernel_vsyscall() at 0xffffe424	
	raise() at 0xb4efc8df	
	abort() at 0xb4efe220	
	RMainWindow::messageHandler() at RMainWindow.cpp:63 0x8f3917a	
	qt_message_output() at 0xb5356f65	
	0xb53571ab	
	qFatal() at 0xb53572c9	
	qt_assert() at 0xb5357355	
	REcmaSharedPointerEntity::setColor() at REcmaSharedPointerEntity.cpp:1,360 0x8bc0602	
	0xb6bd813c	
	0xb6ac1f68	
	0xb6a9164c	
	0xa622afd2	
	0xb6a423e3	
	0xb6af06e0	
	0xb6ac201e	
	0xb6be0cd3	
	0xb6be11a9	
	QMetaObject::metacall() at 0xb5478c83	
	QMetaObject::activate() at 0xb5489134	
	<...more frames...>	

It seems that QCAD and Autocad treat solid fills differently. Here is attached
example and its view in QCAD and autocadws.com web service. I found that order
of vertices is important.

Thank you
Mikhail