Nabble - LibreCAD needs help

Need help on v3

2024-04-01T15:26:58Z

Could any v3 developer fix GitHub actions (continuous integration)?

Re: Test new macOS package

2022-01-10T11:54:39Z

Hi abubk,

it turned out, that issues happened with LibreCAD-2.2.0-rc3.dmg on Big Sur. Presumably it is not related with M1 CPU.
Anyhow, I assume that your M1 Mac has Big Sur and thus you need LibreCAD-2.2.0-rc3-BigSur.dmg.

With automatic builds coming soon this should be solved and we can return back to one package for all MacOS in future.

^{investing less than half an hour into Search function can save hours or days of waiting for a solution}

Re: Test new macOS package

2022-01-10T04:28:13Z

Hey are you using the m1 Macs. I want to know which package to download LibreCAD-2.2.0-rc3-BigSur.dmg or LibreCAD-2.2.0-rc3.dmg. What's the difference? any idea?

Re: Test new macOS package

2021-12-15T11:16:56Z

Many thanks for testing and reporting.

But sad to hear about the zoom issue. I tried hard, but I can't reproduce it on Linux.
Is this with a specific file only or other drawings too?
Can you describe the steps more detailed?

^{investing less than half an hour into Search function can save hours or days of waiting for a solution}

Re: Test new macOS package

2021-12-14T19:07:13Z

New Mac OS package user. I am running Monterey OS. Librecad 2.2.0 rc3 downloads fine. Currently it crashes when using the zoom function in conjunction with another function - say move/copy. It causes the whole system to freeze. Force quit and restart is the only way to get around this. Will push on. Have not had it long enough to use all functions.

Re: Test new macOS package

2021-12-06T12:50:10Z

No problem, you're welcome.

^{investing less than half an hour into Search function can save hours or days of waiting for a solution}

Re: Test new macOS package

2021-12-06T00:56:22Z

Sorry to waste your time. Yes it looks as if I had accidentally turned the print off for the layer. Thanks for the quick reply.

Re: Test new macOS package

2021-12-05T03:30:09Z

It works for me with with latest 2.2.0-rc3 package on High Sierra.
Sure that the printer icon in the layer is activated?
Or an issue with layer 0 color setting?

^{investing less than half an hour into Search function can save hours or days of waiting for a solution}

Re: Test new macOS package

2021-12-05T02:11:28Z

Hi,

Just noticed (on my Mac) that elements in layer 0 do not appear in the print preview. Is this by design or a glitch?

Re: Test new macOS package

2021-10-28T22:42:53Z

More on the Layer List.

Item 1

A left click selects a layer. I can then right click to access the edit layer dialog box.

However, if I then move to another layer and right click to access the edit layer dialog box LibreCAD does not focus on the second layer and the edit layer dialog box brings up the previously selected layer. I do not think this should happen. If I select one layer then right click on another layer and select toggle visibility, it toggles the second layer selected even though the edit layer box remains attached to the previously selected layer. This means I can only edit the layer attributes if I first force it into focus.

Item 2

If I want to toggle a layer into and out of view the behaviour of the layer window is strange. If the selected (focused) layer is present in the layer window I can do it (that is if the layer is close to the selected layer and I toggle, the window list does not change). However, if I scroll away from the selected layer so it is not visible in the layer list but is still the active (focused) layer and then toggle an item, the list resets itself so that the active layer is in the list window, either at the top (if the toggled layer is after it) or at the bottom (if the toggled layer is before it).

This can be frustrating when concentrating on the drawing and trying to toggle an item on and off to see if (for example) the entities are in the correct layer. Due to the movement of the list I end up toggling another item unintentionally.

Geoff

Re: Test new macOS package

2021-10-28T22:14:21Z

More on Filtering.

Applying a filter selects the appropriate layers but any pre-existing visible layers remain on the drawing area. Toggling the filtered selection then only applies to the limited selection with the pre-exiting entities untouched and I believe this is how it is meant to work? Consequently, to only see a filtered group of layers it is first necessary to hide all layers, then filter, then unhide all which will only unhide the filtered layers.

The only problem I have encountered so far is that from time to time LibreCAD appears to lock into the filter so that even when the filter command line is empty (using the deletion cross) the drawing is still filtered. I have overcome this by filtering on "*" which selects everything and brings back all layers to view.

