Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Often I can't save new components in the libraries #120

Closed
Max2433BO opened this issue Oct 2, 2016 · 4 comments
Closed

Often I can't save new components in the libraries #120

Max2433BO opened this issue Oct 2, 2016 · 4 comments
Labels
enhancement A suggestion about how to improve the project user interface Improvements related to the user interface

Comments

@Max2433BO
Copy link
Contributor

HI, @DarwinNE

I shall quote a problem reported by a mutual friend from electroyou.it site:

when you create a new component for FidoCadJ (I suppose the 0.24.6 version, but I'm not sure) libraries and you save it, often does not accept the new component because the key number is already assigned.
In order to save the new component we must make a series of attempts by assigning a random number.
... And if you are unlucky, it happens sometimes, you have to try and try again several times. :(

This is ... I haven't tried it, and I will propose as is.

Bye, Max

@DarwinNE DarwinNE added enhancement A suggestion about how to improve the project user interface Improvements related to the user interface labels Oct 2, 2016
@DarwinNE DarwinNE added this to the FidoCadJ 0.24.7 milestone Oct 2, 2016
@DarwinNE
Copy link
Owner

DarwinNE commented Oct 2, 2016

Hi @Max2433BO
If I understand correctly the problem, a solution may be to put the background of the key field in red if the key can not be accepted (because incomplete or replicate in the library).

Cheers,
D.

DarwinNE added a commit that referenced this issue Oct 2, 2016
…he key text field of the DialogSymbolize.
@DarwinNE
Copy link
Owner

DarwinNE commented Oct 2, 2016

Here is my solution. An invalid key is shown in this way:

invalid

Here the key is invalid as there is a space. The key does not need to be a numerical code, btw.
If the "ok" button is clicked anyway, the usual error message appears.
Now the program checks if the code is available or not before choosing one more or less randomly.

@Max2433BO
Copy link
Contributor Author

Hi, @DarwinNE ,

it's a good idea for me ... now we have to hear what think our mutual friend ;)

Bye, Max

@DarwinNE
Copy link
Owner

Ok, I close this issue now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement A suggestion about how to improve the project user interface Improvements related to the user interface
Projects
None yet
Development

No branches or pull requests

2 participants