Mojmir's New Blackbox Build

https://github.com/x...ox/Settings.cpp around line 1050

https://github.com/x.../ConfigMenu.cpp around line 180

 

some parts of those are not in sync. that being said, my separators are black on black if i set separatorstyle to flat and grey when i set it to bevel

(i have a minimalist light gray-on-black style)

probably they also do not get rendered correctly, still, uh, it's gonna be in rc3 or rc4

Yo Ma Man! You probably going to be my best online friend for the next couple of years   Don't worry I won't put my tongue ... (yeah, I know I have terrible sense of humor)

I think I can clearly see (almost see) where the loop is but I also think you are overestimating my capabilities. I'm happy though it's the first time I'm having a look inside the sources with such a dedicated guide! I happened to notice something else, the separators don't draw correctly except under compact mode. Whenever I run my pointer down the menu the active portion mask out the separators.

This said, I like you "Anotter box" but I find the otters are too cute for this setting. What's in the right corner?

Thank for the insight.

Yo Ma Man! You probably going to be my best online friend for the next couple of years   Don't worry I won't put my tongue ... (yeah, I know I have terrible sense of humor)

I think I can clearly see (almost see) where the loop is but I also think you are overestimating my capabilities. I'm happy though it's the first time I'm having a look inside the sources with such a dedicated guide! I happened to notice something else, the separators don't draw correctly except under compact mode. Whenever I run my pointer down the menu the active portion mask out the separators.

 

This said, I like you "Anotter box" but I find the otters are too cute for this setting. What's in the right corner?

 

Thank for the insight.

that's winamp with the asciiamp skin.

i have a folder full of cute otter pictures (and (half)naked redheads). it's good to have them cycle

https://github.com/x...ox/Settings.cpp around line 1050

https://github.com/x.../ConfigMenu.cpp around line 180

 

some parts of those are not in sync

 

 

i rememeber i encountered similar problem with bbstylemaker. there is some code from bad merge so when you save your style in bbstylemaker it either saves it wrong or crashes. i know i wanted to fix but i do not remember if i really did