Geoff

Re: Test new macOS package

2021-10-26T03:55:53Z

QCad has an item (pro) called Layer States where the defined visible layers can be saved en block. Is there any chance this might be on the horizon for LibreCAD?

Geoff

PS I tried to add a key (Letter) to the layers I want to group and then tried to filter them but the filter is not a search function and is also case sensitive so it would not find my filters.

I managed eventually by adding ViewA at the end of the labels of the layers I wanted to group and then filtered for "* ViewA", however it is a bit cumbersome to do. A neater solution would be helpful when there are so many layers (my drawing currently has 40).

Geoff

PPS I have suffixed my Electrical layers "ViewA" and my Plumbing layers "ViewB" then my building outlines (Walls, Insulation, plasterboard) are given "ViewA ViewB ViewX etc."

I can then select "* View" (to see the entire subset) or "ViewA", "ViewB", ViewX, etc. to see more defined subsets with the outlines always present. It works but requires a bit of planning and label changing. An additional column in the Layer window that filters in the same way would be helpful.

Geoff

PPPS This is not just a Mac issue!

G

Re: Test new macOS package

2021-10-26T03:53:49Z

LoF,

I will keep replying to this post with items I find that are either problems or a Wishlist (unless there is a better place for the Wishlist?).

So here is the first.

How difficult would it be to change the attributes window so that the attributes of the selected item are shown (as a reminder) rather than the drop down lists showing "Unchanged".

Also, if I do not select an entity but select Attributes it applies that attributes to any item I select but I do not see what those attributes are. If the layer is one of the attributes changed but that layer is not currently viewed, the entity disappears which can be disconcerting. so, is there a way to show the selected attributes when the function is used this way?

Geoff

Re: Test new macOS package

2021-10-25T03:26:19Z

Re: Test new macOS package

2021-10-25T03:25:51Z

Re: Test new macOS package

2021-10-25T03:24:54Z

Hi and thanks for the response. I am attaching two images, one that shows the normal background and one with the background changed to white. Both show the command line in black (and the text unreadable). So far this is the only box that seems to be affected. It may be to do with Dark Mode but these shots are taken in daylight mode. I have not played with style sheets, the only thing I have tried is to change the colour of the background. Sorry about the layout but I cannot seem to get the system to show line breaks. I will post each image as a separate reply. Geoff

Re: Test new macOS package

2021-10-24T07:52:33Z

Geoff, many thanks for your report about the working Big Sur version.
There are no open questions from it.

Concerning the status line glitch, there is already an issue report on GitHub.
This is related with auto save, the status bar is toggled for this message and forces a layout rebuild.
It can disturb drawing, when it happens just on mouse input, but not more.

