Mouse Cursors Breeze Cursors by niivu

Hi Lancelot


The Mouse cursor plugins in Win10PESE are not working on PEBakery,
because they depend on WinBuilder-specific IniWrite behavior. WinBuilder reformats the .ini file when IniWrite is used,
while PEBakery avoids that for performance reasons. This fix uses the %PEBakery% variable to detect which builder it is running on.

would it be acceptable for you to add this check/fix to your plugin ?

Code: [Select]

[Macro_Cursor_Process]
// ......
IniWrite,%MacroCursor_w%,DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY,DUMMY_Key,DUMMY_Value
TxtReplace,%MacroCursor_w%,"#$q#$x","#$x"
TxtReplace,%MacroCursor_w%,"=#$q","="

-->

Code: [Select]

[Macro_Cursor_Process]
// ......
If,%PEBakery%,Equal,True,Begin
  // Unlike Winbuilder, PEBakery does not reformat the entire file on IniWrite...
  TxtReplace,%MacroCursor_w%,"#$q#$x","#$x"
  TxtReplace,%MacroCursor_w%,"#$q   #$x","#$x"
  TxtReplace,%MacroCursor_w%,"= #$q","="
End
Else,Begin
  IniWrite,%MacroCursor_w%,DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY,DUMMY_Key,DUMMY_Value
  TxtReplace,%MacroCursor_w%,"#$q#$x","#$x"
  TxtReplace,%MacroCursor_w%,"=#$q","="
End

regards APT

ps posted on a Win10PE SE thread as not sure how often you chk PEBakery ones!

ps posted on a Win10PE SE thread as not sure how often you chk PEBakery ones!

As you may notice It is the opposite, I do not think ied206 check Win10PE SE or other topics for PEBakery, eg. there are new posts by ied206 on the PEBakery section after you open the current topic.

That is THE Reason you should open anything related to PEBakery to PEBakery section.

I agree with PEBakery decision but you should ask ied206 "another compatibility option" for such things,
 there are many plugins written that way and I am not here. see: http://theoven.org/index.php?topic=2834.msg35012#msg35012

Hello Lancelot, long time no see. 

First, let me suggest a perfect solution that will greatly help Win10PESE developers.
Let me introduce the macro IniCompactShim.
The macro should work both on WinBuilder 082 and PEBakery beta 6+.

Code: [Select]

// In Macro Library
[Variables]
IniCompactShim=Run,%API%,Process-IniCompactShim

[Process-IniCompactShim]
If,%PEBakery%,Equal,True,Begin
  IniCompact,#1
End
Else,Begin
  Set,#8,DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY,DUMMY_Key
  Set,#9,DUMMY_Value
  IniWrite,#1,#8,#9
  IniDelete,#1,#8
End

// In mouse cursor code
[Macro_Cursor_Process]
// (Preceding Codes)
IniCompactShim,%MacroCursor_w%
TxtReplace,%MacroCursor_w%,"#$q#$x","#$x"
TxtReplace,%MacroCursor_w%,"=#$q","="

If you prefer a shorter code, here it is:

Code: [Select]

// In Macro Library
[Variables]
IniCompactShim=Run,%API%,Process-IniCompactShim

[Process-IniCompactShim]
Set,#8,DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY,DUMMY_Key
Set,#9,DUMMY_Value
IniWrite,#1,#8,#9
IniDelete,#1,#8
If,%PEBakery%,Equal,True,IniCompact,%MacroCursor_w%

// In mouse cursor code
[Macro_Cursor_Process]
// (Preceding Codes)
IniCompactShim,%MacroCursor_w%
TxtReplace,%MacroCursor_w%,"#$q#$x","#$x"
TxtReplace,%MacroCursor_w%,"=#$q","="

even shorter, this:

Code: [Select]

// In mouse cursor code
[Macro_Cursor_Process]
// (Preceding Codes)
IniWrite,%MacroCursor_w%,DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY_DUMMY,DUMMY_Key,DUMMY_Value
// Add only this line
If,%PEBakery%,Equal,True,IniCompact,%MacroCursor_w%
TxtReplace,%MacroCursor_w%,"#$q#$x","#$x"
TxtReplace,%MacroCursor_w%,"=#$q","="

