Hi folks,

It's that time of the month when I bitch, whine and moan until you commit
your changes to the repository!

   COMMIT FREEZE FOR 6.5.0 alpha 2:   00:00 GMT SEPT 20th 2005!

That's when the tag's going into CVS, so please make sure you've committed
all of your brilliant hackery by then!

Thanks,

Peter

--
Quake II build tools: http://peter-b.co.uk/
Latest QuArK:         http://quark.sourceforge.net/LatestVersion

v2sw6YShw7ln5pr6ck3ma8u7Lw3+2m0l7CFi6e4+8t4Eb8Aen4g6Pa2Xs5MSr5p4
   hackerkey.com



--

Quake II build tools: http://peter-b.co.uk/
Latest QuArK:         http://quark.sourceforge.net/LatestVersion

v2sw6YShw7ln5pr6ck3ma8u7Lw3+2m0l7CFi6e4+8t4Eb8Aen4g6Pa2Xs5MSr5p4
   hackerkey.com

Howdy regedit_77 ;-)

> I am interested in game development. Currently I am writing a 3D
> engine and I think it would be nice to create maps in QuArK instead of
> making my own world editing tool.

That's cool to hear about your engine and no it would be a lot of extra
work to reinvent the wheel you might say. ;-)

> So I have a question: How to add support for a new game/engine? Is
> there any tutorial for this? I have read the manual, but I still don't
> know:

Unfortunately, no. Just what you read in the Infobase so far. But I
will give you what I know so far that might help.

> - Why should I modify QuArK source code and recompile it all just to
> add a new letter signature?

From what I understand, that is just so you can control what QuArK uses
in the way of its own functions when it starts up. But there may be
more to it than that. However, putting it on the start up game mode
menu is done in the Defaults.qrk file and not the source code. The core
of the whole thing seems to be based on the idea that if your engine
handles polys pretty much like another engine then you should be able
to use what is t
here already. If not then you can add a new section in the Default.qrk
file. But that would not go out for general distribution, just for your
own use.
So that is the way I would go. If it's like Q2 or Q3 then use the Q2 or
Q3 mode and game code or make up your own.

> - How to create my own list of entities?

That, I think, is the real key on how QuArK works for new games and
engines. And once you get the hang of it, really is not that hard to do.

It starts with the Defaults.qrk file in the addons folder. That is
where new types of input forms and your basic "game engine" defaults
settings are kept, which get loaded first (maybe the quarkpy and
plugins before that, but that's not important here).

Then the game addons, in the order that they are registered with QuArK
in your config section for addons starting with the "Data" file like
DataQ2.qrk for example, the "UserData",  UserData Quake 2.qrk, and
finally the rest of the addons for that game (I believe it is setup
this way in the source code). Each time a new file is loaded and if
there is a duplicate of a variable name defined in its code, then the
previous code for that name is over written and takes on the new
characteristics of the newer code.That is why you should register your
game engine addon so it will be the last one in the list.

Also the handling of the path to where QuArK looks for and writes files
to is done in your new addon.qrk file, even its capability to look
into ".pak" files to get data like for the QuArK Texture Browser.

A good example on how to set that up would be to look at the
DataQ3CoD.qrk file in your Quake_3 addons folder, that I made about a
year ago. This sets up its own "base" game folder within the Quake3
main game folder. So that should give you a good idea on how to set up
the paths for your own engine game folder, base folder and sub-folders.

The same goes for your entities, they would be setup in your
DataXXX.qrk file and looking at a few others will guide you in doing
that. that is why you will see the headings for a lot of addon qrk
files will actually have another games name because people have just
started with a copy of the original file and created their own from
it. ;-) That makes it a little easer.

> - How to create .MAP output file for my processing tool - the same
> file format that is used in Quake 2 or other similar, wihout
> duplicators, negative polus and other QuArK stuff, but with walls
> already cut - just a simple list of polys and entities.

Now that area I am not well experienced in, so take it for what it's
worth...which is probably not much...but basically, from what I
understand, QuArK writes its own .map file to its tmpQuArK folder
(where you determine that should be in your Defaults.qrk file game/path
coding) and then runs your game compiling tool(s), which are usually
kept in a folder you create in the main game folder and called
something like "QuArk files", to use that .map file to create the
actual game type file format.

QuArK automatically crates the map and texture sub-folders in its
tmpQuArK folder and places the map's and compiled files there for you.
Then you just need to move them to the game (engine) folder. If you run
the game while still in QuArK it will point to its own tempQuArK for
the game to try and use the files where they are placed by QuArK. This
doesn't always work depending on how flexible you write your game
engine. So you might want to keep that in mind as you make it. ;-)

Well, in a nut's shell, that's pretty much it! I think 8-|

HTH and good luck,

cdunde

Hi!

I am interested in game development. Currently I am writing a 3D
engine and I think it would be nice to create maps in QuArK instead of
making my own world editing tool.

So I have a question: How to add support for a new game/engine? Is
there any tutorial for this? I have read the manual, but I still don't
know:

- Why should I modify QuArK source code and recompile it all just to
add a new letter signature?
- How to create my own list of entities?
- How to create .MAP output file for my processing tool - the same
file format that is used in Quake 2 or other similar, wihout
duplicators, negative polus and other QuArK stuff, but with walls
already cut - just a simple list of polys and entities.

I found what was causing the problem in mapentities.py v1.37
and it turned out to be a couple of things. But basically it was
only in the handle section for controlling the spotlight direction.

1) The first thing, as you can see in the screen shot below, is
that it gets passed to all face handles for all games. So a simple
qualifying "if" statement testing if it is dealing with the specific
['_cone'] or ['_inner_cone'] and if it is in the HL2 game mode
should take care of that.

http://dynamic.gamespy.com/~quark/mapentities1.jpg

2) When it got down to line 386 where it has:

           if len(o.dists)!=0:

that is what caused the console error message because "o" is a
face object and does not have an attribute for "dists" apparently
and since that was used as the code carried through that kept causing
to problem to arise. So as you will see I commented those lines out
and used "o.vertices" instead because that is what you had tested for
a few line before that. Anyway, it accepted that.

3) But when it reached line 413 it eroded again for something like
"Improper vertex application" or something like that.

                 pointpos= d*o.normal+p

Because you where trying to deal with vectors, which d, o.normal and
p are, that just seems to be a simple method application error so I
once again commented that line out and used this instead just to get
it to continue on in the code:

                 pointpos= p

4) when it reached line 416 it eroded again but this time in
maphandles
because that line calls that file and passes these arguments:

                 h=h+ [maphandles.SpecialHandle(pointpos,100)]

The console error message showed this:
=====================================

Traceback (most recent call last):
   File "C:\QuArK_6.5.0alpha1_81805\quarkpy\maphandles.py", line 148,
in getcurso
r
     n = view.proj(self.pos + self.face.normal) - view.proj(self.pos)
AttributeError: 'int' object has no attribute 'normal'
Traceback (most recent call last):
   File "C:\QuArK_6.5.0alpha1_81805\quarkpy\maphandles.py", line 148,
in getcurso
r
     n = view.proj(self.pos + self.face.normal) - view.proj(self.pos)
AttributeError: 'int' object has no attribute 'normal'
Traceback (most recent call last):

====================================

The part where it said 'normal' told me that it was looking for
a "face"
to work with, so I checked the maphandles class that it was sent to:

