Problems with checkouts

Hello PushOk-team,

I don't know, what you mean with "please respond to customer", but I
checked this behaviour several times. This non-sense-error-message appears
only in this special case. If I have a pre-commit-hook that fails, the
error-message is displayed correctly. So it seems to be only this special
case.

Kind regards,
Daniel Hilgarth,
pi-consult gmbh

Î just discovered, that you are checking the value of the svn:needs-lock
property. When it is '*' it works!

But still, other users who try to check-out this file will get this strange
error-message instead of a nice one :)

Kind regards,
Daniel Hilgarth
pi-consult gmbh

Very strange. You are right, the first issue is gone.
The second however not. I try to explain again:
I have to working copies of a project which is in subversion. In one
working-copy I lock a file using TortoiseSVN->Get Lock. When I now try to
check-out the same file in the other working copy in my IDE using your
plugin I get the described message and the file is in an undefinded state.

Please tell me, what is supposed to happen, when I specify the attribute
"svn_require_lock" to a file.
I tried the following:
In the config-file of subversion I specified the following:
[miscellany]
enable-auto-props = yes
[auto-props]
*.rc = svn:needs-lock=1;svn_require_lock=1
resource.h = svn:needs-lock=1;svn_require_lock=1

This means that all *.rc-files and all resource.h-files automatically get
the specified properties (or attributes as you call it). But your plug-in
doesn't treat files with this properties differently... (I checked the
files, the attributes are applied correctly...)

Kind regards,
Daniel Hilgarth
pi-consult gmbh

Hello PushOk-team,

- If I have checked out a file and use "Get latest version" on this file it
is being made read-only so I can't edit it anymore.
- If a file has been checked out exclusivly and someone else tries to check
this file out he get's a nonsense error-message ("Unexpected error." "The
operation completed succesfully."), which is shown in a message-box.
Additionally, this file is in an undefined state (You can't try again to
check it out, because the checkout-button is grayed). Only after "Update
status" it has a defined state again.
- Currently it is only possible to switch on exclusive checkout for all
files. It would be good if you could provide an option which let's the
users check out the files concurrently except some defined files.
Scenario: The programmers want to work on the same file at the same
time (concurrent checkout). But with some files this is makes no sense,
because they can't be merged (binaries, resource-files [*.rc and
resource.h]). So it should be possible to define which files should be
checked out exclusivly. And then only those will be checked out
exclusivly.

I use version 1.2.1_050822

Kind regards,
Daniel Hilgarth
pi-consult gmbh