If bob.omb wants, I am ready to contribute fully-patched .script files.

On the technical side, I implemented IniCompact command which replicates side-effect of WB's IniWrite command.

As a side note...

I agree with PEBakery decision but you should ask ied206 "another compatibility option" for such things,
there are many plugins written that way and I am not here. see: http://theoven.org/index.php?topic=2834.msg35012#msg35012

Sorry if he and I bothered you. I will talk to the proper maintainer for similar matters.
I guess APT001 talked to you because he wanted to honor the original writer.

As you may notice It is the opposite, I do not think ied206 check Win10PE SE or other topics for PEBakery, eg. there are new posts by ied206 on the PEBakery section after you open the current topic.

In fact, I was not able to visit theoven for months because I have been quite busy with personal things (as well as PEBakery development).
I started to posting to theoven again only a few days ago because PEBakery beta 6 announcement was ready, and I came across this article today.
I could not check all relevant new posts in only a few days...

I removed my post, since Homes32 find it too complicated and like to post game on them :
Current Topic : Homes32 reply 6 http://TheOven.org/index.php?topic=2958.msg35099#msg35099
Current Topic : Lancelot reply 8 http://TheOven.org/index.php?topic=2958.msg35101#msg35101

Sorry, I forgot PEBakery development routine, my mistake.

I removed my post, since Homes32 find it too complicated and like to post game on them :
Current Topic : Homes32 reply 6 http://TheOven.org/index.php?topic=2958.msg35099#msg35099
Current Topic : Lancelot reply 8 http://TheOven.org/index.php?topic=2958.msg35101#msg35101

Sorry, I forgot PEBakery development routine, my mistake.

I removed my post, since Homes32 find it too complicated and like to post game on them :
Current Topic : Homes32 reply 6 http://TheOven.org/index.php?topic=2958.msg35099#msg35099
Current Topic : Lancelot reply 8 http://TheOven.org/index.php?topic=2958.msg35101#msg35101

Sorry, I forgot PEBakery development routine, my mistake.

Overall, Iniwrite side effects is a very fundamental thing that I had thought PEBakery already figure out and already did the required compatibility option.

So this is fundamental behavior now and not

Idiot Winbuilder Sabotage

 

Ya'll are making this too complicated. no need for "call,blah,blah,blah", shims, etc.

just add the line

Code: [Select]

If,%PEBakery%,Equal,True,IniCompact,%MacroCursor_w%

or if you prefer a less "wasteful" variable

Code: [Select]

If,Not,%EngineVersion%,Equal,"",IniCompact,%MacroCursor_w%


• if the user is running PEBakery the leading/trailing spaces, and padding between = will be removed WITHOUT the "IDIOT SABOTAGE!!!!!!" comment deletes, lines before [] deletes, etc...
• if you are building under winbuilder life goes on and the user gets the full "IDIOT WB DEVELOPER SABOTAGE!!!!!!" experience just as they know and love.
• the users of your plugin will thank you and be happy.
• did i forget to mention its ONE line of code with no overhead? 

of course, you are the author of the plugins in question and your perfectly free to ignore the above suggestions. I won't deny you that freedom. Hopefully this post serves as a resource for those who do use and enjoy those plugins, and may continue to do so under a less troublesome builder with minimal effort.

I removed my post, since Homes32 find it too complicated and like to post game on them :
Current Topic : Homes32 reply 6 http://TheOven.org/index.php?topic=2958.msg35099#msg35099
Current Topic : Lancelot reply 8 http://TheOven.org/index.php?topic=2958.msg35101#msg35101

Sorry, I forgot PEBakery development routine, my mistake.

Ya'll are making this too complicated. no need for "call,blah,blah,blah", shims, etc.

I do not have time to waste following your post games.
 I already responded to your comments and you like to post game them writing "complicated"
   post game: ignore what are written (subject is not about 1 fix on 1 plugin) , put wrong comments, provide wrong fix that only looks correct.