class SpecialHandle(FaceHandle):
     undomsg = "drag edge"
     hint = "control point for height"

     def __init__(self, base, face):
         pos = base
         FaceHandle.__init__(self, pos,face)

Sure enough, it wants a pos and a face
and line (now) 416 was sending it a value instead of the face object:

     h=h+ [maphandles.SpecialHandle(pointpos,100)]

So, once again, I commented out that line and changed "100" to
the "o" face object:

                 h=h+ [maphandles.SpecialHandle(pointpos,o)]

As soon as I did that the console errors where gone and everything
started working.

I realize that it does not give you exactly what you want but at
least now you know
what parts need to be changed and that it needs a qualifying
statement to make it
work with just what you intended it to work with.

The other code changes from v1.38 to v1.41 are most likely fine and
maybe even
v1.42. But because that version broke the views there might still be
something else
but if so then at least you have it isolated to just that code and
can probably fine
and fix it without too much trouble.

Because the line numbers I have given above are from my changed copy
I will just post
here that section of code and you can just correct your original copy:
================================================

         try:
           print "vtx"   #
           for vtx in o.vertices:    #
              print vtx   #
              print "o.name is ",o.name
              print "took o"
     #1      if len(o.dists)!=0:
           if len(o.vertices)!=0:
             print "dists"   #
      #2       delta=1.0/len(o.dists)
             delta=1.0/len(o.vertices)
             print "delta is ",delta   #
             u=delta/2.0
      #3       for dists in o.dists:
             for dists in o.vertices:
               pa=line(u,vtx[0],vtx[3])
               pb=line(u,vtx[1],vtx[2])
               print "u,pa,pb are "   #
               print u
               print pa
               print pb
               u=u+delta
               print "u is ",u   #
               v=delta/2.0
               oldpointpos=pa
               for d in dists:
                 p=line(v,pa,pb)
                 print "u,v,p,d are "
                 print u
                 print v
                 print p,type(p)
                 print d,type(d)
                 print "o.normal ",o.normal,type(o.normal)
           #4      pointpos= d*o.normal+p # just needs dif. method of
doing this.
                 pointpos= p
                 print "pointpos is ",pointpos
           #5      h=h+ [maphandles.SpecialHandle(pointpos,100)]
                 h=h+ [maphandles.SpecialHandle(pointpos,o)]
                 v=v+delta
           else:
               print "skipped len section"
         except:
           exctype, value = sys.exc_info()[:2]
           print exctype, value
         return h

================================================

Like I said in my last e-mail to you guys, if you can get it fixed in
time then we
can still get it into this release. So you can just do a posting to
the board here
so I will be sure to get that and we can wrap this thing up.

HTH,

cdunde

I e-mailed this to you both, but just incase there is a problem and
you do not receive it I also posted it here for you.

----- Original Message -----
From: cdunde
To: cybox ; cybox ; Alexander
Sent: Tuesday, August 16, 2005 12:05 PM
Subject: May have found mapentities.py file problem

Hi Alex and cybox;

While testing the latest files I noticed something that might help
you.

Previously I needed to comment out and change back a couple of lines
of the mapentities.py v1.42 with my v1.43 because they where causing
the editor views to go gray as you recall.

I just noticed that there was still an error being printed to the
console about an unknown entity.
Things still worked but the error was being printed.

After tracking this down it also was in the same file and started to
occur in mapentities.py v1.37 where a lot of code was added for the
[ '_cone'] and ['inner_cone' entities] (lines 651 and 656) . So I am
guessing those are the entities that the error is referring to.

I also noticed that just above those in line 649 that some code used
["angles"], so I tried changing the new ones to double quotes from
single quotes hoping it might just be a syntax error. Unfortunately
that did not fix it.

Is it possible that those new entities have not been defined or
declared somewhere else and thus QuArK does not know how to handle
them? Or may be they where but in a different way.

Finding a fix for this may just also fix the views problem as well.

Right now the easiest way to fix this (if you can call it that) is to
step this file further back to the 1.36 version by adding the log
posting so far. But that leaves out all of that added code and any
following it up to v1.42. However, the files are still in the CVS so
it is easy to download and work from the v1.42 copy and\ or any of
the previous version copies, solving the problem in 1.37 and then
stepping it forward or just testing that fix with v1.42 to see if
that solves it for the view as well. If not, then something else in
that version has caused a problem and it just got compounded along
with the rest. Hate those bugs, Hu? Well we all get them that's for
sure.

So I will make that step back for now and I realize it may break
something else in the HL2 or other games lighting functions, I hope
not, but with this information it might help to find a quick fix and
we can get that in before the release and bring it back up to where
you left off.

If I can be of any other further assistance please let me know.

Best regards,

cdunde

I sent a previous e-mail to you guys yesterday, by my time zone, but
I have had no response. So I will post this to the quark-python board
as well just incase there is a problem with your ability to receive
my e-mails as you stated in the past. If you did not receive
yesterdays e-mail please let me know.

Apparently you made your post while I was answering Alexander's first
post response.

Mine is now posted as well, please read that one so you are aware of
what was said, although very little involves you directly until the
very last of it.

>
> Concerning the logo, I made the decision to include the logo even
within
> our Alpha4 release (as a preview), and I thought you'd agree with
that.

  I believe that you had good intentions about that cybox, but no one
that I am aware of knew about it or agree to it except perhaps
Alexander. And I never saw any communications or posting that it was
going to be done until you had sent yours out about it.


> All I did after that was to re-edit the NEWS.txt to add that change
> (which was already made days before) shortly before the release.

The change was made, but not the NEWS.txt posting until after I had
sent my e-mail, with ample time to receive it, and without going back
to check right now another had made comment about the logo as well.


> So far to clarify things.
>
> And now I am not able to create the release because someone has
> removed my rights to commit files ?

Yes, I did if you are not awair of that.

> I'm sure this isn't the right way to communicate at all.
> (I do not even see a real reason within your e-mail).

I am not sure what you mean by that, but all of us have the right to
present ourselves as we wish when it comes to our e-mail and privacy
setting as you are well aware of.

> I am working on this project to learn things, to communicate with
other people,

I believe that you are, that others recognize that and you in my
opinion are doing an excellent job of both. I appreciate and commend
you of that.

And, as I have indicated all along, I believe you unfortunately have
become swept up in a very uncomfortable and awkward situation even to
the extent of coming a victim yourself.

> but I am not willing to continue my work under these conditions.
>
> Please think about your decision, otherwise I must leave the
project,
> I really don't want to stay here with a knife in my back all the
time :)
>

If I felt like I had a knife in my back, I would not stay either. But
that is not the case here nor will it ever be hopefully. You know
what brought the situation to come about. And you also need to
recognize, in your own mind, where that came from.

After examining that and reading my post you still feel that way,
then you have a decision to make.

I hope you make the correct one.

Best regards,

cdunde

> >As much as I dislike the idea of loosing Alexander and cybox


> What attitude are you talking about, please ? I do not understand
> anything what you say

If you do not understand what I said then you certainly do not
possess the capacity of being afforded the posision of project
administrator.

> >My intensions where to wait until Saturday, since that is the CVS
> >file commitment cut off date, to see if they would come to their
> >senses and do the right thing. But after viewing the posting to
the
> >NEWS.txt file and its time frame, there is more than enough in
their
> >actions to display that they are both a threat to the project and
its
> >members.
> >
> >
> >
> What threat ?  I think you are exaggerating this very much.

