S sorex Expert Licensed User Longtime User Oct 14, 2015 #1 Hello Erel, As you know by now the pre-compile / parse check that happends on each keypress is causing issues for a lot of people. Now we can apply a workaround by tweaking the kick-in delays. (I use 30 seconds) The only drawback is that we need to wait to see if our code is right or we need to do a full compile which is overkill in most cases (edit: when it succeeds that is). Is it possible to invoke that check by pressing for example F4 (which seems to be free) ? this also applies to all B4x products. Last edited: Oct 14, 2015
Hello Erel, As you know by now the pre-compile / parse check that happends on each keypress is causing issues for a lot of people. Now we can apply a workaround by tweaking the kick-in delays. (I use 30 seconds) The only drawback is that we need to wait to see if our code is right or we need to do a full compile which is overkill in most cases (edit: when it succeeds that is). Is it possible to invoke that check by pressing for example F4 (which seems to be free) ? this also applies to all B4x products.
S sorex Expert Licensed User Longtime User Oct 14, 2015 #2 We have discussed this issue on the chat once again. Funny thing is that one user, hey @MikeH , doesn't have these delays but his error log panel doesn't get updated at all until he does an actual compile. Are there triggers implemented that disables this for some configurations?
We have discussed this issue on the chat once again. Funny thing is that one user, hey @MikeH , doesn't have these delays but his error log panel doesn't get updated at all until he does an actual compile. Are there triggers implemented that disables this for some configurations?
Erel B4X founder Staff member Licensed User Longtime User Oct 15, 2015 #4 @MikeH have you saved the project once? Save it and the errors will show. sorex said: As you know by now the pre-compile / parse check that happends on each keypress is causing issues for a lot of people. Click to expand... I don't think that it affects many people. The slowdowns mainly occur with old single cpu computers (or with virtual machines). On most computers the IDE should run smoothly. I will consider adding such a shortcut.
@MikeH have you saved the project once? Save it and the errors will show. sorex said: As you know by now the pre-compile / parse check that happends on each keypress is causing issues for a lot of people. Click to expand... I don't think that it affects many people. The slowdowns mainly occur with old single cpu computers (or with virtual machines). On most computers the IDE should run smoothly. I will consider adding such a shortcut.
S sorex Expert Licensed User Longtime User Oct 15, 2015 #5 Erel said: The slowdowns mainly occur with old single cpu computers (or with virtual machines). Click to expand... that's the odd part. you can't find a line in this problem. I have it on 2 older dual core machines. some reported the same with a brand new machine. so it might be a slower key buffering issue or something combined with the check on each keypress. I'll stick with the forced delay in the INI file and work with the shortcut once it's added to a future release. Thanks for adding it soon.
Erel said: The slowdowns mainly occur with old single cpu computers (or with virtual machines). Click to expand... that's the odd part. you can't find a line in this problem. I have it on 2 older dual core machines. some reported the same with a brand new machine. so it might be a slower key buffering issue or something combined with the check on each keypress. I'll stick with the forced delay in the INI file and work with the shortcut once it's added to a future release. Thanks for adding it soon.
Erel B4X founder Staff member Licensed User Longtime User Oct 15, 2015 #6 sorex said: some reported the same with a brand new machine. Click to expand... I don't remember any such reports (with the exception of virtual machines). However I may be wrong here.
sorex said: some reported the same with a brand new machine. Click to expand... I don't remember any such reports (with the exception of virtual machines). However I may be wrong here.
S sorex Expert Licensed User Longtime User Oct 15, 2015 #7 a spec list of those who have issues would be a way to indicate something based on the processor types and their cores/speeds. on the other hand someone with an i5 @ 3.4GHz shouldn't notice anything at all altho prove is here > https://www.b4x.com/android/forum/t...ping-on-the-keyboard.55203/page-2#post-363641
a spec list of those who have issues would be a way to indicate something based on the processor types and their cores/speeds. on the other hand someone with an i5 @ 3.4GHz shouldn't notice anything at all altho prove is here > https://www.b4x.com/android/forum/t...ping-on-the-keyboard.55203/page-2#post-363641