Anyway, this section is for PEBakery, Following your comment, I removed my previous posts. 

Going back to my first short simple not complicted response to current topic:

I agree with PEBakery decision but you should ask ied206 "another compatibility option" for such things,

Whoever behind, add a compatibility option to PEBakery or not is up to whoever PEBakery author behind.
 I do not even know how to enable PEBakery compatibility options, I only follow relevant posts, I do not care.

With your words No need to complicate things and waste time which you like to waste which I do not have.

@Lancelot

You really are a complete prick!, this forum has been running so well recently without you fuckwitted input and comments, everyone has been getting on and progress has been made by all, then you come back and post your pathetic responses to posts and act like you are some kind of king, when in fact the best description I can think of for you would be a complete and utter cock womble

Since I had to delete my posts after Homes32 comments, to summerize to public :

So I learn things on the current topic:
+ PEBakery does not have "Ini" compatibility options to be compatible with current plugins.
+ Homes32 likes to hide this incompatibility with a workaround on 1 plugin, ignoring the rest of plugins that silently fails, with a set of misguided info, as usual.

Homes32 workaround only provide such a thing:
- Looks working on default, who cares if silently fails on other plugins,
-  winbuilder developers stupid behavior we know from the past, where this stupid ini-side-effect behaviour came from. 

No need to jump from one stupid to another.


***************************************************************
To ALL Others:
Although Project default build "looks" like working with Homes32 workaround,
 many plugins will silently fail since PEBakery does not have "Ini" Compatility option for today.
***************************************************************





@APT,
That is another reason you should open anything related to PEBakery to PEBakery section.
 It is PEBakery decision to provide compatibility or not,
  or PEBakery goal to have options for compatibility or not, I really do not care.
   I do not have time to spend post games like Homes32 or others, I fully left PEBakery development long time ago because of Homes32 post games.
     Sorry for providing info to your post.
       My mistake.
          I should leave PEBakery people alone to figure out themselves.

@Lancelot

You really are a complete prick!, this forum has been running so well recently without you fuckwitted input and comments, everyone has been getting on and progress has been made by all, then you come back and post your pathetic responses to posts and act like you are some kind of king, when in fact the best description I can think of for you would be a complete and utter cock womble

Good to see such post.

I only came around to update 1 plugin on the other topic
http://theoven.org/index.php?topic=2906.0
from response fixed successfully. 
What did you recently do productively instead of hiding behind a fake id to use bad words.

APT ask PEBakery thing and I figure out missing with PEBakery,
 after that I get Homes32 post games and you "commonsense" very common sense post.
  I do not care PEBakery decide to fail on old plugins written months (and years) ago, It is sure my mistake to feedback properly.

 Thanks for reminding me why I decide to be away from PEBakery.  and why I decide to be away from idiots like you, why current forum created.

   For now I keep your post as an example to public about idiots why this forum created years ago.
    Because of immature people just like you.
     Next time you post similar I have to ban you like all other normal forums in the world.
      Thanks for giving me smile of the night. 

ps:
Reminding, When I was away, idiots like you banned from theoven forum by other admins.
 Self proving My existence does not matter, there are always idiots like you who come and goes,
  we get rid of them and people like you which provides environment where as you write everyone has been getting on and progress has been made by all
    I am sure you will be banned by other admins in future too.
     Only idiots left are post gamers and fake id posters like you which happens time to time, attacking me or others.
     With getting rid of idiots like you at theoven, not allowing to attack other people; LiveSystemPro, PEBakery, WimBuilder2 and new projects  etc. born here.
      Thanks again reminding me why we create current forum, because of usual idiots like you. 

Hello Lancelot, long time no see. 

First, let me suggest a perfect solution that will greatly help Win10PESE developers.
Let me introduce the macro IniCompactShim.
The macro should work both on WinBuilder 082 and PEBakery beta 6+.

I don't think it is a perfect solution.

Why PEBakery was written?
PEBakery is compatible with WinBuilder 082.
PEBakery works as a drop-in replacement of WB082, while providing much improved envrionment.