I let the facts speak for themselves. Although you may or may not
posses better programming capabilities than others on this team and
board does not avoid the realization that they are still very
intelligent people which can interpret those facts for what they
really display and represent.

> >Therefore, I have removed Alexander's Administrative and CVS
access
> >rights and cybox's release and CVS access rights. Committed the
> >corrected files reverting the logo back to the older version,
> >reversed Alexander's last file that breaks the editors views on
poly
> >face drags and corrected the NEWS.txt file.
> >
> >
> Let me recapitulate what happened: We obviously had a different
opinion
> about the use
> of the logo,

Perhaps in your eyes, and if that was the case then it was a
misinterpretation on your part, of the competition posting, as to
specificly what the logo was to be used for. As it states quite
clearly in the title line "New QuArK 6.5 Logo Competition", just
exactly which part of that do you not understand? And even when I and
one other brought this to your attention, you still failed and
refused to take any proper action to rectify the matter.

> and there is a bug in a file i committed  These are both -
> as everyone clearly
> can see, issues that can be sorted out in 10 minutes each.

Well, for once you where able to get three things correct, and all in
a row. There may be hope for you after all.

1) A bug that obiouly shows that you did not test your code for even
the most basic of functions. That of which is dragging the side of a
face without obliderating every view of the editor making the program
entirly worthless and unusable, that's all. And it was just about to
be released in that kind of condition. I highly recommend that you
start testing your work with other functions in the project to ensure
you are not interfering or distroying them all togeather before you
commit them.

2) and 3) Yes, everyone could and can see that it would have only
taken 10 minutes each to make those corrections. Yet, even after I
had pointed that out to you and specifically gave you detail to
assist, you refused to do anything about the first, saying it would
be too complicated and did nothing at all about the second. When did
it go from being to complicated to just a simple 10 minute fix? Two
more facts that display your total disregard, stubbornness and threat
towards the entire project just to try and prove some worthless point
of your own.

> And you - god
> like administrator
> - come along and want to kick us off the QuArK project for that ?
>
> I think the QuArK project has a serious problem, but a totally
different
> one. It is a problem
> about an administrator that happily kicks out project members that
have
> done and still would
> do contribute their valuable time to an open source project instead
of
> getting a life.

My, you are arrogant arn't you.
I can see that your attitude has not changed one bit by inserting sly
immature innuendos. And you expect people to believe that you are a
true team member and participant worthy of being a project
administrator? I highly recommend that you take a class in "People
Skills" for your own good and the good of others.

>
> Cdunde, the way you are acting on the quark project shows that you
> should try to be more
> willing to work in a team yourself!  What do you thing how i felt
when i
> read that mail about
> being kicked of quark for reasons i totally not understand.

Again you do not understand. That seems to be your favorite out of
every situation. Why not try something new for once? You may just
find that you will be able to get along and a lot further with others
that way.


  I'd say you
> should have thought
> twice before changing access the privileges of project members

I thought far more than just twice about all this and I have had many
discussions about this whole thing with other team members before
coming to that conclusion. Go back and re-read the postings again.
And rather then trying to insert your own interpolations, by reading
between the lines as you state in the posting after this one, read
what is written in the lines. If you do not understand what is there
then I recommend that you buy a dictionary and see if you can read
what is on those lines. While you are there look up the definition
for "Administrator".

It was your attitude and actions that forced me to exercise my
options and responsibilities as a project administrator and only
after due consideration and communications with others involved
and\or effected by them.

You have absolutely no conception of what kind of possession being a
project administrator puts a person into, do you? When situations
like this arise, at some point in time there is going to have to be
one individual that steps up and takes that final action for the
others to protect their rights and the project.

You keep trying to convince others that I haphazardly did this all on
my own on some sick, power crazed or vindictive whim. You could not
be any more wrong or further from the truth. People recognize that.
Again, their not blind or ignorant like you are trying to make them
about to be. The more you keep trying, the more ridicules and self
centered you become in their eyes.

Sure, you're upset, you're angry. You got your tail feathers clipped
real good. But you deserved it by your own actions and attitude. May
be you're over worked, stressed out with other things in your life.
We don't know the answer to that question, only you do or you may not
even be aware of it yourself. But it took you over and turned you
into somebody I don't think you really want to be like.

So step back, take a couple of deep breaths and use some time to
yourself to reevaluate it all. Then if you honestly believe within
that you should leave this project, then leave. If you see things for
how they really are and the way they went. If you can change that and
once again become a team member as we all know how it should be and
agree to and you still want to say, then stay. You have one of two
decisions, there is no other way to go, and that decision is going to
have to be made by you and you alone at this time.

This isn't just about you, me or our projects. It's about everybody.
Sure QuArK is open source, freeware, for making games and about
having fun. But when something like this happens it can become cruel
and ugly as well. That's when it reverts back to those real life
situations that we use QuArk to get away from. Why do you think all
of us and those before have been involved, dedicating their time?
Experience? Sure, but more than that it is our release, our
enjoyment, our way of getting away from all that real life pressure
and ugliness that we detest so much, no matter what age. But
sometimes too, it carries on, gets inside us, eats at you till
something like this happens.

If someone was getting out of control and starting to push others
around, including you, by their actions or lack of, wouldn't you want
someone that to step up and take that situation on. Or just sit
around and let it continue, hoping it just goes away or thinking
that "Aw, it's not that big of a deal"? But it won't, it just feeds
it and gives it acceptance by doing nothing at all. It'll be back,
bigger and worse than it was before. To the point that the whole
project and enjoyment for others is completely destroyed or gone all
together. Then good people will leave with it.

You might be thinking to yourself as you read this, "Oh great!
Another piece of XXXX!". I wouldn't be surprised, that's normal right
now. But try doing what I suggested about taking some time. then come
back and read some of this stuff again and what lead up to it. It may
be hard and you may need to do it a couple of times because you might
start felling that defensive rage building up again. In fact, prepare
yourself for it, and hopefully, you will realize when it starts to
happen. Then move away from it again, right then and there! Take some
more time to calm down, reflect, then you will be starting to take
control of what ever it is that is bothering you so much as to get
you there in the first place. then change that, what ever it is.

Yup, you could be reading something else between the lines there,
couldn't you? But would you really want to go that way? Because you
know it would come right back at you sooner or latter and a whole lot
harder. If not in this project, eventually somewhere else down the
road in a whole other situation.

I could answer the rest of this, substantiate and document it. You
know that and so do a lot of others. The bulk of it is already out
there. The same goes for the posting I have already seen that follows
this one. But what would that accomplish? Feed the rage, that's all.
So I am ending it here.

Like I said, if you decide to stay, stay. If you decide to leave,
then leave. But if you figure you will stay and try to get back at me
or anyone else, do yourself a favor and think again. Because the
hammer will fall sooner or latter, if not by me, then by someone else.

At this time, I am leaving the permissions settings stay the way they
are for both you and cybox. Please inform him as such. After this
next release has been made I am willing to put the both of you back
to CVS access and cybox back to releases. But I will not reinstate
you as a project administrator at this time and I hope others will
agree and abide by this.

