SyMenu Forum

chef

all messages by user

23/06/2019 Topic: Bug resp. limitation in new VirusTotal integration chef	I'm new to SyMenu. So various questions are raised and could not yet find the answer myself. According to section 11. 2. of the manual, VirusTotal report has been integrated in SyMenu version 6.0.8. As you can see in the attachement enclosed in the package list section, this works for some packages while not (yet) for others. In that screenshot, some packages report such a VirusTotal report while this field is empty for others, hence a bug as different to what is specified and described in the manual. The manual is lacking information on these situations, their interpretation and what integration means exactly. Is this report entered into SPS and hence corresponds to a situation shortly before SPS package version gets published? Or does SPS integrate the query to VirusTotal and reports the situation for the moment you get this list in SyMenu package manager resp. form? What does it mean, if this field is empty? edited by chef on 23/06/2019
24/06/2019 Topic: SyMenu package manager eror in SPS editor contact chef	Gianluca wrote: chef wrote: What's wrong with this forum software configuration? This forum software configuration doesn't seem to work as expected neither in preview nor when submitting You simply misunderstood the documentation. You wrote (img)symenu.contact.20190623.png(/img) because "symenu.contact.20190623.png" is the name of your attached image but you have to write a logical name instead: (img)att1(/img) and for your second image: (img)att2(/img) Please note that in my examples I'm using "(" instead of the correct "[" to avoid the forum interpretation, but you need to use the square brackets. I'm not sure if I understood your hint correctly. Do you mean that I should have used the names of the documentation hint as literals instead of using the actual file names of the attachements (meaning that forum software will make the mapping between literals and the actual file names of the attachements)? Thanks for the hint. I'll try next time using as literal.
24/06/2019 Topic: The SPS scripting engine chef	Gianluca wrote: The dependencies release with a certain package is not our business. As SPS editors we release the packages as they are released from their authors. Since the AutoIT major is still stuck on the 3.3.14.5 (https://www.autoitscript.com/site/autoit-script-editor/downloads/) I can't update it or update one of its dependency (SciTE). This I already learned yesterday when following a recommended reading where you refer of this forum into a thread of another forum in the States. And as far as I understood, the issue of package management including such dependencies one of the moderators claimed as still open meaning not addressed in a portable manner by any implementation or proposal in that other forum. This means that neither you nor any competitor had addressed this aspect yet. Nobody in that threat made a different claim. Gianluca wrote: If in your opinion a separate SPS package for SciTE is needed you can try to create it by your own and eventually share it with the community. My post was in answer to the questions raised by sl23. He elaborated on handling of packages requiring another download. In that context, he raised several questions with seemingly not getting a reply yet. So I replied on his question if the editor mentioned by him works also without that context of the other package or only in that context. My reply was that it works also without that context. I continued that the option to have a seperate SPS package for SciTE makes sense as it works also stand alone. Priority would probably not be high as there exist already editors with syntax high lighting in the suite although not yet SciTE as stand alone package. Before I replied to sl23, I looked up in the suite and found that the situation is still as he reported and no seperate SPS package for SciTE created although another SPS package exists which extends the one included as reported by him for use in the context of another tool. Gianluca wrote: If in your opinion a separate SPS package for SciTE is needed you can try to create it by your own and eventually share it with the community. I'm always open to new SPS editor and always available to help the newbie! I already new this openness. (You mentioned it in another topic in the forum on a different request to another thread author.) And as clarified in this response, I see no such need in the sense of requirement. I consider it just an option which makes sense. So do you recommend me starting to create such a SPS package for learning (and maintaining) a SPS package? (And I see and learned now that there exists a work around to the limitation of the forum software to support my style of quoting reported in another threat.)
24/06/2019 Topic: Was v6.08 released prematurely? chef	Gianluca wrote: chef wrote: Then I wanted to report it to SPS editor. This revealed the next bug. Clicking on the corresponding option opens a new tab in the web broswer. But the opening page is a web error page I contacted the editor to ask him to re-activate the contact form. edited by Gianluca on 24/06/2019 I tried also to contact the SPS editor. As I did not get a feed back before if you would be so kind to forward these posts, I tried if the same user name in this forum relates to the same person and wrote a PM via this forum to raise his attention on these posts. And he replied to me similarly that fixing will take some time as he's currently not at home. According to what I understood of the contact form hosting web site, re-activation probably will not work. It sounds to me that creating a new contact form with the new method on offer of the same web site will create a new contact form. I'v not clue if that new contact form will result in the same URL which has been intentionally deleted by that hoster or into a new one. If the result is a new one, creation of the new contact form will not be sufficient as this SPS editors SPS packages will then need a refresh of the contact field. This raises the new question if the SPS package manager does support and recognize an updated contact field as I didn't read so far of a versioning of SPS independant of the versioning of the packages they describe? I fear that SPS package manager will ignore it as long as the described package doesn't get updated. And I further guess that a work around will be to force update in SPS package manager in order to take into account the new content field. Am I right? Gianluca wrote: chef wrote: Create a free contact form for your website! Sorry no time for this, the priority is SyMenu not the web site. edited by Gianluca on 24/06/2019 This was meant as part of the message addressing the (currently not directly addressable) SPS package editor, not you as you aren't the SPS package editor of those packages. Gianluca wrote: chef wrote: And here you see another bug resp. limitation of this forum feature as I don't have any influence on font size. It's a side effect of quoting off different sources and how the forum software handles it. I can only influence style like bold, italics or underlined as far as I can see. Again with the forum... I can't correct the forum bugs because I'm not the forum author. IMHO it's a good software, it's free, it's easy to use, it's compatible with the platform I'm using for the web site, it it's bugged it's not so bugged to be unusable, and I have not time to create a forum software by myself. So please try to workaround all the bugs of this bad software and don't report them to me. edited by Gianluca on 24/06/2019 I know that you're not the forum software author. And as the forum software is in trial edition, it reveals its source in the mean time and found the authors note on the few differences between trial edition and subscribed resp. registered edition (and that your usage of trial edition is explicitely permitted by the author). What I don't know is when I observe a limitation if it is due to its configuration or the software itself. The first variant could be fixed by you while the second one obviously not. No. It's not free nor freeware. Only the trial edition is free while the others are on subscription (with almost same feature set but varying support options all missing for the trial edition). (In the other forum on portable software in the states where you're member too, there is a classification of software types/licenses and some trends. According to the FAQ there, such mixed types and licenses are wide spread resp. converted to.) Your choice wasn't limited to use this trial edition forum software or create your own. There are several other forum software available free of charge, some probably more wide spread, probably requiring to install another tool so that alternative forum software may run on your hosting environment. I'll continue trying to find work arounds as far as suitable and ignore other effects of the forum software (as long as they're not blocking). And as you see, I already found some work arounds and you provided me already another hint in this thread. (Some have to do with the order of processing, just changing processing order when writing.) So as far as my notes on the forum software concern you, it's fine to provide feed back if the observation is due to configuration or inherent of the forum software. And as far as I've seen, there are forum users who master this forum software much more with astonishing effects.
24/06/2019 Topic: Was v6.08 released prematurely? chef	Gianluca wrote: chef wrote: The best option would be that SPS allows such a mirror list [of download URL] and SPS editors use it This could be a nice feature above all if your considerations about the SourceForge limitation policies against repeated download is true. Can you supply some official documentation regarding this limitations? I don't think a limitation like this can be kept secret because otherwise they'll start to have bug reports from their unaware users. I don't see any dependancy. My proposal should always work regardless of repository concerned. And it may increase reliability of SPS package manager regardless of repository or package concerned. Only for cases where the software authors prohibit such second source or mirror list for download, this list would just contain the single member as currently. (You mentioned one such software author in the forum. I know at least a few others.) As I already wrote to you by email, I remember such a recommendation and limitation published on SourceForge before a major ownership change of that repository. I didn't save copies of such web pages as already written in that email. So I can't supply you this documentation for the case of SourceForge as I looked up before resp. during writing that email. I further mentioned the case of the package SIV System Information Viewer where even you found such an authors clear preference to download not of his web site but instead of the mirror list he provided. Do you need also documentation on the limitation policy? It's a long time ago that I've read those. And I didn't save them locally. If you need it, I'll have to search again. Independant of that I occassionally manage a few web sites. I didn't investigate when such configuration options are provided by the web server itself and when by some security extension. I can assure you that such solutions exist and are in use. When I configure such items, I take sliding windows of either in the range between 1 and 5 minutes into consideration, and always to take additional conditions into the evaluation in order to prevent locking me out myself and to address (at least partially) dangers of denial of service (DOS resp. distributed variant DDOS) attacks. It's a hardening policy for abuse prevention.
24/06/2019 Topic: Was v6.08 released prematurely? chef	Gianluca wrote: chef wrote: I haven't been clear enough. I didn't write nor claim that AV stopped downloads. I meant that I observed that SyMenu aborted initiated download while AV intervened after successful download for inspection, holding back the download success until end of AV checking. In the view of SyMenu download was still in progress while in view of operating system and AV download was finished. That's no error. That behavior may depend on AV edition. Better AV editions try checking so soon while basic editions try it later when another program opens it for execution or unpacking. SyMenu package management seems to assume that either no AV software is installed or only such a basic edition one, not a more powerful one. That's a bug in SyMenu package management if my assumption is true. I perfectly disagree with this. edited by Gianluca on 24/06/2019 I didn't catch up on which part you perfectly disagree? Do you disagree with my statement not to refer to AV stopping download? Do you disagree with my observation that SyMenu aborted its initated download after download has finished and not yet reported back to SyMenu? Do you disagree with my assessment that operating system behaviour or AV behaviour to intervene is no error? Do you disagree with my observation of differences between AV editions (regardless if of same AV publisher or different ones)? Do you disagree with my perception on the relation between SyMenu and AV software or operating system file system configuration? Or on all together? Gianluca wrote: chef wrote: Which kind of software reports initiates the reported timeout? How may I know? How does SyMenu package management determine if download is ongoing or not? How does SyMenu package management distinguish between downloading and some intervention by operating system (i.e. configured Windows policies or security policies marking every download) or AV software? A download in the Internet works this way: - hi man, I need that file - sure, give me your hand before - (what a nice start.. this is one of the boring guys...) Sorry you are right, what a rude I am. Now can you give me that file. I really need it - no man, since I'm a very precise host and I'm following all the protocols, I firstly have to give you some information about the download - (uuuhhh this guys is is a real pain in the ass... I have things to do)..... then OK, give me the info - here is the file name, its mime type, its size... The sketch goes on but the thing to understand is that SyMenu doesn't make anything different from any other download manager in the world. SyMenu knows that a download is finished when the file reaches the expected size, it declares timeout when the file is no longer downloaded but the host doesn't send any byte for a while, if the OS or the AV make something with a downloaded file, the download manager can do nothing because of the system privileges order. Your browser behaves exactly the same way. Everything is on the hands of Windows or AV. edited by Gianluca on 24/06/2019 These questions were not on the download itself but on SyMenu resp. SPS package manager management of handling downloads. I disagree on your claim that SyMenu doesn't make anything different from any other download manager in the world. It doesn't match my observation. And you provided a work around in your inital reply which was working perfectly for almost all cases where SyMenu aborted with timeout error. If your claim of no difference would be right, that work around would not have worked! I can assure you that your promise of your second to last sentence quoted above is not true. My standard web browser doesn't behave so strangely. Your hint for work around of the SPS package manager bug works very well. It did not experience any timeout although SPS package manager aborted prematurely on the same packages reporting time outs in contrast to your promise to experience the same timeouts with this builtin download manager of the standard web browser! I know various download protocols. I even know command line tools handling various of those protocols in various variants. Sometimes I need them to bypass size limitations of download managers builtin to web browsers, never for time outs (except SPS package manager!). These protocols have their own timers at network level, transport level and application level. For longer lasting downloads (i.e. a complete operating system distribution, a complete application stack intended for import into virtual machine), these download managers provide the option to enable a feature so that the application level get's confirmation that the download is still going on to prevent premature abort of such long lasting downloads. Where may I configure this feature in SPS package manager? Why do I need to activate such a feature in SPS package manager even if the downloads take between 1 and 6 minutes while I may need them with other tools and wweb browser only sometimes for downloads lasting much more than 40 minutes? When I use your working work around, it seems to me that for some repositories, the download does not report the size in advance while doing so for other repositories. So why does SPS package manager initate an abort on ongoing download even if the repository didn't provide the size to expect before nor during the download? How may I deactivate that timer or reset it to some download protocol default of 10 minutes network inactivity? Why doesn't SPS package manager limit itself to the timers specified in the download protocols but uses its own? At the GUI level, I didn't see a configuration option for this internal download timer. How may I configure it either by configuration file or command line? I didn't look up what kind of information SyMenu provides on those time outs in its logs yet. Where may I find these? And for what shall I look? I remember that package Picasa was aborted due to this timeout while the download has finished at network and transport level while not yet at application level because AV software was still proceeding its check. With a look at the logs I may report other packages where downloads were aborted by SPS package manager while the downloads were even not finished at network level! They could be downloaded without any problems with the download manager builtin to my standard web browser. And your hint was directing me how to get the input for this alternative download manager off the SPS package manager. Gianluca wrote: chef wrote: So how does SyMenu package management handle reported download success (after passed AV check) if it reported the same download as aborted due to timeout before? It's impossible. SyMenu can report a download success only if a timeout hasn't happened. edited by Gianluca on 24/06/2019 This situation is not impossible. This situation is the reality for almost all packages which SPS package manager aborted prematurely with time out although in most cases the download was not yet finished and in a few cases the download had finished at network layer but not at application layer. And as far as I've read, I'm not the only user reporting such SyMenu "installation" problems in the forum. And the question was not when SyMenu reports download success. The question was on how SyMenu package management handles the incoming feed back of the network layer for successful download of its initiated download request while the network layer did not report any timeout and SyMenu already processed some download requests later while having reported aborted the still ongoing download as aborted for timeout reasons which cannot be network timeouts but have to by SPS package manager timeouts and SPS package manager not yet having finished the multi-package download request.
24/06/2019 Topic: Was v6.08 released prematurely? chef	Gianluca wrote: chef wrote: So what does it mean that SyMenu package manager reports 0/54 for VirusTotal report? It means that when the editor reviewed the package this VT was able to analyze it with 54 engine and no one reported a suspicios file. This condition can change resubmitting the same package in another moment but SyMenu remains stuck to the first report until the editor reviews the package. Thanks for this precision. With the help of your published manual, I already assumed part of that meaning of 0/54. The important information is the context you now added. I recommend amending that manual section accordingly. The "at the moment of package release" resp. submit would be fine for the understanding there. And your second sentence is worth a N.B. note in that same section of the manual.
27/06/2019 Topic: Was v6.08 released prematurely? chef	Gianluca wrote: chef wrote: I disagree on your claim that SyMenu doesn't make anything different from any other download manager in the world. You partially right here. It's totally useless to speak about this topic in this forum (who cares how SyMenu download the programs in so deep details????) and above all you can use a network sniffer to satisfy this curiosity by yourself, but I can avoid you this fatigue. The only difference between a download manager of a browser and the SyMenu download manager is the user agent I use (mine is wget, the browser one is its own). This is the only reason for the slightly differences between the behaviors. edited by Gianluca on 25/06/2019 When downloading the whole suite as recommended on the SyMenu project web site, most gets downloaded and a few packages not. For most of these the reason is with SyMenu, not with the download nor unpacking nor copying, and SyMenu reports timeout as reason for abort of download, not for unpacking nor copying. When downloading the whole suite, if finishes its work on my computer after something between 2 and 3 hours. I use another tool wsusoffline which does also downloading, unpacking, copying, repacking and a few other things according to my limited configuration of what concerns me and my few computers (current and older ones). It also uses wget for downloading. The whole process takes more than 8 hours and doesn't produce any timeout on my computer, even if run off an USB 2.0 stick! (And this tool is already included even in SyMenu suite!) I tried your work arounds for coping with these timeouts. It worked for most of them. (You don't need to worry on those where it didn't. As directed by you, I've to contact either AV software publishers for some and SPS editors for some. That's already going on.) So for this large majority of cases with SyMenu reporting timeout during download, the work around would encounter the same problems as SyMenu and hence not work. So I've to conclude that there is an unknown limitation within SyMenu resp. its SPS package manager which is not documented. Such a mismatch is usually called a bug. That's why I report it in the bug report thread of this forum as desired by the project SyMenu. Gianluca wrote: chef wrote: This situation is not impossible. This situation is the reality for almost all packages which SPS package manager aborted prematurely with time out although in most cases the download was not yet finished and in a few cases the download had finished at network layer but not at application layer. And as far as I've read, I'm not the only user reporting such SyMenu "installation" problems in the forum. Again, it's impossible. The installation of any SPS is split up in several moments: - downloading - unpacking - copying You can have a problem at any of these levels and it doesn't mean that your download has had a timeout. It can be a difficulty during unpacking, a changed internal structure int the package, an AV that locks one of the mentioned action... Trust what I'm saying... I'm the one who wrote the code. edited by Gianluca on 25/06/2019 I still don't understand. This has nothing to do with trust. I'm trusting you. Otherwise I would not report. Do I understand right, that SyMenu reports abort of download with timeout, even when download was successful but issues appeared with unpacking or copying? Do I understand right, that SyMenu may experience difficulties during unpacking when done automatically while not experiencing such difficulties when doing so with local package as source instead of web site? That sounds like strange mystery. Again, I'm not writing here on the small minority of cases where AV intervention was the reason. And this AV intervention was a lock just in one case, not the others. Gianluca wrote: Usually a user has got an issue, reports it, I solve it and we are all happy. edited by Gianluca on 25/06/2019 I can confirm that I reported my issue in the forum when doing the first time installation as guided on the project web site. And I further can confirm that you addressed the part on timeout with a work around. But a work around is something different then a solution. It allows to progress while the issue still being unresolved within the program. Work around are intended to progress while keeping the bug reported and on a list for looking when and how to find the root cause and to fix it. That's why this project SyMenu has decided to use this thread for bug reporting. And you confirm that this decision of the SyMenu project creates some difficulties to you to recognize suggestions for improvement. Or did you mean something different with declaring these suggestions as hidden? Gianluca wrote: Instead you are investigating the internals of the program with no cues in your hands because you didn't read the code, edited by Gianluca on 25/06/2019 No. Your observation is wrong. How do you come to such premature conclusions or perceptions? I only reported my observations of SyMenu and its SPS package manager. I didn't investigate the internals of the program as it seems to me not having access to these internals. These observations give some indication which questions to raise for finding the reason of the observation. In the software testing industry it is well known the developers are biased on testing. And the observations with working work arounds proposed by you clarify some observations while keeping it unchanged on others that your analysis seems aborted prematurely. That's common in commercial software while open source software focuses more on root cause analysis before going to work arounds. As far as I know SyMenu is neither commercial nor open source. While both handling policies are valid, only the root cause analysis can assure a fix and solution. And it is you who claimed of always solving issues which wasn't the case here with most of these timeout errors. Gianluca wrote: Instead you are investigating the internals of the program with no cues in your hands because you didn't read the code, with no experience in the program because you are a new user, edited by Gianluca on 25/06/2019 Yes, I'm new to the program SyMenu. With that little experience I could at least report back to another user one way to handle his problem via this forum within three days. I call it a learning curve. You call it no experience. Gianluca wrote: Instead you are investigating the internals of the program with no cues in your hands because you didn't read the code, with no experience in the program because you are a new user, and, above all, without a real purpose. edited by Gianluca on 25/06/2019 I can't follow how you come to such a conclusion of not having a real purpose. Or do you want to say that new users have no purpose when reporting issues they observed? My purpose is to help improve the quality of the program. That's why I use the means proposed and recommended by the project SyMenu which is this forum, in particular this thread for reporting bugs and troubles encountered with SyMenu. What did I miss? Gianluca wrote: Do you really think that these endless interrogation can contribute in some ways to the application improving? I'm sorry, it can't. And even if you are suggesting something good, it's so hide inside your rant that I'm not even able to recognize it. edited by Gianluca on 25/06/2019 Which interrogations? If you mean my questions, then yes I think they may help analysis for fixing, reveal misunderstandings for clarification, and hence help improve the application. How do you come to the conclusion that my questions are interrogations? How do you come to the conclusion that such questions may not help to improve the application? Or do you mean your false resp. premature accusations as interrogations? And no. It's not true that you don't recognize good suggestions. It happens that you don't recognize it immediately. But that's something different of not recognizing it at all. You're better then you think and claim! Do you mean that because I made suggestions for improvement, you'll not consider them although you recognized them. Gianluca wrote: My feeling is that you are only showing how much good and analytics and experienced you are. OK you are the best. Are we good now? Can I return to more useful activities now? Thanks. edited by Gianluca on 25/06/2019 I didn't write about good or bad. So it seems that your feelings are deceiving you. What kind of more useful activities are you refering to? If you have difficulties with some kinds of bug reports, why not considering to extend the forum FAQ or add a pinned thread for directing and qualifying what you consider a good bug report, what a bad bug report, what an insufficient bug report, ... ? And why not fixing this major cause of premature download abort of SPS package manager timeout (instead of download timeout)? (I may repeat my two alternative proposals if you like.) Again, it's your decision when and how to address it as you provided a working work around. Priorization is completely up to you. I didn't ask for an immediate solution. That's the difference between bug reports and bug fixing. Other projects consider it more useful to use other tools for monitoring progress on bug reports (handling). I don't prescribe the SyMenu project which tools to use for this purpose. I use what this project provides and recommends. What did I miss?
27/06/2019 Topic: Unhandled Exception of SPS package manager chef	After three times using SyMenu resp. SPS package manager update mechanism for the tools included locally, I get the following unhandled exception error of SPS package manager to process on index beyond range!: See enclosed attachement. I don't remember if I encountered it after finishing these updates or if it was after I asked SPS package manager to refresh its processing list with the unchanged criterie (updates). Updateing succeeded for 59 out of 60 installed packages with one timeout error for update. I still didn't get notified about a fix or solution to that timeout error. Gians recommended work around though did work well. I choose to proceed anyway with the unhandled error as shown in the attached screenshot .
27/06/2019 Topic: Unhandled Exception of SPS package manager chef	After three times using SyMenu resp. SPS package manager update mechanism for the tools included locally, I get the following unhandled exception error of SPS package manager to process on index beyond range!: See enclosed attachement. I don't remember if I encountered it after finishing these updates or if it was after I asked SPS package manager to refresh its processing list with the unchanged criterie (updates). Updateing succeeded for 59 out of 60 installed packages with one timeout error for update. I still didn't get notified about a fix or solution to that timeout error. Gians recommended work around though did work well. I choose to proceed anyway with the unhandled error as shown in the attached screenshot .
30/06/2019 Topic: Unhandled Exception of SPS package manager chef	chef wrote: I don't remember if I encountered it after finishing these updates or if it was after I asked SPS package manager to refresh its processing list with the unchanged criterie (updates). Updateing succeeded for 59 out of 60 installed packages with one timeout error for update. This bug is still present and reappeared today. And I can report that it wasn't on finishing the update but afterwards when asking SPS package manager to update its list of still not yet successfully processed SPS packages. Here you'll find that what looks like a trace stack, if this helps for analysis. It further sounds that the index would have a value either too low or negative. Do you want me to follow the instructions to enable JIT-Debugging in preparation for the next occurance? And do you also want the used assembly list? If yes, I prefer sending by PM instead of post, just in case of need and interest. ************ Ausnahmetext ************ System.ArgumentOutOfRangeException: Der Index lag außerhalb des Bereichs. Er darf nicht negativ und kleiner als die Sammlung sein. Parametername: index bei System.Collections.ArrayList.get_Item(Int32 index) bei System.Windows.Forms.DataGridViewRowCollection.SharedRow(Int32 rowIndex) bei System.Windows.Forms.DataGridViewRowCollection.get_Item(Int32 index) bei SyMenu.FormSPSMain.‎‏‍‪⁯‬⁮‎‍⁮⁮⁯‬‬⁬‎‏‭‪⁯‮‎⁯‫‫‬‬⁮⁪⁬‏⁯‏‎‎‪‮(DataGridViewRowCollection , Int32 ) bei SyMenu.FormSPSMain.GetSPSElementFromDataRow(Int32 index) bei SyMenu.FormSPSMain.gridSPSPrograms_SelectionChanged(Object sender, EventArgs e) bei System.Windows.Forms.DataGridView.OnSelectionChanged(EventArgs e) bei System.Windows.Forms.DataGridView.FlushSelectionChanged() bei System.Windows.Forms.DataGridView.ClearSelection() bei SyMenu.FormSPSMain.‍‏‌‮‍‪‬‍‏⁭‌‬⁯⁬‏⁮⁪⁬⁪⁪⁬⁮⁬‪‪‎⁮‏⁮‎⁬⁬‏‫⁪⁪‌⁬‮(DataGridView ) bei SyMenu.FormSPSMain.ResetForm() bei SyMenu.FormSPSMain.TabControlResize(Boolean expand) bei SyMenu.FormSPSMain.SearchWithFilter() bei SyMenu.FormSPSMain.btnFilterSearch_Click(Object sender, EventArgs e) bei System.Windows.Forms.Control.OnClick(EventArgs e) bei System.Windows.Forms.Button.OnClick(EventArgs e) bei System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) bei System.Windows.Forms.Control.WndProc(Message& m) bei System.Windows.Forms.ButtonBase.WndProc(Message& m) bei System.Windows.Forms.Button.WndProc(Message& m) bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
30/06/2019 Topic: Unhandled Exception of SPS package manager chef	As far as I understood, I still don't have the source of this project nor did I ask for. I only report what I observe that SyMenu resp. its SPS package manager report. This SPS package manager reporting gives some hints about internal code but doesn't mean I have it as could be a possible misunderstanding by Gian. It's still up to him to analyse and request what kind of context information might be helpful for identifying what happened, what the reasons and the root cause are and how to fix it unto when he may find time. Just my note after using SyMenu just a few times within a week and still progressing slowly on customization.
30/06/2019 Topic: How to know when to use builtin update? chef	As a newbee of using SyMenu just for almost 10 days, I still don't know when to use builtin update of "installed" tools as far as this feature exists within. Is it save to always try such a builtin feature if existing, and to proceed in any case when it does not initiate a web browser download resp. abort in case of such web browser download initiation is tried? And in the latter case, I should instead contact SPS package editor to inform him of new available version. Right?
30/06/2019 Topic: Which methods exist to stop SyMenu? chef	As a newbee with about 10 days experience with SyMenu, I know the means to stop SyMenu with exit in its menu, by default on the bottom. But sometimes while using SyMenu, it vanishes too as if somebody has chosen to select exit. It wasn't me. Is this expected behaviour with which trigger? At least I don't expect such a behaviour. It happened twice today and least once before. I still don't have a clue on its trigger so seemingly at random.
30/06/2019 Topic: Missing forced install resp. update option chef	As a newbee, I've not seen an option I'm looking for in my first 10 days. SPS package manager has an option to install an SPS package via web or via local storage if it is not yet installed. SPS package manager provides also an option to force reinstallation via web if already installed. What I'm missing is the option to force reinstallation via local storage. What did I miss finding? Where do I have to look for this feature?
30/06/2019 Topic: Missing forced install resp. update option chef	It seems now that the missing option exists for some SPS packages like RJ TextEd while being missing for others like TextEditorPro. So what's the reason for such a difference? What options exist to handle this difference?
01/07/2019 Topic: SyMenu Settings Form chef	On the left side of SyMenu settings form, there is usually a vertical scroll bar when the complete suite is installed as recommended. That's fine. Also when I add my own folders for customization, this works too. The whole set of containers and folders is accessible via that left navigation section. But when I try to move a container into the last folder, this seldom works. Moving is possible to almost all custom folders and existing containers. But the last entry isn't displayed when moving another element, folder or container. It works sometimes nevertheless to move an entry to the last and no longer displayed custom folder. After finishing the move, the display of the navigation section works again as expected, showing all containers, folders and elements, including the last one. What do I need to configure in order to display the last custom folder while moving another element?
01/07/2019 Topic: Unhandled Exception of SPS package manager chef	Gianluca wrote: chef wrote: This bug is still present and reappeared today. And I can report that it wasn't on finishing the update but afterwards when asking SPS package manager to update its list of still not yet successfully processed SPS packages. Who did ask to the SPS Manager to update the list? Was it you? Because the SPS Manager updates by itself whenever it finishes the update/installation/delete process. If you force the update you are forcing the update of the programs definitions not only the list update. So does this bug appear after the automatic (local) refresh or your forced (online) refresh? Does it always appear or occasionally? edited by Gianluca on 01/07/2019 Sorry that I wasn't precise enough. What I meant and did was not to request an update (in the sense of reload) of SPS definitions. It was just an update of that list to process instead. The corresponding action button carries the localized label for search. As far as I can see, the action of this button is as expected, not to update the SPS definitions but to reapply the filter criteria to the displayed list as the automatic update of that list kept the processed element on that list although no longer complying to the specified filter criteria. The manual is a bit short on this feature in the section filter. The automatic update of the list by SPS package manager seems inconsequent. It doesn't change the size of the list. It just changes the state of that package although with changed state it no longer complies with the search criteria defined on the right column called filter in the manual. This choice also allows some post processing of the just processed element resp. tool to be initiated by myself without any intermediate steps. So this inconsequence is meaningful. I don't like the default search criteria. And I didn't look up if that default may be reconfigured to one of my preferences. And the manual doesn't explain one difference letting me assume what is meant. The terms in my language don't correspond to the terms in the manual! It might even be that the localized terms are even better than those in the manual. The localized version of SPS package manager doesn't tell which term is used for updated tool version and which term for updates SPS definition, assuming the term update meaning the first case (updated tool version). (According to the figure in the manual, the international non-localized version seems to use the term added where the localized one uses update and the international version seems to use the term update where the localized one us something like refreshed. Is this an error in the manual? The comparison between localized version and manual confuses at this point of the manual.) This inconsequence is fine. It gives me the choice when I want which kind of update of the list. Such a post processing might be some customization, some configuration or immediate execution. Without this inconsequence, post processing would require to search again for the already processed element with different filter or search criteria which would take longer. So the automatic local refresh happened before the described symptom. And I don't know if this symptom would also appear with forced online refresh. I didn't try. What may be possible is that the internal data structures handle this inconsequence differently, being more consequent on internal data structure then on display and perhaps not providing a field for that difference between display and internal data structure. That would explain the debugger output probably meaning off by 1 corresponding to the list one field longer then the filter criteria would expect. So I don't expect that symptom to appear in the context of forced update of SPS definitions after automatic local refresh list. So yes, it was me who decided and requested an update of that list to process in order to recomply with the filter criteria as I decided that I finished the update of the just processed tool (resp. former list element still being displayed as part of that list although no longer complying to the filter criteria) so wanting to have a again the list with still unprocessed tools (resp.list elements). This has nothing to do with an update resp. refresh of the SPS package definitions. And as reported initially, this symptom comes irregularly. Common context criteria are that there are several tools available for update and updating doesn't succeed for all of them. Usually, there remain more than one tool not updated when the described symptom appears. But if I remember right, this doesn't forcibly lead to the described symptom, only sometimes. I still have no clue what triggers it or what additional constraints like race conditions have to be reached as constraints to make it reproducable. (Race conditions are difficult to identify.) That's why I asked if you ask me to prepare to follow the instructions of the debugger to get not just symbolic trace but also the corresponding parameters. That's at least as I understood the debuuger annex with instructions not posted as it is reported in localized language.
01/07/2019 Topic: Missing forced install resp. update option chef	Gianluca wrote: The force update is only available with already installed programs and through online packages. That doesn't seem true. It seems true initially but may change on context. My request is to have the option of forced update with already installed tools not only via online packages but also via local packages. And it seems that this option isn't available initially as you claimed. But if I use the icon in SPS package manager for manual download, it seems that this opens the desired choice (of forced update via local package) in context menu, not before. I observed this difference at least twice yet, not knowing if it is deterministic. I couldn't find a corresponding note in the manual for advanced users neither. So is my request already implemented and the observed behaviour deterministic although not yet described?
01/07/2019 Topic: SyMenu Settings Form chef	Gianluca wrote: Can you post a little video where you reproduce the issue? A few seconds is enough. Not now. My priorities are currently different. I'll probably not find time before Friday afternoon. So please remain patient on follow up some time. Gianluca wrote: If you don't know a program to record your desktop I can advise you to try ScreenToGif (in the SyMenu Suite). Thanks for that hint. I don't know where to find. But SyMenu has an appropriate seach field. So I may proceed as time permits.