3. Turn on compatibility optionss
For Win10PESE and Win10XPE, turning on compatibility options is required.
Create PEBakery.ini in %BaseDir% and paste these snippets:

Code: [Select]

[Compat]
AsteriskBugDirCopy=True
AsteriskBugDirLink=True
FileRenameCanMoveDir=True
AllowLetterInLoop=True
LegacyBranchCondition=True
LegacyRegWrite=True
...

with this settings PEBakery simulates WinBuilder's bugs and quirks.

There are already something about compatibility. It is better solution than update every plugins.

LegacyIniWrite=True ? BehaviroIniWrite=WinBuilder ? or something should fix this in one shot.

So I don't know why, PEBakery didn't that, and ask WinBuilder's plugins to write:

If,%PEBakery%,Equal,True,Begin

For people they just use Released Win10 PE SE, Win10XPE, those codes are useless.

Who want to use PEBackery to build the Win10 PE SE, they was following your description to add the Compat settings file,
NO needs to ask plugin's creators to write plugin to compat with other builders.

I also wonder why you make it to be complex.

It is very easy to detect a project is Win10 PE SE or Win10XPE, PEBackery can easily turn on the options auto, but it didn't,
push this to end users.

About compatibility, for old legacy projects, they shouldn't modify any thing to make it work, Build them out-of-the-box that is friendly.
For new projects with PEBackery's improve functions, you can make a new variable for them.

Hi slore,

happy to answer your questions.

LegacyIniWrite=True ? BehaviroIniWrite=WinBuilder ? or something should fix this in one shot.

So I don't know why, PEBakery didn't that, and ask WinBuilder's plugins to write:

If,%PEBakery%,Equal,True,Begin

Performance. to replicate that behavior you need to read the entire .ini file into memory, then rewrite it. That's extremely wasteful when all you want to do is change a single value. Oh yeah. and its slooooooww, and gets slooooooooower, the lager the .ini file. Why should PEBakery users have to suffer this behavior PROJECT WIDE for the benefit of a handful of "plugins" and/or developers who couldn't be bothered to use existing commands and trim their IniRead variables (StrFormat,CTRM/TxtDelSpaces/TxtDelEmptyLines anyone?) and instead decided to take advantage of bad wb behavior?

IniCompact is an ideal "drop-in" compatibility solution that allows the developer of the affected "plugins" or a user who just wants them to work, a one line fix, where they are in complete control of which files get compacted and without the destructive behavior of wb deleting things it doesn't like in the process.

There are already something about compatibility. It is better solution than update every plugins.

No need to update EVERY "plugin" If you look you will find that In the default WinPESE project selection this isn't an issue. It's a few optional "plugins" that take advantage of bad wb behavior (such as the mouse cursor "plugins") In the case of said "plugins" its used as a lazy way to get rid of whitespace so the author didn't have to StrFormat,CTRIM or write multiple TxtReplace lines in order to remove doublequotes. Is it fair to penalize every "plugin" author and the project builder for the choices of a few? or is it justified to ask the few to  SANATIZE their input or at a minimum add ONE line of code to their "plugin" that allows them to keep their lazy behavior?

Now, PEBakery is open source and developers are open to change and suggestions, so if you and other developers, and users feel very strongly that everyone's life would be better with a inefficient, slow, IniWrite behavior, please get together and make a good case for a compatibility option to enable the behavior project wide. If enough developers (and users, they are the ones who ultimately pay the price) think its a good idea, we may try to implement it. Or for the time being we could update 5 "plugins" with If,%PEBakery%,Equal,True,IniCompact,%MacroCursor_w% and take any other action on a case by case basis as they come up, just like developers have been doing the last 15-20 years.

It was a simple request, as a courtesy to the "plugin" author to update the code to their 5 "plugins" so all users could continue to enjoy them. If that author chooses not to, fine. That's their choice and t least then the decision is on them, and we can point users to other options, or the user can fork the "plugin" and distribute an updated version.

It is very easy to detect a project is Win10 PE SE or Win10XPE, PEBackery can easily turn on the options auto, but it didn't,
push this to end users.