Show us that you are truly back as Alexander, the one we can trust,
work with, grow with. Then it can be considered by one and all. But
that is going to take some time, maybe a fair amount of time. Because
once the trust is broken and the respect is lost, they are hard
things to get back. Never take them so lightly or expect that they
can be demanded from others. You earn those things and they are just
two of the most important things you can have from people in your
life. Guard them well.

cdunde

Hello,

c> I wish to apologize to the other team members and viewers of this
c> board.

c> However, a serious situation has arisen that effects everyone of us,
c> the users of QuArK and the project itself that should be availed to
c> all concerned.

c> This involves Alexander, cybox, myself and others.

c> As much as I dislike the idea of loosing Alexander and cybox I see by
c> their actions a total disregard towards the members, users and the
c> QuArK project as well. I had hoped that they would recognize this
c> fact and would change their attitudes, but apparently that is not the
c> case. I also felt all along, and still do, that cybox is caught in
c> the middle of a very uncomfortable situation here since, from what I
c> understand, he works with Alexander.

c> The usage of any new Logo was specifically agreed upon by other
c> members and posted to be used for version 6.5. After I had brought
c> this to their attention on the quark-python board (Thu Aug 11, 2005
c> 11:16 pm )
c> http://groups.yahoo.com/group/quark-python/message/6934
c>
c> cybox made an entry to the NEW.txt file ( Fri Aug 12 12:33:42 2005
c> UTC (14 hours ago) by cbxpm ) of the new Logo being used for 6.4.1
c> alpha 4.

c> I have sent a communication to Sourceforce support on the general
c> situation, asking for their input and /or guidance on membership
c> conduct and procedure. Although I would expect that they will not
c> want to get involved in it.

c> I have already created new files to reverse the use of the new logo
c> with the proper 6.4.1 alpha 4 release date. As I thought and advised
c> them in detail, it only took about ten minutes and only involves
c> three files, which Alexander tried to convince me that "After some
c> discussion we found it to be too complicated to roll back". Since
c> they discussed it, then they where both aware of the fact that this
c> was not the case.

c> My intensions where to wait until Saturday, since that is the CVS
c> file commitment cut off date, to see if they would come to their
c> senses and do the right thing. But after viewing the posting to the
c> NEWS.txt file and its time frame, there is more than enough in their
c> actions to display that they are both a threat to the project and its
c> members.

c> Therefore, I have removed Alexander's Administrative and CVS access
c> rights and cybox's release and CVS access rights. Committed the
c> corrected files reverting the logo back to the older version,
c> reversed Alexander's last file that breaks the editors views on poly
c> face drags and corrected the NEWS.txt file.

c> Please try to test your files with the latest versions in the CVS and
c> continue to commit them for this up coming release. The cutoff will
c> remain midnight GMT, Saturday, Aug. 12.

c> Thank you,
c> cdunde

I am just wondering what's going on now.

Let me re-post parts of a previous e-mail from last week.

>> I will create the tag on Sunday, and release 6.4 Alpha 4 on Monday,
>> cu,
>>
>> Cybox
>
>That sounds fine, and I will check the updated CVS files needed for
>TG, make the necessary changes and commit all of its files right
>after that for the 6.5 release on Sept. 1, 2005.
>
>Thank you,
>cdunde

Concerning the logo, I made the decision to include the logo even within
our Alpha4 release (as a preview), and I thought you'd agree with that.

All I did after that was to re-edit the NEWS.txt to add that change
(which was already made days before) shortly before the release.

So far to clarify things.

And now I am not able to create the release because someone has
removed my rights to commit files ?

I'm sure this isn't the right way to communicate at all.
(I do not even see a real reason within your e-mail).

I am working on this project to learn things, to communicate with other people,
but I am not willing to continue my work under these conditions.

Please think about your decision, otherwise I must leave the project,
I really don't want to stay here with a knife in my back all the time :)

cu,

Cybox

On Sunday 14 Aug 2005 18:09, Alexander wrote:

> Hi chris,
>
> Do you develop using windows ? i have problems with the path seperators
> using mingw-win32.

Unfortunately not, I don't currently have a working windows setup, I should
probably set one up at some point. Can you describe the problem? I might
still be able to help. I would like to get this compiling properly on both
platforms if possible.

On Sunday 14 Aug 2005 17:42, you wrote:
> Hi Chris,
> thanks for the instructions.
>
> Id like try to start with qt4, is there a way how  i access your qt4 port ?

I changed over to QT4 and committed the necessary changes to cvs last night.
Some of the #include statements are using old (QT3) style  includes, but that
shouldn't cause a problem. The current checkout should just work with QT4
(and no longer with QT3)
Chris

Chris Cook wrote:

>Hi,
>Sorry about that, should have made a note somewhere.
>
>You need (currently) qt3.x, qmake (included with qt), Python 2.4 (any 2.x
>version should work, but you need to change a couple of lines in
>qtquarkplusplus.pro so it finds it), plus the usual c++ tools (make/gmake,
>g++, std libs and headers etc). For windows you need MinGW.
>
>move into the directory with qtquarkplusplus.pro in it and run 'qmake'
>then 'gmake'
>make a cup of tea.
>if all is successful the program should be built in the current directory
>
>It should compile with qt4 using the compatibility library and the conversion
>tool. I'm currently working on getting it to compile as a native QT4
>application as it has a cleaner api especially for menus/toolbars.
>
>
>

Hi chris,

Do you develop using windows ? i have problems with the path seperators
using mingw-win32.

--
best regards
  alex

May i cite you ?

on Aug. 11th you wrote  in this forum

>As far as delaying 6.5 alpha, I think we need a time frame.
>6.4.1 alpha 4 next week would be fine, then 6.5.1 alpha 1 with TG on
>Sept. 1, 2005 should be ample time to complete any needed testing.

>We can also leave the Logo contest open for that period incase
>someone else wants to submit one.

So please stop talking about unawareness - either a competition is over
or it is not. Obviously it was not and still ist not - otherwise someone
might have posted this to quark-python to inform the developers, right ?

>If you and Alexander were unaware of the competition, as I believe you
>stated once, then I suggest at least one of you should check things out a
>little better before going ahead and taking it upon your selves to try and
>
>
There was no other posting to quark-python about the state of the logo
contest, and quark-python is
still the official developer forum of quark.

>When I saw the entry and posting date to the NEWS.txt file about using the
>new logo for the 6.4.1 alpha 4 release right after I had notified you both,
>in detail, about my awareness of the simplicity to make the logo file
>reversal, it became, as I stated on the board, extremely apparent that
>anything that anybody did or said was not going to detour you or Alexander
>from doing as you two saw fit! The whole process was arrogant, deceitful and
>down right despicable. If either one of you worked for me, your feet
>wouldn't hit the floor until you where out the back door!
>
>
>
Could you please calm down and stop this ranting ? It is just unbearable.

Maybe you felt like that. If you were a real boss in an organization you
would have learned to control your
feelings, count to 10, calm down and start thinking. Are you a position
to fire real people from a real
company ? sad enough. Unfortunately you are also in the position to lay
havoc on quarks project members
as you like. Even more sad.

>The QuArK project, and every other project with Sourceforge, is built on
>"TRUST" and member participation as a "TEAM". No one or two people have the
>right to circumvent the desires and decisions of the team no matter how long
>they have been on the project or how much they have contributed. When that
>trust has been violated and abused, action needs to be taken! I have done it
>all my life in my corporate working career and my own business, which I have
>operated successfully for over 25 years based on honesty and trust, and I
>will do it here for the protection and betterment of the team, this project
>and its users.
>
>
>
Very nice speech. Are you talking about yourself violating the trust of
the other project members ?

