General UI support

[Chris H.]

Using today's snapshot build rev15148 I once again tried to play a constructed mode game and had the same freeze as yesterday. My processor is pegged at about 100%.

I clicked on the close box in the picture below and the pic changed back to the home screen but the processor is still pegged at 100%.

OH, and I have 2.71 GB of free memory at the time of the above freeze.

I can use forge's Quit forge.view.Main menu command and my processor usage will go back to normal.

It is strange that this only happens with the constructed mode yet I can play a quest match OK. Do not know if this is useful or not.

This might be a Mac OS only type of problem. I have not yet seen reports from anyone else stating that they are having the same problem with constructed mode.
 

[Forger]

I hope you plan to make the labels toggle-able, they waste a lot of space and most of them are worthless to keep around once you set up your layout.

[friarsol]

I hope you plan to make the labels toggle-able, they waste a lot of space and most of them are worthless to keep around once you set up your layout.

I was thinking the same thing. Have some way to "grow the panel" once you are done setting up your config so they don't take up so much space. Wherever you put the "Reset panels" could also have a "show/hide panel tabs" to regain that space.

[friarsol]

I hope you plan to make the labels toggle-able, they waste a lot of space and most of them are worthless to keep around once you set up your layout.

I was thinking the same thing. Have some way to "grow the panel" once you are done setting up your config so they don't take up so much space. Wherever you put the "Reset panels" could also have a "show/hide panel tabs" to regain that space.

[slapshot5]

This is fantastic work Doublestrike. There are a couple things that are rough around the edges, but all-in-all, this is another huge step forward in our UI experience.

-slapshot5

[slapshot5]

Using today's snapshot build rev15148 I once again tried to play a constructed mode game and had the same freeze as yesterday. My processor is pegged at about 100%.

This might be a Mac OS only type of problem. I have not yet seen reports from anyone else stating that they are having the same problem with constructed mode.

Hey Chris, I'm not seeing this on my Mac. Not really sure what is going on. Does it happen if you do a fresh checkout? Perhaps it's having trouble reading a txt file or a config file or a dck file?

-slapshot5

[Chris H.]

Hey Chris, I'm not seeing this on my Mac. Not really sure what is going on. Does it happen if you do a fresh checkout? Perhaps it's having trouble reading a txt file or a config file or a dck file?

 
I was having this problem with the snapshot build and the local copy in Eclipse.

I decided to remove my prefs file from the Eclipse local copy and found that I can now start a constructed match OK without the freeze.

Let me paste in a copy of the contents of the old prefs file incase Doublestrike sees something there that is suspicious.

buggy(?) forge.preferences file contents | Open

Code: Select all

