Collectible Card Game Headquarters

Doublestrike wrote:avatars...hoping some graphics guru can do some fixing.

And a graphics guru did - thanks WompWomp for a whole selection of Vanguard avatars.

FIXED (right?). Die visual artifacts, die! Some of these UI fixes are hellish, for sure.

ArsenalNut wrote:The combat pane is not getting updated as you declare attackers and blockers which makes it combat challenging.

Also fixed.

Doublestrike wrote:FIXED (right?). Die visual artifacts, die! Some of these UI fixes are hellish, for sure.

There are still visual artifacts.
When i start the deck editor and close it again, all the buttoms have disappeared until i hover over them.

I am seeing the same thing as Sloth.
Additionally, if I accidentally or unknowingly select only one or exactly 4 colors for the deck generation(which it can't handle), the "Starting New Game" progress bar is stuck on after the warning dialog disappears.

@Sloth: Is your Win7 setup 64 or 32 bit? I'm running Win7 x64 and haven't had any of these issues, so if you're using 32 bit then maybe it'll help narrow down the problem to some kind of threading issue? (If not then there's something else going on )

Jiminy Christmas. OK back to it then. I did the debugging on a 64 bit (with 1.7 JDK I think, lazy to check), that behavior is not happening. Will give it a whirl on the 32 bit in an hour or two.

Hellfish wrote:Additionally, if I accidentally or unknowingly select only one or exactly 4 colors for the deck generation(which it can't handle), the "Starting New Game" progress bar is stuck on after the warning dialog disappears.

That is an unrelated but still very legitimate bug. Well, it used to be, anyway :smash:. Thanks for an easy one.

Hmm, that behavior is not happening for me on x86 or x64 (Windows 7). Sorry, but I'll need some further clues to debug. It sounds like a validation/repaint issue on the top level.

In a separate working version, I've got a big chunk of the legacy code removed, and various performance improvements from there. Since the release is delayed anyway, I may as well commit - but I'll wait the ok from someone. (My point being, the problem may be fixed on the new stuff.)

Doublestrike wrote:

slapshot5 wrote:I just commented out this line in FPanel (around line 245 - I've got some debug code in though):

Code: Select all

g0.fillRoundRect(0, 0, pw, ph, cornerDiameter, cornerDiameter);


in drawBackgroundColor. All seems normal.

-slapshot5

Yeah, except now background colors won't be drawn (probably) But I suppose a workaround is better than nothing. Working on it today.

`
I tried this fix yesterday and it did appear to help somewhat. Although the background colors were not drawn. I could at least see the various components.

Without this fix it appears that the background color is being drawn over and on top of the various buttons and so forth. That may explain why my screen shot is missing many of the components that should have been visible.

I updated to rev 13998 and still notice lots of issues on my Mac. I use the default skin and I see the dark blue color instead of the lighter blue color that I was seeing before these graphics issues started.

Most of the components are not visible for the most part. Using Slapshot's temporary bug fix looked better overall than today's version. The color that I am seeing today looks like the background colors are not being drawn or are becoming invisible somehow.

Doublestrike wrote:In a separate working version, I've got a big chunk of the legacy code removed, and various performance improvements from there. Since the release is delayed anyway, I may as well commit - but I'll wait the ok from someone. (My point being, the problem may be fixed on the new stuff.)

`
I vote for delaying the build and release as the graphics problems at this time are fairly major.

I think that you should go ahead and commit your other work as it may help to improve the graphics issues.

OK it's up - r14000 (yikes). Will hang around here for a bit for major problems.

I updated to rev 14001 and it pretty much looks the same as it did before. I ran forge and had to click on invisible buttons to get to quest mode. If I click on one of the tabs and hover my mouse pointer over this tab and do not move the mouse pointer out of the tab I see this:

`

Chris H. wrote:I updated to rev 14001 and it pretty much looks the same as it did before. I ran forge and had to click on invisible buttons to get to quest mode. If I click on one of the tabs and hover my mouse pointer over this tab and do not move the mouse pointer out of the tab I see this:

`
Now if I move my mouse pointer out of the tab I see this:

`

You know, this reminds me of way back when with the button repainting strangeness. That was fixed just by a random line in the code that shouldn't have mattered. Maybe I'll go dig that up.

Looks like it may be a "validate" problem - could you have a go with 14005? If not, I'll try a repaint also, sometimes that helps.

Does your match UI work?

Doublestrike wrote:You know, this reminds me of way back when with the button repainting strangeness. That was fixed just by a random line in the code that shouldn't have mattered. Maybe I'll go dig that up.

Looks like it may be a "validate" problem - could you have a go with 14005? If not, I'll try a repaint also, sometimes that helps.

Does your match UI work?

`
Let me update and do a run and test ... I will get back to you in a few minutes.

Chris H. wrote:

Doublestrike wrote:You know, this reminds me of way back when with the button repainting strangeness. That was fixed just by a random line in the code that shouldn't have mattered. Maybe I'll go dig that up.

Looks like it may be a "validate" problem - could you have a go with 14005? If not, I'll try a repaint also, sometimes that helps.

Does your match UI work?

`
Let me update and do a run and test ... I will get back to you in a few minutes.

`
Updated to rev 14007 and things look the same. I checked out the match UI and it displays the same problem:

`

Doublestrike wrote:Jiminy Christmas. OK back to it then. I did the debugging on a 64 bit (with 1.7 JDK I think, lazy to check)

`
Before we get too far into other hypotheticals, would it be worth the effort to see which version of java you are using?

Several issues in recent months appear to have been caused by a few people using an early version of java 7 and there may be incompatibilities. Many of us are still at java 6 and us Mac folks have no other option at this time but java 6.