Lets read between the lines of your speech.  The real problem is that
TEAM and TRUST are only
applicable as long you lead the TEAM. You dislike to have your  work
criticised.

I have criticised your Terrain Generator work and i tried to be fair
because you are a python
beginner. But i believe that you could not handle this. (Dont think i am
going to step back from
my comments to the TG - its design is broken and does not fit into the
overall design of QuArK).

I think you want to force the QuArK project exactly in the direction you
want it to go to - and kick
anyones ass that doesnt agree to that. Maybe that is the way it works
where you work - its not
the way it works in an open source project.

Please go back to your "own Business" where you can kick peoples asses
out of your back door
because it is your own. Your business rules dont apply to open source
projects. Maybe you'll
have to learn this the hard way. Maybe you have to trash the QuArK
project to learn it - time
will tell.

>That's my excuse, now what's yours and Alexander's?
>
>
>
I dont need an "excuse", and i am definitely not going to continue on
this sf project
as long you dont apologise to your false accusations.

>If you wish to have this posted to the public board and continue the
>discussion there, I will be happy to oblige either one of you. But be
>forewarned, I think the both of you have brought enough shame, distrust and
>embarrassment to your selves already and damaged this project as well.
>
>
I'd like to discuss this in the public, so anyone can judge himself
Anyway, you started this discussion in the public
and thus it will end in the public.

>I do apologize for my lashing out at you so harshly here, but this is also
>
>
Then just dont do it

>directed to Alexander as well because I believe he has been the driving
>
>
Then direct it to me

--
best regards
  alex

cdunde wrote:

>I wish to apologize to the other team members and viewers of this
>board.
>
>However, a serious situation has arisen that effects everyone of us,
>the users of QuArK and the project itself that should be availed to
>all concerned.
>
>This involves Alexander, cybox, myself and others.
>
>As much as I dislike the idea of loosing Alexander and cybox I see by
>their actions a total disregard towards the members, users and the
>QuArK project as well. I had hoped that they would recognize this
>fact and would change their attitudes, but apparently that is not the
>case. I also felt all along, and still do, that cybox is caught in
>the middle of a very uncomfortable situation here since, from what I
>understand, he works with Alexander.
>
>
>
What attitude are you talking about, please ? I do not understand
anything what you say

>My intensions where to wait until Saturday, since that is the CVS
>file commitment cut off date, to see if they would come to their
>senses and do the right thing. But after viewing the posting to the
>NEWS.txt file and its time frame, there is more than enough in their
>actions to display that they are both a threat to the project and its
>members.
>
>
>
What threat ?  I think you are exaggerating this very much.

>Therefore, I have removed Alexander's Administrative and CVS access
>rights and cybox's release and CVS access rights. Committed the
>corrected files reverting the logo back to the older version,
>reversed Alexander's last file that breaks the editors views on poly
>face drags and corrected the NEWS.txt file.
>
>
Let me recapitulate what happened: We obviously had a different opinion
about the use
of the logo, and there is a bug in a file i committed  These are both -
as everyone clearly
can see, issues that can be sorted out in 10 minutes each. And you - god
like administrator
- come along and want to kick us off the QuArK project for that ?

I think the QuArK project has a serious problem, but a totally different
one. It is a problem
about an administrator that happily kicks out project members that have
done and still would
do contribute their valuable time to an open source project instead of
getting a life.

Cdunde, the way you are acting on the quark project shows that you
should try to be more
willing to work in a team yourself!  What do you thing how i felt when i
read that mail about
being kicked of quark for reasons i totally not understand . I'd say you
should have thought
twice before changing access the privileges of project members - at
least you should contact
them by e-mail and try to solve issues - that is the job of a project
admin - to calm things down,
not to heat things up. I did not get any personal e-mail from you on
saturday or today.

If you feel  really concerned about QuArK, there would have been other
means to stop
bad things from happening.

If you always lock want to lock out a project member when they commit a
file that you dont like,
you will end up alone. Not that you would be able to continue the QuArK
alone - this
can be done only done by team.

I'd also say you should not be an sf project administrator when you
remove peoples access
privileges just because things happen that you dislike personally. See,
we're talking about a
technical issue here - not that cybox or me have behaved in a way that
hurts the QuArK project.

It  is just that we have different opinon about when to release and some
design issues of your
TG - and i accuse you not to be willing to discuss them. Some weeks
before, you were
about to leave the project because you were frustrated with your work
Now you are frustrated
again - you kick us out of the project ?

For myself i must now start to think wether i want to continue
contributing to QuArK at all.
Adding HL2 support had cost much of my time, but i enjoyed it.

But i am not going to spend any more minute, if i expose myself to see
my work
wasted just because someone with administrator privileges and a bad mood
kicks me out
for no or badly constructed reasons.

bye.

--
best regards
  alex

In light of the recent situation of the up coming release, another
element has arisen or re-arisen. That of the new TG for QuArK.

It was previously agreed upon, on July 21, that a final 6.4.1 alpha 4
release would be made in a relatively short period of time then the
6.5 with TG as soon as possible after that. This is what inspired the
idea of having a new logo, and its competition, as well for 6.5.

Now that the time frame has been set for Monday Aug., 15 for 6.4.1
alpha 4 and 6.5 with the logo and TG set for Sept. 1, also agreed
upon, it has become obvious that come Sept. 1 there would be nothing
else to go along with TG to warrant its release at all and would only
add one more additional set of large files to the SourceForce release
site. Therefore that release would most likely once again be
postponed for another couple of months and the TG along with it.

The whole idea was to give an impact effect to QuArK, the 6.5 new
logo and the TG, while keeping its completion under wraps, which has
been a bit undermined now.

The idea of alpha 4 being a final "test" release really carries no
merit if these dates where agreed upon and the same files would be in
6.5 two weeks later as well anyway.

Since neither one was being presented as a "stable release" and QuArK
still had major problems, including the 3D textured views, with the
so called 6.3.0 final stable release the idea of not combining the
current alpha 4 items and TG really carries no merit either and only
causes unnecessary additional delay to a major addition of the QuArK
tools available for our users.

Although it may not cover all games, mods and engines that QuArK
currently supports, it will most certainly cover any that can handle
the use of polyhedrons, which amounts to about 90 percent of them or
better. It too will need to be improved and expanded upon no
different than that of the recent Doom 3 and Half-Life 2 additions to
QuArK.

The big difference, that does carry merit, is that of a clean version
introduction, updated appearance and major application addition thus
creating a far more marketing impact for all three items. Let one
feed off of another to increase the desire and demand for the over
all project.

Therefore, I personally recommend that all of the current 6.4 and 6.5
items be combined and released as a 6.5...alpha or what ever
distinction is agreed upon by a majority number of the development
team, past and present.

In light of this matter, I am extending the commitment of new files
deadline until Wednesday April 17th, midnight GMT with the next
release to be made on Friday April 19th so that ample time is allowed
for team input, discussion and voting which will also terminate on
that same deadline to facilitate the release preparation.

Please remember to update and commit the NEWS.txt file of your
changes and additions for distribution information and
acknowledgement.

Also, please be sure to compare and handle your files accordingly
with the latest versions already committed to the CVS archives.

