search for: new_ui

Displaying 3 results from an estimated 3 matches for "new_ui".

Did you mean: new_oi
2008 Jul 14
0
Problem with vampire: bloodlines
...uot;Fragment shader(s) linked, vertex shader(s) linked. \n Validation failed - samplers of different types are bound to the same texture image unit. \n" Reference Count for Material ___error (132) != 0 Reference Count for Material debug/debugmrmnormals (1) != 0 Reference Count for Material hud/new_ui/firstbarframe (1) != 0 Reference Count for Material hud/new_ui/firstbarlace (1) != 0 Reference Count for Material hud/new_ui/firstbarblackfill (1) != 0 Reference Count for Material hud/new_ui/firstbarcolorfillaqua (1) != 0 Reference Count for Material hud/new_ui/firstbarcolorfillgray (1) != 0 Refer...
2012 Jan 07
3
Mixed-commit problem solved
...t-conversion.tar.gz for your inspection. Remaining issues: # 1. Have yet to find a clean merge point for any branch. # 2. set-eol-style operations get lost; see tags windows-set-eol, reset-eol. # 3. Should the first Eaton_SDK commit after the deleteall have a link # back to trunk? # 4. Is the new_UIs-root tag still useful? It doesn't seem to point # at an actual branch. Also, some remaining zero-fileop commits on the root branch should probably be tagified. >From what you said before, point 2 may actually be a non-issue. Should I cross it off the list? -- >>esr>&gt...
2012 Jan 09
1
reposurgeon progress
...mat. I'd do that if I undertood the gitk code well enough. But it's pretty hairy, and my Tcl-fu is weak. How's yours? > Also attached is a patch to fix the help for several commands (they did not > print anything in the interactive mode). Applied, thanks. >> # 4. Is the new_UIs-root tag still useful? It doesn't seem to point >> # at an actual branch. > >ESR: In terms of content, no - not useful. OK, crossed off my list. >I think we have another case of some deleteall commits masking some other >problem. From the reposurgeon Git repository, the...