I can't say, why your command line has black background. I've not heard that before and it is surely not intended by any newer version.
Is the command box the only input field which is affected or are there others too?
Maybe it's somehow related with a dark desktop schema?
Or have you played around with Qt style sheets? (see https://github.com/LibreCAD/LibreCAD/wiki/Style-Sheets)

^{investing less than half an hour into Search function can save hours or days of waiting for a solution}

Re: Test new macOS package

2021-10-24T02:39:51Z

BigSur version.

When using the command line the entry box is now black (it used to be white). not sure what colour text is used (grey?) but it is virtually impossible to read as I am entering the text. Is there a way to reset it or is it something that needs an update?

Geoff

Re: Test new macOS package

2021-10-17T06:57:10Z

Hi LordofBikes,

Are you still looking for feedback from Mac users?

If so, are there any specific areas you would like feedback on?

I have installed the 2.1.3. and 2.2 Big Sur versions on my MacBook Air (Big Sur) and both installed and now work OK. There are some glitches from time to time with Big Sur on saving (autosaving?) but I have not recorded incidences logically but if required will now do so.

I have also installed 2.1.3 on my late 2010 iMac which also installed fine and is now working well. I am working on (architectural) drawings across an internal network to see if one version causes problems in the other and thus far I have not seen any.

Are there any test sheets you use for recording issues or do you just want a free text description?

I had thought the project had stalled so was delighted to see 2.1.3 available. The first massive improvement for me was that I am now finally able to print directly from LibreCAD instead of going via a pdf export to do so.

I am happy to help in any way I can to support what is a really good and useful open licence project. Just point me in the right direction.

Geoff

Re: Test new macOS package

2020-11-03T20:21:19Z

I have the habit of "E+space bar" from Autocad, Like to stick to commands when ever possible.

Re: Test new macOS package

2020-11-03T20:20:09Z

So more details, I can't snap!
Once I enable snap, say snap at end points, I have to restart Librecad to make it work and it only work once. I have to restart again to make it work again.

OS: MacOS catalina 10.15.17
Macbook Pro 13 early 2015 edition

Re: Test new macOS package

2020-10-28T10:51:35Z

Trigger delete function with space bar? Just select the the items and press delete key, gone!

Re: Test new macOS package

2020-10-28T07:24:09Z

Installed just now;
Version: LibreCAD-2.2.0-rc1-254-g9f2c32dd.dmg
OS: Catalina 10.15.7
Device: Macbook pro 13 (early 2015 edition)

So far it is good, No problems in general drawing and saving files except for the delete function. I don't know if it is a bug, but the delete function cannot be triggered with space bar. Also the delete function is weird, I have to select items > activate the command "del" > and re-select any one item to delete it. If I select first and then type in command, nothing happens. I had the same issue in Manjaro as well, so not a mac problem.

Re: Test new macOS package

2020-05-17T09:53:14Z

I am running High Sierra on a mid-2011 iMac. It installed with no problem at all. Thank you!

All I've done so far is draw a single line just to see that the space bar worked. :) But I have more to do after the weekend.

Now, I tried to understand the instructions about building my own installation and I have to say I got nowhere. The instructions are written by people who know the material very well, for people who know the material very well, and not in such great English. People like me, who use a Mac because they want a simple life... don't really fit in there. But I can write instructions, so if someone could help me understand the build process I would be happy to rewrite the instructions in the Wiki.

Test new macOS package

2020-04-27T11:26:29Z

We need some help from Mac users.
There is a new V2 DMG package available at https://sourceforge.net/projects/librecad/files/OSX/2.2/preRelease/
The package LibreCAD-2.2.0-rc1-192-g24027e44.dmg was built from latest code on High Sierra (10.13.6).
It is in release candidate state and thus as stable as the latest 2.1.3. release and even more stable as the latest alpha package from 2016.
It would be great, if some Mac users can test this package and report about the macOS version and how it worked.

Many thanks for your support!

^{investing less than half an hour into Search function can save hours or days of waiting for a solution}

Re: tool descriptions

2017-06-16T03:02:14Z

Gary, I am beginning to think that I am not your Man for this project of understanding.

Additionally, I am not sure that my 32 bit laptop is up to it, there are too many mysteries, things disappearing,
Parallel not working, snap all over the place, move and copy very temperamental etc.

I have got over some of these matters by using my Mac (64 bit), but I really do want to make Linux my success story.

I do apologise to you all, but Librecad is not revealing itself as a tool of certainty.

Kind regards to you all,

Cy

Re: tool descriptions

2017-06-12T04:32:44Z

Hi all,

Need to get up to date on the section beyond Tools, so nothing to offer yet. I hope that, that is ok?

Regards,

Cy

Re: tool descriptions

2017-06-08T05:49:23Z

@ Gary,
Hi Gary,
Your writing for the Tools needs some 'getting up to speed' on from me so I will get back to you on that.
Your KLR-650 is nearly as exciting as Western Canada. My wife and I only got as far as Toronto and London, Ontario, but we love Canada very much. Got offered a job with Architects in Nova Scotia in the 70s, but a friend in Toronto thought it might be a little quiet for me, how wrong we both were.
Cheers,
Cy

Re: tool descriptions

2017-06-07T09:55:00Z

Not waiting around...

I've finished the Tool descriptions. Please proof-read and edit as necessary...

This script did the trick for me, but adjust to suit as required *...

#!/bin/bash

SOURCE=LibreCAD-WIKI-Tools.txt
TARGET=lc_actionfactory.cpp

# Strip formating characters, replace with delimiter:
#    replace all "'''" with (null)
sed -i -e "s/'''//g" $SOURCE
#    replace all " {" with "|"
sed -i -e "s/ {/|/g" $SOURCE
#    replace all " }" with "|"
sed -i -e "s/}: /|/g" $SOURCE

# Read through SOURCE and parse fields; toolName|objectName|Description

while IFS='|' read toolName objectName toolDescription; do
#  echo $toolName
   echo $objectName: $toolDescription

   # Find objectName in line "action->setObjectName('objectName');"
   # and insert a new line above consisting of "action->setWhatsThis('toolDescription');"
   sed -i "/setObjectName(\"$objectName\"/i \    action->setWhatsThis(\"$toolDescription\");" $TARGET

done <$SOURCE

Edit: added missing ";" after setWhatsThis(\"$toolDescription\")

*: BTW, it has been a long time since I've done any coding, and never in a QT environment, so ** please ** ensure the inserted line is the correct syntax, etc...

@All
I'm willing to continue to develop or enhance other wiki pages, updating and adding as required. I see that there are others that are writing manuals, so I'd like to focus on short descriptions and aligning command where available. Any thoughts on that??

@ Cy
I ride my KLR-650 through the foothills and mountains of western Canada...

Cheers,
Gary S

Re: tool descriptions

2017-06-07T01:34:48Z

Gosh Gary, yet another Bike man. I do miss them especially my old T110. What have you got at the moment?

Good job you informed me that all the Tools are done, never the less, something to look back on to get an idea of what is required.

Cheers to you also,
Cy

Re: tool descriptions

2017-06-05T01:59:48Z

Gary, once again, many thanks for sharing your knowledge with me, it is most appreciated.

I do wish that I was a little further on with doing what is required. Still, I feel more positive today.

Kind regards,

Cy

Re: tool descriptions

2017-06-05T01:47:53Z

Thank you Gary, that is most helpful. I suppose many of my problems in understanding moat of this, comes from my struggle to relate it to all the other cad applications that I have learnt and used, much of it being the missing sequences.

Kind regards,
Cy

Re: tool descriptions

2017-06-04T10:36:58Z

Cy O'Hara wrote

...
Item 2) I would understand this Simple text idea if, we were doing this for Writers and not Users
....
Item 5) So, in addition to the Tool name, what is our job? Written process description?