Thank you one and all,

cdunde

Hello,

R> Have you considered trying Eclipse instead of WinCVS?

R> The download is rather bigger, but the functionality and feature set
R> (using Eclipse to access a CVS repository) is sooo much better.

R> Rowdy

I had a look at Eclipse right after your advice :)
It's quite big, and I don't think I will ever use other parts of it.

But who knows, maybe later.

cu,

Cybox

I wish to apologize to the other team members and viewers of this
board.

However, a serious situation has arisen that effects everyone of us,
the users of QuArK and the project itself that should be availed to
all concerned.

This involves Alexander, cybox, myself and others.

As much as I dislike the idea of loosing Alexander and cybox I see by
their actions a total disregard towards the members, users and the
QuArK project as well. I had hoped that they would recognize this
fact and would change their attitudes, but apparently that is not the
case. I also felt all along, and still do, that cybox is caught in
the middle of a very uncomfortable situation here since, from what I
understand, he works with Alexander.

The usage of any new Logo was specifically agreed upon by other
members and posted to be used for version 6.5. After I had brought
this to their attention on the quark-python board (Thu Aug 11, 2005
11:16 pm )
http://groups.yahoo.com/group/quark-python/message/6934

cybox made an entry to the NEW.txt file ( Fri Aug 12 12:33:42 2005
UTC (14 hours ago) by cbxpm ) of the new Logo being used for 6.4.1
alpha 4.

I have sent a communication to Sourceforce support on the general
situation, asking for their input and /or guidance on membership
conduct and procedure. Although I would expect that they will not
want to get involved in it.

I have already created new files to reverse the use of the new logo
with the proper 6.4.1 alpha 4 release date. As I thought and advised
them in detail, it only took about ten minutes and only involves
three files, which Alexander tried to convince me that "After some
discussion we found it to be too complicated to roll back". Since
they discussed it, then they where both aware of the fact that this
was not the case.

My intensions where to wait until Saturday, since that is the CVS
file commitment cut off date, to see if they would come to their
senses and do the right thing. But after viewing the posting to the
NEWS.txt file and its time frame, there is more than enough in their
actions to display that they are both a threat to the project and its
members.

Therefore, I have removed Alexander's Administrative and CVS access
rights and cybox's release and CVS access rights. Committed the
corrected files reverting the logo back to the older version,
reversed Alexander's last file that breaks the editors views on poly
face drags and corrected the NEWS.txt file.

Please try to test your files with the latest versions in the CVS and
continue to commit them for this up coming release. The cutoff will
remain midnight GMT, Saturday, Aug. 12.

Thank you,

cdunde

--- In quark-python@yahoogroups.com, Alexander <alex_claudi@g...> wrote:
> Hi cdunde, could you contact decker 'bout that ? I also dont know
what
> was the
> real reason for the "fix" .
>
> Maybe it should be tested if other specific modifying duplicators
work
> with / without the fix ?
>

I doubt that Decker would recall the basses of his entry that far back
and since he has had no real involvement for some time he would most
likely have no knowledge of the changes to date that might have
effected his entry.

However, because this curry originated as a HL2 posting and that is
your project feel free to contact him if you wish.

Other wise I have made the reversal and committed the file for the up
coming release as a service to the users. If errors should occur it
would be best to handle them at that time to help track down the
current file(s) involved.

Regards,

cdunde

The file that is causing this problem is the last version 1.42 of
quarkpy\mapentities.py by Alexander. Please reverse or correct your
file and retest with all of the latest CVS files prior to
recommitting.

Thank you,

cdunde

--- In quark-python@yahoogroups.com, "cdunde" <cdunde1@c...> wrote:
> I just did a complete new checkout of the Source, runtime and
Infobase
> files from the CVS HEAD.
>
> After making a new build and using only the current files I am
getting
> gray screen in all of the editor views and a text showing "Unknown
> attribute" when I use the standard selector (because nothing is in
> there for TG) and try to drag a poly face.
>
> I have only committed two files which I have used the previous
copies
> to replace them and do not seem to be the cause because the problem
> still exist.
>
> I also used only the same QuArK.exe file in my previous most
current
> folder (which I updated all the files for not to long ago) and it
ran
> fine there, that's all I can tell you.
>
> So somebody might want to do the same and check that out before any
> more files are committed or the 6.4.1 alpha 4 release is made.
>
> cdunde

Hi,
Sorry about that, should have made a note somewhere.

You need (currently) qt3.x, qmake (included with qt), Python 2.4 (any 2.x
version should work, but you need to change a couple of lines in
qtquarkplusplus.pro so it finds it), plus the usual c++ tools (make/gmake,
g++, std libs and headers etc). For windows you need MinGW.

move into the directory with qtquarkplusplus.pro in it and run 'qmake'
then 'gmake'
make a cup of tea.
if all is successful the program should be built in the current directory

It should compile with qt4 using the compatibility library and the conversion
tool. I'm currently working on getting it to compile as a native QT4
application as it has a cleaner api especially for menus/toolbars.

Chris

On Friday 12 Aug 2005 00:38, Alexander wrote:
> Chris, could you point out how to compile ? which tools are needed ?
>
> Chris Cook wrote:
> >Hi all,
> >
> >Following the release of QT 4 with a better license for windows, I have
> > been attempting to port the CVS version of QuArK to QT.
> >
> >I have now made some progress in the port, and would like to add it as a
> > new module in the QuarkPlusPlus CVS. Are there any objections?
> >
> >So far I have had the splash screen working (nothing to shout about, I
> > know, but I thought the beginning was as good a place as any to start
> > from), The python initialisation code has been started (but crashes in a
> > python function), and some of the QObject and QkForm derived classes have
> > been stubbed out.
> >
> >In short I could do with a hand if anyone is interested. Some of the key
> >sub-projects are :
> >* Documenting classes and functions (I think this is key for future
> >maintenance)
> >* Figuring out what various functions and classes are meant to do.
> >* Fixing and finishing Python integration.
> >* converting windows messageing stuff to QT signals/slots
> >* Doing something better with file associations (I think this is for the
> >future)
> >* Finishing QObject class hierarchy
> >* Getting it all to work with QT4 (I only have QT3 at the moment)
> >
> >I welcome any comments.
> >
> >Thanks,
> >Chris
> >
> >
> >
> >--
> >Yahoo! Groups Links

It does not seem that is would too complicated since the only files I
see that where changed (by cybox for a preview by others and he said
he could of course change them back in his notice) was the
prog\About.dfm (1.9), prog\About.pas (v1.16) and the
icones\icones.res (v1.4).

The icones\QUARKLOGO.bmp (v1.3) was also change to the newest image
but is not really used by the building of the program as it is
already in the icones.res file above. I know because I tried the
other two submitted logos to see how they would look for myself.

And of course all of these files have their previous copies in the
CVS which would only need to be recommitted as new copies and then
reversed back to the current copies the same way.

So you are really only talking about recommitting 3 files and doing
it back again after the build is made, unless I am missing something
here. If so please clarify for me.

Also, I feel this discussion, thus far, should be posted to the quark-
python board because what that is doing is terminating the
competition as well by implied acceptance with the release and
circumventing all the coordinated efforts by everyone else without
proper notification and confirmation.

Plus, being an open source program controlled by the team and not any
one person, the avenue of procedure should be adequately addressed
and followed here.