UI_USE_OLD=false
UI_RANDOM_FOIL=false
UI_LAYOUT_PARAMS=0.15,0.8034948741845296,0.7164583333333334,0.7924417520969245,0.34680335507921717,0.5854613233923578
UI_SMOOTH_LAND=false
UI_AVATARS=0,73
UI_CARD_OVERLAY=true
UI_UPLOAD_DRAFT=true
UI_SCALE_LARGER=true
UI_MAX_STACK=3
UI_STACK_OFFSET=tiny
UI_CARD_SIZE=medium
UI_BUGZ_NAME=
UI_BUGZ_PWD=
UI_ANTE=false
UI_MANABURN=false
UI_SKIN=Default
UI_PREFERRED_AVATARS_ONLY=false
SUBMENU_CURRENTMENU=CONSTRUCTED
SUBMENU_SANCTIONED=true
SUBMENU_QUEST=true
SUBMENU_SETTINGS=true
SUBMENU_UTILITIES=true
DEV_MODE_ENABLED=true
DEV_MILLING_LOSS=true
DEV_UNLIMITED_LAND=true
DECKGEN_SINGLETONS=true
DECKGEN_ARTIFACTS=false
DECKGEN_NOSMALL=false
PHASE_AI_UPKEEP=true
PHASE_AI_DRAW=true
PHASE_AI_MAIN1=true
PHASE_AI_BEGINCOMBAT=true
PHASE_AI_DECLAREATTACKERS=true
PHASE_AI_DECLAREBLOCKERS=true
PHASE_AI_FIRSTSTRIKE=true
PHASE_AI_COMBATDAMAGE=true
PHASE_AI_ENDCOMBAT=true
PHASE_AI_MAIN2=true
PHASE_AI_EOT=true
PHASE_AI_CLEANUP=true
PHASE_HUMAN_UPKEEP=true
PHASE_HUMAN_DRAW=true
PHASE_HUMAN_MAIN1=true
PHASE_HUMAN_BEGINCOMBAT=true
PHASE_HUMAN_DECLAREATTACKERS=true
PHASE_HUMAN_DECLAREBLOCKERS=true
PHASE_HUMAN_FIRSTSTRIKE=true
PHASE_HUMAN_COMBATDAMAGE=true
PHASE_HUMAN_ENDCOMBAT=true
PHASE_HUMAN_MAIN2=true
PHASE_HUMAN_EOT=true
PHASE_HUMAN_CLEANUP=true
SHORTCUT_SHOWSTACK=83
SHORTCUT_SHOWCOMBAT=67
SHORTCUT_SHOWCONSOLE=76
SHORTCUT_SHOWPLAYERS=80
SHORTCUT_SHOWDEV=68
SHORTCUT_CONCEDE=17

[Chris H.]

I was having this problem with the snapshot build and the local copy in Eclipse.

I decided to remove my prefs file from the Eclipse local copy and found that I can now start a constructed match OK without the freeze.

Let me paste in a copy of the contents of the old prefs file incase Doublestrike sees something there that is suspicious.

buggy(?) forge.preferences file contents | Open

Code: Select all

UI_USE_OLD=false
UI_RANDOM_FOIL=false
UI_LAYOUT_PARAMS=0.15,0.8034948741845296,0.7164583333333334,0.7924417520969245,0.34680335507921717,0.5854613233923578
UI_SMOOTH_LAND=false
UI_AVATARS=0,73
UI_CARD_OVERLAY=true
UI_UPLOAD_DRAFT=true
UI_SCALE_LARGER=true
UI_MAX_STACK=3
UI_STACK_OFFSET=tiny
UI_CARD_SIZE=medium
UI_BUGZ_NAME=
UI_BUGZ_PWD=
UI_ANTE=false
UI_MANABURN=false
UI_SKIN=Default
UI_PREFERRED_AVATARS_ONLY=false
SUBMENU_CURRENTMENU=CONSTRUCTED
SUBMENU_SANCTIONED=true
SUBMENU_QUEST=true
SUBMENU_SETTINGS=true
SUBMENU_UTILITIES=true
DEV_MODE_ENABLED=true
DEV_MILLING_LOSS=true
DEV_UNLIMITED_LAND=true
DECKGEN_SINGLETONS=true
DECKGEN_ARTIFACTS=false
DECKGEN_NOSMALL=false
PHASE_AI_UPKEEP=true
PHASE_AI_DRAW=true
PHASE_AI_MAIN1=true
PHASE_AI_BEGINCOMBAT=true
PHASE_AI_DECLAREATTACKERS=true
PHASE_AI_DECLAREBLOCKERS=true
PHASE_AI_FIRSTSTRIKE=true
PHASE_AI_COMBATDAMAGE=true
PHASE_AI_ENDCOMBAT=true
PHASE_AI_MAIN2=true
PHASE_AI_EOT=true
PHASE_AI_CLEANUP=true
PHASE_HUMAN_UPKEEP=true
PHASE_HUMAN_DRAW=true
PHASE_HUMAN_MAIN1=true
PHASE_HUMAN_BEGINCOMBAT=true
PHASE_HUMAN_DECLAREATTACKERS=true
PHASE_HUMAN_DECLAREBLOCKERS=true
PHASE_HUMAN_FIRSTSTRIKE=true
PHASE_HUMAN_COMBATDAMAGE=true
PHASE_HUMAN_ENDCOMBAT=true
PHASE_HUMAN_MAIN2=true
PHASE_HUMAN_EOT=true
PHASE_HUMAN_CLEANUP=true
SHORTCUT_SHOWSTACK=83
SHORTCUT_SHOWCOMBAT=67
SHORTCUT_SHOWCONSOLE=76
SHORTCUT_SHOWPLAYERS=80
SHORTCUT_SHOWDEV=68
SHORTCUT_CONCEDE=17

 
I think that I found the problem with constructed mode.