i finally found the issues page on the github ( https://github.com/x...450/wiki/Issues ), and i found this:

some windows (like visual studio 2012/2013) refuse to disappear most of the time when switching workspaces

i got that too, but i think it happens only to windows that runs as administrator (msvc sometimes does). just yesterday i ran cmd "as admin" et voila - the window was omnipresent on all workspace (behaving like sticky). so i run blackbox as administrator to avoid this and everything works well.

i am not at all sure about this. is it a feature or a bug? should non-admin blackbox handle admin windows as he handles the rest?

sometimes windows disappear completely when using workspaces, making the feature a russian roulette

is it similar to this?

http://blackbox4wind...from-workspace/

i finally found the issues page on the github ( https://github.com/x...450/wiki/Issues ), and i found this:

some windows (like visual studio 2012/2013) refuse to disappear most of the time when switching workspaces

i got that too, but i think it happens only to windows that runs as administrator (msvc sometimes does). just yesterday i ran cmd "as admin" et voila - the window was omnipresent on all workspace (behaving like sticky). so i run blackbox as administrator to avoid this and everything works well.

i am not at all sure about this. is it a feature or a bug? should non-admin blackbox handle admin windows as he handles the rest?

sometimes windows disappear completely when using workspaces, making the feature a russian roulette

is it similar to this?

http://blackbox4wind...from-workspace/

ahhhh yeah, that totally explains it.

it's a feature. when blackbox runs in a user context, of course it shouldn't have access to admin processes or to directly control admin handles, but probably it can still do some basic window managing operations (everything which just requires PostMessage).

and i guess it is related to the workspace problems (and also why windawesome breaks at times)

i think if we rework the way workspaces currently work, we can get around this.

instead of actually hiding the window, we could send it a minimize message and internally mark it as not-visible, so that it doesn't appear in the toolbar's task list - that being said i have no clue how workspaces are currently implemented

also i was thinking of registering an optional service which handles this stuff (if carefully designed, this would minimize the security risk of having the whole of bb running in an admin context).

when the service is on, bb delegates calls for controlling window properties and the like

when the service is off, bb tries to do it's best by itself (as it currently does)

Edit: for now we should probably include checks for whether bb has admin rights and whether it can control these windows. if it can't it should just not touch them instead of leaving them in a possibly corrupted state

that's winamp with the asciiamp skin.

i have a folder full of cute otter pictures (and (half)naked redheads). it's good to have them cycle

To be politically incorrect and with great respect for the ladies: I really like redheads...be they be naked, half naked or plain red nice collection though.

To continue on the minor issues I encountered: sometimes right clicks on plugins wouldn't work (I disable desktop right click with this line [#disable right-click blackbox.desktop.RightClick: ] in extension.rc.)

i fear for my virginity now

okay i wrote the problem to the list of known issues on the wiki

Hello!

Don't worry from my part it's merely male awkwardness to build serious friendly relationship

Concerning the builds issues: I really find this build convenient for me, I am used to switching from fork to builds, forks to forks etc. but the bbleans builds have always been the one that I most extensively use. I am always trying new softwares and sometimes trying two shell replacement elements together (e.g. sharp enviro's tray with bblean (sic)) I have a number of little issues I encounter from time to time. What do you suggest I do, doI post them here when they happen or post a list once every 5 or 6? The fact is that not all issues are this builds bugs, it may be my misuse of bb...

Hello!

Don't worry from my part it's merely male awkwardness to build serious friendly relationship

 

Concerning the builds issues: I really find this build convenient for me, I am used to switching from fork to builds, forks to forks etc. but the bbleans builds have always been the one that I most extensively use. I am always trying new softwares and sometimes trying two shell replacement elements together (e.g. sharp enviro's tray with bblean (sic)) I have a number of little issues I encounter from time to time. What do you suggest I do, doI post them here when they happen or post a list once every 5 or 6? The fact is that not all issues are this builds bugs, it may be my misuse of bb...

nah, they are probably bugs

it would be nice if you could post them either here, on the github wiki page https://github.com/x...450/wiki/Issues or both :3

and i guess either way would be alright.

for now we don't have any incredibly awesome bugtracker or other way to organize all this, but it's still managable - i mean, it's not like we don't fix a bug because we don't know it exists, we don't fix it because we are fixing one of the other 20 xD

a nice bugtracker would be nice, maybe github has some... i found this

https://github.com/b...b-issue-tracker

so maybe it is not just turned on somewhere in repo settings?

until recently i was using berlios.de as s project hosting site. it is very nice, has an issue tracker, wiki and support for wordpress. but i received a notice that they will shut down in april.

i just asked my friend and there is issue tracker on github. in between 'code' and 'pull request' he has 'issues'.

so i've written to Jonathan (xzero450) if he will kindly turn this feature on

i just asked my friend and there is issue tracker on github. in between 'code' and 'pull request' he has 'issues'.

so i've written to Jonathan (xzero450) if he will kindly turn this feature on

ahh, the luxury of github

yay, we have issue tracker

https://github.com/x...xzero450/issues

thanks Jonathan!

blackboxzero RC3

- diabol fixed the bbleanskin. now it should run like before, except with aero

- diabol fixed the new plugins from Theo

- and maybe more

- i made new installer, so there is only 1 executable (which contains all 4 builds) and the autodetection (+ user gui for confirmation) decides which one will be used. the installer is kinda new and hot, so i expect bugs (not sure how it works on XP 64) and comments about the components etc.

it's in .rar because for .exe i get error "You aren't permitted to upload this kind of file".

(not sure how it works on XP 64)

thanks for trying!

$ file install.exe install.exe: PE32 executable (GUI) Intel 80386, for MS Windows

so the installer is 32bit, that's fine.

i will look what other dependencies installer has. it's build on win7, maybe that has someting to do with it.

The installer work like a charm, haven't try to install on my pendrive yet.   I have to issues to report, I missed the first one because I usually edit the config files before I run bb. I don't have use for bbleanskin so I always wipe this from plugin rc.   1.  18022014-bbleanskin.png   5.13KB   0 downloads

2. Whenever I maximize excel and restore it back bblean bar disappear, I have to right click or press mod to have it back.

3. I don't know if it's me or else but it seems to me that start up time has increase.

Cheers for this new update, bullets are now permanent [separators still not surviving a logoff.

Thanks to M and D

@meanmechanics: You need http://www.microsoft...s.aspx?id=30679

Which leads me into:

Is there a reason that you are wanting to use the MSVC runtimes? There was a lot of backlash when builds used it "back in the day" and they had a habit of limiting which Operating Systems you could use..

I ask to try and understand where you are heading. 'sides, if you're going to build an installer that detects/installs the MSVC runtime.. Get fancy and do some real stuff in it too?

multiple points of view

* this is still development build. i build with what i use for development.

* i have a legal copy of visual studio 2012 and that's why i am using it.

* it is much easier to make the sources work in x64 with msvc than with mingw (i.e. there is more plugins with msvc)

* 2012 update 4 (i think) is the first version, that supports multitargetting, i.e. ability to compile software for win XP under the same visual studio, using only a different toolset. this is a big step from microsoft and a good one. i am impressed, really

* in theory with this new cmake build system should be able to compile with any decent compiler, i.e. vs2008, vs2010, vs2012, 2013, mingw 3+

* but i refuse using any compiler under 2010. 2008 if you put fist in my rectum, but 2005? never

* in theory we can make build for xp with different compiler than for vista+

* but xp is dead, admit it ;P microsoft already did

* msvc runtimes can be installed by the installer (one of the reasons behind it, the second is existence of multiple builds), so the users do not have to do anything

* users should be familiar with this already, every game install redistributables

* msvc redistributables are shared so you have to install them only once

we can discuss what compiler we will use at the end for the final build, but for now it is 2012

to where i am heading:

1) have a comfortable development environment for everybody

really. making an environment for creating 64b build is.. well it's not complete nightmare, but still not a dream you like to dream. you have to get mingw64, but this cannot be any mingw64, but special mingw64 with static threading libraries, otherwise you'll end up with build that has dependencies on gcc libraries. best if you build mingw64 on your own. then you have to fix the makefile subsystem, which is feasible, but requires amount of work.

at that point i said f*ck this, we are dragging blackbox in the new century. build environment should not be an arcane knowledge accessible to few brave hearts who made it through the thorny journey.

2) collect as much from blackbox as possible from all the corners of the internet.

right now the blackbox is quite scattered all around, you have pieces of 32b plugins with no sources lying everywhere. get the lost sheep back, and make them 64bit while at it.

3) have a stable build of blackbox on xp, vista, win7, win8 and 32 / 64 editions

after all of these RC candidates, that one build will be the base and the one we will give to users.

these i am doing here should be considered as betas. i hope everybody accepts this.

and then... break this shit with new stuff (wink to diabol)

during x64 porting i've been all around the sources and honestly bb feels like garden that nobody cared for a decade or more. so maybe a bit of careful pruning and it could look like a garden again

 

Get fancy and do some real stuff in it too?

what do you mean?

btw: we'd need probably some fancy stuff from you, dear Jonathan. Pete is persistent with split diagonals and mirrored horizonts what we will do about it?