Thank you,

cdunde

(----- Original Message -----
From: "Alexander"
To: "cdunde"
Sent: Thursday, August 11, 2005 4:47 PM
Subject: Re: Question

> After some discussion we found it to be too complicated to roll
back the
> changes in
> order to have the old image in the 6.4



----- Original Message -----
From: "cdunde"
To: "Alexander"

Sent: Thursday, August 11, 2005 3:08 PM
Subject: Re: Question

Well that is a bit confusing. Are you saying it can be tagged to use
the old
logo for the up coming final 6.4 release and then pick up the new
logo in
6.5?

Is so fine, if not, no I would like to see the new logo on 6.5 only.

cdunde



----- Original Message -----
From: "Alexander"
To: "cdunde"
Sent: Thursday, August 11, 2005 2:53 PM
Subject: Re: Question

> My opinion to that point is :
>
> lets have a 6.4 without new logo and TG next week
> and after that  going for 6.5 (with TG and new logo)
>
> But : The logo is already in cvs and looks good - so lets just
leave it
> as it is for 6.4
> I agreed this with cybox.



----- Original Message -----
From: cdunde
To: Alexander ; cybox
Sent: Wednesday, August 10, 2005 7:22 PM
Subject: Question


Hello Alex and cybox;

I wanted to ask you a question. Is the reason you want to hold off on
6.5 because of H-L 2, the Logo change or the TG? I would just like to
get a clear understanding as to what the bases is.

Thank you,

cdunde

I just did a complete new checkout of the Source, runtime and Infobase
files from the CVS HEAD.

After making a new build and using only the current files I am getting
gray screen in all of the editor views and a text showing "Unknown
attribute" when I use the standard selector (because nothing is in
there for TG) and try to drag a poly face.

I have only committed two files which I have used the previous copies
to replace them and do not seem to be the cause because the problem
still exist.

I also used only the same QuArK.exe file in my previous most current
folder (which I updated all the files for not to long ago) and it ran
fine there, that's all I can tell you.

So somebody might want to do the same and check that out before any
more files are committed or the 6.4.1 alpha 4 release is made.

cdunde

Hi cdunde, could you contact decker 'bout that ? I also dont know what
was the
real reason for the "fix" .

Maybe it should be tested if other specific modifying duplicators work
with / without the fix ?


cdunde wrote:

>Ok, found the "real" cause of the problem.
>So first of all, my sincere apologies to the gentleman that did the
>python dll conversion.
>
>The cause was due to the last change to the mapduplicator.py file
>which commented out the inclusion of "e:" for entities. And since the
>user had applied an entity, it therefore would not work in that case.
>
>The comment in the change file says this:
>
>    # Decker: Finding all subitems of type ":d", also automatically
>finds subitems of type ":e"
>       #         This is a "bug" in the QuArK.EXE, caused by having
>the Duplicator-class inherit from
>       #         the Entity-class. Not easy to fix in the QuArK.EXE,
>so the solution here is to not
>       #         search for ":e" types, but have them found when
>searching for ":d" types.
>       return item.findallsubitems("",":b")+item.findallsubitems
>("",":d")  #+item.findallsubitems("",":e")
>
>Taking out the comment # in the last line of code causes it to work
>with entities again.
>
>So the question is, do we reverse this change or leave it as it is?
>
>I do not know if the problem Decker spoke about was finally fixed
>which caused this to break or not.
>
>Thank you,
>
>cdunde
>
>--- In quark-python@yahoogroups.com, "cdunde" <cdunde1@c...> wrote:
>
>
>>Apparently this problem has existed for some time gang (Dec. 18,
>>
>>
>2003
>
>
>>to be exact) and now I could use a little help to straighten it out:
>>
>>http://games.groups.yahoo.com/group/quark/message/16748
>>
>>It all stems back to the conversion from Python reliance to use of
>>the dll file and the Python "string" module in particular.
>>
>>Sorry, but as gallant as this persons effort was, I suspect it is
>>effecting just about every file involved in the conversion, as this
>>is the second one I have found that needed corrections.
>>
>>The particular file involved with this situation is the
>>quarkpy\mapduplicator.py file.
>>
>>I downloaded version 1.23, reversed all the changes only dealing
>>
>>
>with
>
>
>>the "string" conversion (because a couple of other changes had been
>>made since then), added in "include string" statement and placed
>>
>>
>the
>
>
>>Python "string" module in my latest quarkpy folder. The Duplicators
>>now function properly again.
>>
>>It would have been just as easy to have put the python.dll file in,
>>pace the "string" module in both the quarkpy and plugins folder and
>>left the rest of the files the way they where, at least for that
>>module.
>>
>>There are 11 lines that need to be corrected for the syntax errors,
>>however I do not know exactly what the correct syntax would be. So
>>
>>
>I
>
>
>>need help to figure that part out.
>>They involve the def's for find, split, strip and zfill.
>>
>>Please review the file and let me know ASAP so we can get this fix
>>
>>
>in
>
>
>>for the next release scheduled for this coming Monday with a commit
>>dead line prior to that.
>>
>>Thank you,
>>
>>cdunde
>>
>>
>
>
>
>
>
>--
>Yahoo! Groups Links
>
>
>
>
>
>
>
>
>


--
best regards
  alex

Chris, could you point out how to compile ? which tools are needed ?


Chris Cook wrote:

>Hi all,
>
>Following the release of QT 4 with a better license for windows, I have been
>attempting to port the CVS version of QuArK to QT.
>
>I have now made some progress in the port, and would like to add it as a new
>module in the QuarkPlusPlus CVS. Are there any objections?
>
>So far I have had the splash screen working (nothing to shout about, I know,
>but I thought the beginning was as good a place as any to start from), The
>python initialisation code has been started (but crashes in a python
>function), and some of the QObject and QkForm derived classes have been
>stubbed out.
>
>In short I could do with a hand if anyone is interested. Some of the key
>sub-projects are :
>* Documenting classes and functions (I think this is key for future
>maintenance)
>* Figuring out what various functions and classes are meant to do.
>* Fixing and finishing Python integration.
>* converting windows messageing stuff to QT signals/slots
>* Doing something better with file associations (I think this is for the
>future)
>* Finishing QObject class hierarchy
>* Getting it all to work with QT4 (I only have QT3 at the moment)
>
>I welcome any comments.
>
>Thanks,
>Chris
>
>
>
>--
>Yahoo! Groups Links
>
>
>
>
>
>
>
>
>
>


--
best regards
  alex

Ok, found the "real" cause of the problem.
So first of all, my sincere apologies to the gentleman that did the
python dll conversion.

The cause was due to the last change to the mapduplicator.py file
which commented out the inclusion of "e:" for entities. And since the
user had applied an entity, it therefore would not work in that case.

The comment in the change file says this:

     # Decker: Finding all subitems of type ":d", also automatically
finds subitems of type ":e"
        #         This is a "bug" in the QuArK.EXE, caused by having
the Duplicator-class inherit from
        #         the Entity-class. Not easy to fix in the QuArK.EXE,
so the solution here is to not
        #         search for ":e" types, but have them found when
searching for ":d" types.
        return item.findallsubitems("",":b")+item.findallsubitems
("",":d")  #+item.findallsubitems("",":e")

Taking out the comment # in the last line of code causes it to work
with entities again.

So the question is, do we reverse this change or leave it as it is?