Choose "Fully random color deck" and select the checkbox for "Singleton Mode".

I can play a constructed mode random deck game OK if the "Singleton Mode" checkbox is off, and if I check this box and start a match Forge will then freeze.

[Milod]

i dont like the new ui in previous versions i had more view space and iam using 1024X768 screen res

[Doublestrike]

EDIT 2: You also have panels disappearing if you change from full screen to windowed mode so it doesn't look like a daul monitor issue.

This should be fixed...no news is good news

EDIT: It might be dual monitor issues. If you reshuffle the panels with the display stretched across two monitors then resize the window, panels disappear.

This bug is a cousin of the "EDIT 2" one, so it should be fixed too.

If you then drag panels any further it causes a crash.

This hasn't happened to me yet, a stack trace could be helpful if it comes up again.

I can play a constructed mode random deck game OK if the "Singleton Mode" checkbox is off, and if I check this box and start a match Forge will then freeze.

I can confirm this. Do you think this is a UI problem?

[Doublestrike]

...another huge step forward in our UI experience...

Thanks Slapshot, glad you like it and it's not too crash-y.

Re: huge step forward - you're right, this framework will allow great things in the deck editor (I won't even get started there) and even the home screen, where multiple cells for the game modes can be up at the same time.

[Chris H.]

I can play a constructed mode random deck game OK if the "Singleton Mode" checkbox is off, and if I check this box and start a match Forge will then freeze.

I can confirm this. Do you think this is a UI problem?

 
Not sure if it is UI or some other recent change that is causing this issue.

I quickly ran a test with the last beta v1.2.6 and did not experience the freeze with the "Singleton Mode" checkbox set to on. It looks like this problem started sometime over the last 2 weeks.

I ran the snapshot build test with and without using Eclipse. I checked Eclipse's console and saw no reports. I also ran my Mac's console app and there was no useful info generated.


I do like the new UI changes and had a lot of fun moving panels around this weekend. And thank you for the reset button. It could be useful as more people experiment with the new movable panels.

[Chris H.]

I hope you plan to make the labels toggle-able, they waste a lot of space and most of them are worthless to keep around once you set up your layout.

I was thinking the same thing. Have some way to "grow the panel" once you are done setting up your config so they don't take up so much space. Wherever you put the "Reset panels" could also have a "show/hide panel tabs" to regain that space.

 
I think that we may want to keep the tabs visible for a panel that has more than one tab, this would allow to easily select which tab was active.

[friarsol]

I think that we may want to keep the tabs visible for a panel that has more than one tab, this would allow to easily select which tab was active.

Right, I was thinking this mostly for battlefield/Hands. But Having a single tab is probably the best way to determine if the tab should be hidden.

[Sloth]

I can play a constructed mode random deck game OK if the "Singleton Mode" checkbox is off, and if I check this box and start a match Forge will then freeze.

I can confirm this. Do you think this is a UI problem?

 
Not sure if it is UI or some other recent change that is causing this issue.

I quickly ran a test with the last beta v1.2.6 and did not experience the freeze with the "Singleton Mode" checkbox set to on. It looks like this problem started sometime over the last 2 weeks.

I ran the snapshot build test with and without using Eclipse. I checked Eclipse's console and saw no reports. I also ran my Mac's console app and there was no useful info generated.

This was a simple logic bug in a "do while" loop.

Bam!

:fist pump:

Nice hit Doublestrike!