It's not that simple. how do you detect the project? The title? the author? hash embedded resource? what if the title changes? what if another author forks a file and keeps the original author in the author field as a gesture of respect to give credit? lots of users heavily customize projects. what if a user uses a resource or modifies a project to use pebakery behavior but the detector still keeps thinking its the "stock" project and insists on turning on compatibility options that break the changes/fixes? what happens when a project author makes changes? does PEBakery development have to get a list of breaking changes from each project author, update and recompile PEBakery, and distribute new binaries to everyone? what if everyone doesn't update the binaries but keeps updating "plugins" via on-interface buttons? then we have a .exe hell where everyone is on a different version that may or may not have a working auto compatibility detector. this is a nightmare for pebakey devs and project devs alike. have an option to turn the detector off? we already have a single button that turns all compatibility options on....even better, PEBakeryCompat.ini can be configured and distributed by each individual project author in the same folder as the projects script.project file guaranteeing Out-of-the-box compatible configuration. that is the reason compatibility options are stored in a separate file and not the main pebakery.ini  As you see, its far from easy and that is why an automatic compatibility checker is not included. If you have specific suggestions on how to overcome any of the above, I am more then happy to look into them.

best regards,
Homes32

Hi Homes32,

As you wrote, you are making this too complicated.

I had already written which was complicated to you :

Summary :
IniCompact is good for PEBakery. 

But not good for current plugins compatibility,
 better you add a "compatibility" option for IniWrite functionality,
 this is NOT only 1 plugin that uses IniWrite side effect.

Now 1 plugin became 5 plugins on your post .... number will increase as there are more than 1 stupid ini functions that requires a lot more than 1 update on plugins.
Sorry for providing detailed info previously, I already deleted relevant posts to suffer from your continuation of post games in order to avoid wasting time.

I had already written in detail before, It is not a simple update to projects and all plugins on server,
 No need to PostGame by mixing Correct Argument (stupid winbuilder developers lazy bad decisions on ini function)
 with a False Argument (not correct: It is not only 1 plugin fix, not correct: It is a simple 1 line fix, not correct: Speed , NotCorrect: you do not have to load all ini file to memory if you want to implement stupid winbuilder ini behavior, loading to memory and speed down is only a lazy & quick solution, Not correct ....... (keeping short in order not to get too complicated to Homes32))

Also, other arguments that are out of subject are wrong too ...

As written in detail before,
 It is a nightmare that requires at least a month of work requiring a project admin be active around checking all plugins and relevant updates.
  In opposite, we only could find free time to update only 2 plugins in last 5 or more months. (which was written in detail before which you find complicated)

Well, such fundamental things could be done long time ago If PEBakery followed initial path before you were around when ALL project admins very active around.
 Probably today without project admins active around all projects were using PEBakery.
  After PEBakery decides to go to another path, I left PEBakery development, current situation and other things in the past and future are results of PEBakery decisions which I do not care at all. I had already written same thing when I left, Ini functions is not the only thing I do not like about PEBakery and I do not care.

No need the hide the dust under the carpet as winbuilder developers did with ini functions by wrongly updating 1 plugin the way you wrote.
As I wrote "No need to jump from one stupid to another."

I do not care If PEBakery decide to implement or not to implement compatibility to ini functions or not, or it will be a quick lazy slow implementation or smart fast implementation.

I only comment to your post game that is all.

At the point you have Homes32PE or whatever with PEBakery that does not read or support .script files, you are perfectly correct with how ini functions should work (and I agree) like LiveSystemPro is.
  http://theoven.org/index.php?topic=296
 Which is not the current topic situation.

What is PEBakery?
PEBakery is a builder specialized in customizing Windows PE.
It is intended to be used with projects such as Win10PESE, Win10XPE, MistyPE and ChrisPE.

I decide to be away from PEBakery development in order not to waste time to respond to post games probably a year or more ago. I am right again.
 Come on Homes32, you may have a lot of time to create post games and you are post gaming like winbuilder developers.
  The difference is, There is no discussion to win or lose, I do not care PEBakery things, I do not care PEBakery decisions on current subject or other subjects,
   so you do not need to Post Game at all, it only serves your self-satisfaction and wasted time.