Hi Cy,

This information is for the users, but not as a separate document / manual. The description of the "Tools" menu item is 'embedded' within the applications and will appear when the a user moves the mouse over or selects the tool (at least, that is the way I think it is suppose to work) - think of pop-up tool tips. That is why it needs to be a brief and written in a very specific way using simple text - it allows the descriptions to be 'imported' into the applications code when the descriptions are complete. Images and other graphics cannot be used.

It is not a process description, but a description of what the tool does (with a couple of additional details as "Draw a line." seems to be pretty obvious, but "Draw a line between to specified points" offers the user a better hint of what the particular tool will do).

At a later date, I feel that these short descriptions can be expanded on in a separate wiki page to be a more complete description of the tools and many options that are available. At that point the document can include images, etc. There already is a "User Manual" that offers a guide and examples for users available on the wiki, but I don't think there is a complete description of the available Tools, Snaps, Docks, etc.

Cheers,
Gary S

Re: tool descriptions

2017-06-04T01:43:47Z

Thank you Gary, that is most helpful.

However, it now seems clear to me that i am not understanding what is required here. I thought we were doing this for Users.

Item 1) is now clear.
Item 2) I would understand this Simple text idea if, we were doing this for Writers and not Users.
Item 3) As item two, this would be clear to me for Writers but not for Users.
Item 4) I seem to remember this being said, so it is probably me with a senior moment, sorry.
Item 5) So, in addition to the Tool name, what is our job? Written process description?

I am beginning to think that I am not equipped to do this job.

Kind regards,

Cy

Re: tool descriptions

2017-06-03T07:41:30Z

Hi Cy,

I can answer those questions...

1. I'm using 2.2.0-alpha (and since the descriptions will be imported into that, or a later, version I think it is appropriate).
2. It possible, but it wouldn't be the right way to do it as any formatting done in Impress cannot be used. Only simple text can be used (I work with a text editor similar to notepad).
3. No, we cannot use images of any kind.
4. I thought I had stated in the preface that is was based on ver 2.2.0-alpha. If it is not there, I'll put it back.
5. There are no descriptions in the code - just the "Tool" name.

Gary S