I do not know if the problem Decker spoke about was finally fixed
which caused this to break or not.

Thank you,

cdunde

--- In quark-python@yahoogroups.com, "cdunde" <cdunde1@c...> wrote:
> Apparently this problem has existed for some time gang (Dec. 18,
2003
> to be exact) and now I could use a little help to straighten it out:
>
> http://games.groups.yahoo.com/group/quark/message/16748
>
> It all stems back to the conversion from Python reliance to use of
> the dll file and the Python "string" module in particular.
>
> Sorry, but as gallant as this persons effort was, I suspect it is
> effecting just about every file involved in the conversion, as this
> is the second one I have found that needed corrections.
>
> The particular file involved with this situation is the
> quarkpy\mapduplicator.py file.
>
> I downloaded version 1.23, reversed all the changes only dealing
with
> the "string" conversion (because a couple of other changes had been
> made since then), added in "include string" statement and placed
the
> Python "string" module in my latest quarkpy folder. The Duplicators
> now function properly again.
>
> It would have been just as easy to have put the python.dll file in,
> pace the "string" module in both the quarkpy and plugins folder and
> left the rest of the files the way they where, at least for that
> module.
>
> There are 11 lines that need to be corrected for the syntax errors,
> however I do not know exactly what the correct syntax would be. So
I
> need help to figure that part out.
> They involve the def's for find, split, strip and zfill.
>
> Please review the file and let me know ASAP so we can get this fix
in
> for the next release scheduled for this coming Monday with a commit
> dead line prior to that.
>
> Thank you,
>
> cdunde

Apparently this problem has existed for some time gang (Dec. 18, 2003
to be exact) and now I could use a little help to straighten it out:

http://games.groups.yahoo.com/group/quark/message/16748

It all stems back to the conversion from Python reliance to use of
the dll file and the Python "string" module in particular.

Sorry, but as gallant as this persons effort was, I suspect it is
effecting just about every file involved in the conversion, as this
is the second one I have found that needed corrections.

The particular file involved with this situation is the
quarkpy\mapduplicator.py file.

I downloaded version 1.23, reversed all the changes only dealing with
the "string" conversion (because a couple of other changes had been
made since then), added in "include string" statement and placed the
Python "string" module in my latest quarkpy folder. The Duplicators
now function properly again.

It would have been just as easy to have put the python.dll file in,
pace the "string" module in both the quarkpy and plugins folder and
left the rest of the files the way they where, at least for that
module.

There are 11 lines that need to be corrected for the syntax errors,
however I do not know exactly what the correct syntax would be. So I
need help to figure that part out.
They involve the def's for find, split, strip and zfill.

Please review the file and let me know ASAP so we can get this fix in
for the next release scheduled for this coming Monday with a commit
dead line prior to that.

Thank you,

cdunde

--- In quark-python@yahoogroups.com, cybox <cbxpm@g...> wrote:
>
> Hello,
>
> c> As far as delaying 6.5 alpha, I think we need a time frame.
> c> 6.4.1 alpha 4 next week would be fine, then 6.5.1 alpha 1 with
TG on
> c> Sept. 1, 2005 should be ample time to complete any needed
testing.
>
> c> We can also leave the Logo contest open for that period incase
> c> someone else wants to submit one.
> >
> > cdunde
>
> (...)
>
> > We should realy sett a deadline on this now, Both Cdunde , me and
> > others have worked realy hard to get this release(6.5) out now. If
> > you sugest that the new stuff is to "Experimental" lets release
this
> > one ASAP(6.4 a.4) and sett a deadline right after it.
> >
> >-Fred
>
> OK. Then please commit all necessary files until Saturday, August
13.
> I will create the tag on Sunday, and release 6.4 Alpha 4 on Monday,
15 th.
>
> cu,
>
> Cybox

That sounds fine, and I will check the updated CVS files needed for
TG, make the necessary changes and commit all of its files right
after that for the 6.5 release on Sept. 1, 2005.

Thank you,

cdunde

Hello,

c> As far as delaying 6.5 alpha, I think we need a time frame.
c> 6.4.1 alpha 4 next week would be fine, then 6.5.1 alpha 1 with TG on
c> Sept. 1, 2005 should be ample time to complete any needed testing.

c> We can also leave the Logo contest open for that period incase
c> someone else wants to submit one.
>
> cdunde

(...)

> We should realy sett a deadline on this now, Both Cdunde , me and
> others have worked realy hard to get this release(6.5) out now. If
> you sugest that the new stuff is to "Experimental" lets release this
> one ASAP(6.4 a.4) and sett a deadline right after it.
>
>-Fred

OK. Then please commit all necessary files until Saturday, August 13.
I will create the tag on Sunday, and release 6.4 Alpha 4 on Monday, 15 th.

cu,

Cybox

Sorry about the double posting. Something weird going on with it.

cdunde

--- In quark-python@yahoogroups.com, cybox <cbxpm@g...> wrote:
>
> Hello,
>
> c> We need to have all new and updated files committed by midnight
GMT
> c> this Friday, Aug. 12, 2005 for the preperation of QuArK 6.5 to
be
> c> released Tuesday, Aug. 16, 2005. This will enable the review and
> c> updating of any related files for the Terrain Generator, and its
> c> Infobase section, prior to their commitment by midnight GMT
Sunday,
> c> Aug. 14, 2005.
>
> c> I wish to request that cybox prepare and issue this release.
>
> c> The new Logo that seemed to have the best and most acceptance
was
> c> that by "Leonard "paniq" Ritter", the designer of the previous
QuArK
> c> Logo, and which has already been committed to the CVS files.
> c> Congratulations Leonard and thank you for a job well done
(again)!!!
>
> c> Although it was hoped that one more 6.4.1 alpha 4 release would
be
> c> made it would be best to roll all of those changes and
improvements
> c> into the 6.5 release, giving it that much more impact. I know a
lot
> c> of work has been done for Half-Life 2 by Alexander and cybox. We
all
> c> thank you for your continued efforts and contribution.
>
> I think it's too early to release a final right now.
>
> Many things were added, most changes are Source Engine related, and
we should
> really test all these complicated changes for a couple of weeks
longer before the
> final is ready to roll :)
>
> I had a "system meltdown" over the weekend, and as soon as
everything is up and
> running again (including Delphi and WinCVS), I would suggest to
release
> version 6.4 alpha 4 next week.
>
> cu,
>
> Cybox

If we are talking about the same thing, SF has been making a server
change over which shut down some of the projects CVS access. I had
the same problem with Eclipse server access being denied and
installed a new ssh server only to find out the real problem. It
covers this on the SF system status page.

As far as delaying 6.5 alpha, I think we need a time frame.
6.4.1 alpha 4 next week would be fine, then 6.5.1 alpha 1 with TG on
Sept. 1, 2005 should be ample time to complete any needed testing.

We can also leave the Logo contest open for that period incase
someone else wants to submit one.

cdunde

>I think it's too early to release a final right now.
Makes a lot of sense. I sent a similar email to CDunde too.


[Non-text portions of this message have been removed]

cybox wrote:
<snip>
> ... and as soon as everything is up and running again (including Delphi
  > and WinCVS) ...

Have you considered trying Eclipse instead of WinCVS?

The download is rather bigger, but the functionality and feature set
(using Eclipse to access a CVS repository) is sooo much better.

Rowdy