------------------------------------------

About compatibility, for old legacy projects, they shouldn't modify any thing to make it work, Build them out-of-the-box that is friendly.
For new projects with PEBackery's improve functions, you can make a new variable for them.

@slore ,
That was most of the idea when PEBakery first developed,
 at one point Homes32 joined PEBakery development,
  as a result I left since PEBakery development left the initial idea. Life and Luck.....
Initial Idea was, step by step, first getting compatibility the way you wrote,
  later continue plugin development with better functions by getting rid of winbuilder stupid behaviours.
   As a result we would be using only PEBakery today and leave winbuilder behind.
Thanks to Homes32 (sarcasm),
 PEBakery development decide no to follow that path,
  I fully left anything related to PEBakery since I do not like to waste time to respond post games.
   But still it is a winbuilder sin with Homes32 that comes and goes time to time like current topic which I try to suffer.
------------------------------------------




Keep things simple:
- APT report something
- Lancelot respond pointing the missing thing shortly
- ied206 (developer) respond (I guess misguided) it should be easy
- Lancelot responds with detailed info about why it is not easy.

Normally, Things goes much or less that way with all developers I contact on the internet after many years (exception: people who use winbuilder, one of winbuilder sin)
 after that point developer - ied206 decide what to do and life goes, no need post games and complicate things Homes32.
  You do not post game, I will not need to respond,
   there is nothing to win or lose on my side,
    I do not care PEBakery at all,
      Reminding I did not open such topic or I do not have such request,
       I respond to end user APT that is all
        (which proves my mistake, I should expect Homes32 start post gaming at one point as usual.. I should only move APT topic to PEBakery and do not feedback ),
         PEBakery is your kinder garden, EOD (End of Discussion). 

If the view point is that making people both plugin developer or end user happy to use,
I'm not be limited on Compat with WinBuilder's mess script.

As this plugin, when people want to use a custom Cursors, I won't let them have to write 200 lines script,
Just few lines like:

main.bat

Code: [Select]

7za.exe -x breeze_cursors_by_niivu-dcz3zpb.zip "%X_WIN%\Temp\breeze_cursors\"
call TextReplace "%X_WIN%\Temp\breeze_cursors\install.inf" "HKLM," "#n[Disabled_Wreg]#nHKLM,"
echo InfDefaultInstall.exe "%%X_WIN%%\Temp\breeze_cursors\install.inf" > "%X_Startup%\BeforeShell\breeze_cursor.bat"
echo reg add "HKCU\Control Panel\Cursors" /ve /d Breeze /f >> "%X_Startup%\BeforeShell\breeze_cursor.bat"
Learn new script syntax(AND only works on specific things), and write 50+ times script codes won't make me happy.

When PEBakery starts, I said my suggestion, but ied206 didn't consider it.

For now, What I see about PEBakery is: More re-create wheels than evolution.

WimBuilder2 don't re-implement IniWrite, IniRead, RegWrite, math, self control flow ... but it also build PE and be faster with least codes,

and I have time to make full functional PE(more powerfull than any other WIN10PE) with New thing:
* MTP support
* RDNIS support
* Remote Desktop Service
* origin USB eject
* Devices and Printers
* Duel-Session User Login

I think 90% people actually don't care what Builder is, but what a PE can be built, and they just add 3rd-applications, do some customization.
my builder is working for me to build/test PE in faster way, and focus on how can I modify wim in less/easy to understand way.

PEBakery is a good project for PEBakery's Developer, but not good enough for end users now.

It has the totally diffrent design principle with my mind(I don't advocate to compat with mess WB script, I prefer to use ready-made things).
WB's script is inefficient, and lots of plugins have inefficient design codes, like HiveLoad/HiveUnload in every plugins.

Answer your qustion:

It's not that simple. how do you detect the project? The title? the author? hash embedded resource? what if the title changes? what if another author forks a file and keeps the original author in the author field as a gesture of respect to give credit? lots of users heavily customize projects.

I won't never think it so far, just check BuilderSE.ini and WIN10XPE.ini should be enough.
If someone who use PEBakery with WIN10 PE SE, WIN10XPE, but rename the config file, ask him to write explicit option.
ProgjectEngine=WinBuilder or something else.
Be out-of-box for most people, and little config for few people.


I don't create plugin for Win10PE SE or Win10XPE, and I don't use PEBakery with those projects. I don't have any strong suggestion on this,
just comment tech-problem( compatibility) with a developer opinion. The rest is on yours.

I perfer to updating (fork) plugins than ask them use new way, which are inefficient codes, because they write plugin with WB's "feature" not PEBakery,
the PEBakery devs won't waste time to implement the side-effect IniWrite.

Hi Slore

what can I say

PEBakery is a good project for PEBakery's Developer, but not good enough for end users now.

simply, untrue

regards APT

Hi Slore

what can I say

PEBakery is a good project for PEBakery's Developer, but not good enough for end users now.

simply, untrue

regards APT

OK. not for all end users. Just for me(a end user), it is not good.

1. I can't run it in winre.wim, or custom PE, and Slim Lite RAMOS what I used. Because there is no .NET.
2. Not good to support other language than English(like Chinese, Japanese, etc).
    UI, plugins, even recreate RegWrite() function.
3. UI interface are hard to custom, size, color, style.
4. script is too long and complicated like WB does.
...

Also WinBuilder is not good to me, I was expected PEBakery could some different, and evolution,
but it is not, so I created my own builder with less time. I will not persuade others to use mine, or plugins creator to do adaption on it.
It is good for me, and save me lots of time than WinBuilder. I shared it, if someone want to save time and build PE quickly, they can use it for free.

Multiple choices are good, Users can select the one what is fit to himself.
Or Build PE with both them.

Hi Slore,

*
I can use many plugins like the one mentioned on current topic "Mouse Cursors Breeze Cursors by niivu"
with other projects and builders :
LiveSystemPro (4 projects), Win10XPE, WimBuilder2, WinPE (Assessment and Deployment Kit),
naturally same plugin also works with other projects Gena, Win7PESE, Win8PESE, Win8.1SE, Win10PESE.
without changing anything on plugin and it does not look complex to me at all. 

Again naturally WimBuilder2 and LiveSystemPro looks more complex to me, since I am less familiar with their syntax and etc.... 

Keeping short, Things out of PEBakery subject better out of current section of the forum, I only respond shortly.

*
I agree with your idea to get "compatibility easier" to end user by PEBakery,
maybe PEBakery can have a list of projects following [Main] Title= of relevant projects
eg.
PEBakery.ini
Compatilibility_Enabled_Projects=Gena,Win7PE SE,Win8PE SE,Win8.1SE,Win10PE SE,Win10XPE
such ini file can always be updated during builder updates with such a dynamic list.

maybe not a good idea from PEBakery development point of view, fine to me, I do not care.
 Such compatibility options created after I left PEBakery and I do not want any post game after my current input to the subject you mentioned.

All I want is I do not want to be in a position to respond to anything related to PEBakery from end user like current APT post in future which always have potential to be followed by Homes32 post games and continues with wasted time.
Any improvement that serves this idea is nice to me (like yours), either with above suggestion or another way. (<--- I mean I do not want to get post game response for commenting on this)

Even If I accidentally hit a PEBakery hidden agenda, whoever have such agenda just do not post game to my comment at all, I already wrote my intention "I want to be away from PEBakery related things"

*
I agree with your comment "multiple choices are good" ,
 I am proud TheOven.org provide the liberty to developers to develop other projects and builders,
  which was one of the goal of TheOven forum. 

This way I can use plugins with other projects too. 

*
Keep in mind, you will get a pm one way or another after your presence on the current topic.
 Nothing new to me, just keep alert.
  Old winbuilder developers always pm to others saying "I am an old retired programmer worked on things for blabla years...."  etc.
     and sometimes provide some free tools to only have goal to create some allies.
      In the end winbuilder development died. Homes32 knows I predicted that at hot development times of winbuilder. I am right again. 

One thing I learn on this pe development world, human nature is everywhere with all bad and good sides.